3 ms·
That's not the only reason it would become the defacto standard, and it's naive to claim so. https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish ht
by happymellon 1y ago
That's not the only reason it would become the defacto standard, and it's naive to claim so.
https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extingu...
Users can get a bundled version that slowly breaks compatibility forcing vendors to align with the closed source version.
- catach 1y agoIt would indeed be naive to make that claim, so it's a good thing that's not what I did.
- happymellon 1y ago> If the closed fork functionality is superior enough to make the original de facto obsolete then the users have already collectively decided that the tradeoff is worth it. I'm afraid you did. Users are lazy, and IE and Java on Windows are great examples.