this post was submitted on 21 Jan 2026
119 points (92.2% liked)
Linux
11278 readers
319 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It would be in line with their usual EEE, so totally not surprising.
They don't give two shits about brand loyalty as long as line go up.
What standards would Microsoft EEE in this case? POSIX?
they might ship a proprietary lib with their os, encourage developers to use it, then license it out of being distributed
I imagine it’d be more like Android/iOS. Lock down bootloader so you can’t tamper with the OS, enforce notarisation requirement so that apps have to go through them. But Microsoft can’t do that, they don’t have any users vendor-locked to their application store. Valve on the other hand is in a much better position to do this.
The whole OS and user base.
That’s not what EEE is.
By all means do nitpick the specific meaning of EEE, might be amusing to others.
I just don’t like people throwing around terms they don’t understand, leads to weird outcomes like people saying Meta would EEE ActivityPub back when every instance decided to defederate Threads.
@0x0 @codeinabox it wouldn't be EEE in this case. Because a Linux distribution is built up around thousands of packages from hundreds of various open source projects.
For EEE to work, the entire base OS stack would need to be extended with features not becoming useful outside Microsoft's use. Such changes would first of all have a really hard time being accepted in upstream projects. And if they did, these projects would be forked if the last E phase in EEE is triggered. And then Microsoft would be alone with their Frankenstein distribution monster while the majority of the Linux users moves on to something better.
With Linux, there is no single instance of control or power. If a project takes a path people don't like, it get forked. EEE requires Microsoft to cease full control of all the related pieces and components and kill the open source aspects of it.
That's the advantage of open source licences. Once the source is out in the public, you can't retract the source code afterwards, then it just forks.
Ever heard of android?