Probably all managers and engineers working on Teams have similar copious amounts of memory and powerful CPUs on their devices and hardly use their own product. That would explain a lot
It honestly wasn't much different on my 2018 i5 Mini with 32 GB.
Maybe what sucks here is the experience of running it on Windows. Or maybe it sucks for large meetings? But I never have Teams meetings with > 40 people at this company.
You definitely can once the device has a hostname set in set-inform. The MAC proxy is just for initial adoption where a device may only know the IP. Such as when you use DHCP Option 43.
You can after the initial discovery step, the article mentions this. The MAC routing is for the first step where the device is reaching out to try and find a controller and signal it's available for adoption, which uses an IP address at least in the scheme that is relevant for hosted operators. After that initial channel is established, the controller uses it to tell the device what its hostname is, and you can switch to more normal HTTP proxy routing thereafter.
I just packaged the extension for the fun of it! And I do want people to try for themselves, that is the point. About people that are not dumb; surely many people are not dumb; many people are very smart indeed. But that does not prove there are no dumb or gullible people!
thanks for responding and sharing your perspective.
What I would say, you could have omitted some negativity or judgement from your post about 4k devs starring something because it looks simple, because they might have different intentions for starring.
Here is another great example of 65K "not wrong" developers: https://github.com/kelseyhightower/nocode - there is no code, long before AI was a trend, released 9 years ago, but got 65K stars! Doesn't mean devs "not wrong", it means people are curious and saving things "just in case" to showcase somewhere
I'm so fascinated by replies like this, it's too random and nonsensical to be a language barrier issue, but it also does not pattern match into LLM generated text. Reminds me of ~2010 era wordpress comment spam.
The table lists very limited support for M1 and not even lists newer variants! I guess it was only to be expected, asahi Linux also has challenges and of course FreeBSD has less eyeballs than Linux
All browsers ever implemented was XSLT 1.0, from 1999. There were 2.0 and 3.0 for which there is an open source Java based implementation (Saxon) but this never made it into libxslt and/or browsers!
reply