First you have to convince consumers to give up on systems that work with support to development kits that are build it yourself with (lots of) caveats, which is why the year of the Linux desktop still hasn’t arrived.
It was a tongue-in-cheek / silly suggestion outright. I don't think many people are actually using the tool for its off-ToS purpose though, there is also a lot of prior art across multiple sharing services. It's still interesting to think about the inner workings of it.
Never used one in over 15 years. I write a short post it only if I don't finish a certain task between days and it is really complex or maybe as a to-do list before leaving for holidays.
But I never felt the urgency to start a proper notebook. All the important decisions are documented in form of git commits for code or decision records for systems
Why is it a new surface? Either you can run UEFI code, or you can't. Attacking the JS interpreter itself is unrealistic IMHO, it's the poorly written JavaScript running on top of this that might open new surfaces of attack. But other UEFI code is mostly written in C or C++, so let's call that a wash?
Coincidentally, if you switch to use Windows Server 2025 (which is W11), you end up with a much better experience. No forced updates, no ads or messed up things with account
reply