Re:LSP could have been better
by throwaway50182 on Thursday October 12, 2023 @06:45AM
(#37855501)
By this logic, they are also currently Embracing and Extending Windows, Office, etc. This doesn't make sense to me. It's their original products, not something they embraced and plan on extinguishing.
Re:LSP could have been better
by prometheon1 on Thursday October 12, 2023 @08:26AM
(#37856232)
Windows and Office are both mentioned as products that are leveraged to do EEE on Wikipedia: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
They are not extinguishing their own products, but using their products to extinguish alternatives. The example I mentioned actually fits the wikipedia definition quite well in my opinion.
CSS was to a large extent a Microsoft project (when the time came to introduce stylesheets it was more-or-less Opera and Microsoft against Netscape, and Microsoft had many more users than Opera).
Nonetheless Microsoft managed to use CSS to achieve a great deal of user lock-in by refusing to conform to the standard they co-authored.
Re:LSP could have been better
by throwaway50182 on Thursday October 12, 2023 @06:17PM
(#37863883)
Well then that's clearly not EEE. There can be more predatory market strategies than just EEE.
Re:LSP could have been better
by prometheon1 on Friday October 13, 2023 @04:54PM
(#37875517)
- Embrace the web with Internet Explorer.
- Extend the web with CSS as an open standard.
- Extinguish competition by being the main browser and not following the CSS standard.
Still follows the recipe quite well in my opinion.
Building VSCode, LSP and Typescript could still prove to be the Embrace and Extend phase. There are some worrying signs, e.g. many VSCode extensions built by MS don't work on open-source VSCode builds like code-server and VSCodium. From a business perspective, this makes sense, as GitHub Codespaces and vscode.dev now have features that are difficult to get in competitors. Maybe at some point they will try to Extinguish all local development and push everyone to use a cloud version of VSCode? (See e.g. Python integration in Excel)
The truth is probably a lot more complex, but we can't rule out anything yet.