Adam Mosseri:
Second, threads posted by me and a few members of the Threads team will be available on other fediverse platforms like Mastodon starting this week. This test is a small but meaningful step towards making Threads interoperable with other apps using ActivityPub — we’re committed to doing this so that people can find community and engage with the content most relevant to them, no matter what app they use.
EEE doesn’t work with FOSS, where anyone can fork a project and go with it.
Ask Oracle how well EEE worked for them with Sun, Java, or MySQL. Ask Microsoft how well adding the WSL worked to kill Linux.
Threads can try as much as they want, the fediverse is already full of different projects like Mastodon, Lemmy, Pixelfed, PeerTube, Calckey, etc. and they aren’t extinguishing each other.
The point of EEE isn’t outright destruction but marketplace irrelevance. FOSS projects can absolutely be hit by it.
Java actually was hit by EEE tactics from Microsoft, and they were actually rather successful. Sun has to sue MS to stop them from calling their Java VMs Java.
HTML was hit by EEE tactics so well that for years IE was the only game in town and other browsers couldn’t compete.
Sun sued MS to stop them from calling it “Java™”, then Oracle failed spectacularly to EEE it when they lost the API lawsuit against Google.
MSIE’s popularity arose from monopolistic practices by Microsoft, not its EEE tactics against HTML, which failed miserably.
I would know it, I was there: everyone started making websites in Flash because it was the multiplatform solution, even if it had more security holes than a female duck cornered by a flock of horny drakes, only MS sellouts used MSIE’s proprietary extensions to HTML, only Oracle sellouts used post-Sun Java… and it all went down the drain the moment JavaScript evolved to a point of allowing polyfills to make a single codebase compatible with all browsers.
Now all browsers are FOSS-based, with de-branded forked versions making the rounds, and it’s good.
Because that was part of MS’s EEE strategy.
Ooo boy you do not remember your history.
When Microsoft started pushing IE, they did everything in their power to sabotage the competition. That included the creation of a proprietary web extension called ActiveX. Back in the day, this, along with non-standard behaviour when dealing with the actual standards, was the reason why many, many sites would not work in non-IE browsers. Developers only cared about what worked in IE, not what was standard. That didn’t change until the arrival of Firefox.
You know how trademarks work? Sue or lose it.
I remember my history quite well, all the way back to Mosaic and before. I also remember “Best viewed with Netscape” websites (1994), when everyone and his uncle had a proprietary plugin they were trying to push, and only a handful of developers (I was one of them) actually cared about any standards. Firefox (2004) came very late to the party, way after the “MSIE can’t be uninstalled from Windows” shenanigans (1997).
Wouldn’t have applied in this case. Microsoft actually did have permission from Sun to use the trademark…right up until they made their Java VM incompatible with base Java, and Sun sued to terminate the agreement.
Okay? And? None of them had any actual leverage to force people into using their standards. Microsoft had a de facto monopoly on an essential bit of computing software that they leveraged to hell and back to make their proprietary standards THE de facto standard.
And at that point, IE had a 97% market share. Care to take a wild stab in the dark why?