

There’s no chance in hell Vance knows what that phrase means
There’s no chance in hell Vance knows what that phrase means
Oracle happened to it
All the devs went to LibreOffice after that
I wasn’t trying to give a positive side, I was just explaining why Microsoft wants the feature
If the executable binary has to be signed with a key, similar to the module signing key, Microsoft could sign their binaries
This, along with secureboot, would prevent the owner of the machine from running eBPF programs Microsoft doesn’t want you to run, even with root
I agree, but the wording of that is imprecise…
Google reimplemented the same API (which should be legal) but “use” sounds like they called Oracle’s implementation of the function
Oracle tried to argue that writing your own virtual machine with the exact same same interface as theirs (even a clean room reimplementatio, or an improved version) was copyright infringement
If Oracle had won, it would likely have killed things like OpenJDK, WINE, Proton, Rosetta, etc. and would have made licensing around OpenGL/Vulkan very confusing (for a few examples)
Kind of seems like they simply installed this dude’s tarpit from a few months ago
Where did Microsoft put an official announcement saying the statement from an official Microsoft employee, Jerry Nixon, speaking at an official Microsoft conference, Ignite, was incorrect?
Edit:
When reached for comment, [Microsoft] didn’t dismiss them at all
Recent comments at Ignite about Windows 10 are reflective of the way Windows will be delivered
https://www.theverge.com/2015/5/7/8568473/windows-10-last-version-of-windows
That’s already how it functionally worked for each major release
Here’s their previous strategy: https://web.archive.org/web/20220917195332/source.android.com/docs/setup/about/codelines
As far as I can tell, this would really only affect QPRs, since the public experimental branches that get made after they throw the next release over the wall is going away