> We have technical debt in software. Investing in holistically proprietary and locked down ecosystems in enterprise, where you are talking millions in software

> We have technical debt in software. Investing in holistically proprietary and locked down ecosystems in enterprise, where you are talking millions in software and more in labor training, you are incurring your own form of technical debt. I understand, yet the challenge is exactly the same every time. Say, for example, you launch a brand new electric car company and need a bunch of integrated software and automation tools to help you do everything, from running the business to designing the cars, manufacturing, supply chain management, document processing, etc. You have two choices: You can be an operating system, FOSS, free beer, free speech, pink unicorns for everyone zealot. Or you can go buy shit that works and get on with the business of getting shit done. The difference is this: A business should only be concerned with delivering it's products and services and doing so on a timely manner while staying ahead of the competition. A business should not waste one microsecond on "technology jihad". That is not their job. It is up to entrepreneurs who are "believers" to identify opportunities --if and where they exist-- and work hard to create solutions that appeal to the businesses who need them. It's a tall task, because success might require replacement solutions across a wide range of disciplines. This guarantees that multiple solution providers would have to engage in this "holy war" (sorry, sticking to a bad analogy at this point) in order for the car manufacturer to be able to even consider making a switch. And then there's the other factor: Even if you could switch to an alternative universe and make it seamless within your organization it could still be a terrible business decisions. Why? Because if the vendors and suppliers you have to work with depend on communicating across company demarcation lines by using files produced by specific types of software you are almost assured a great deal of friction if you don't use the same tools. Don't believe me, call-up 100 machine shops and ask them if they accept Siemens NX or SolidWorks files and see what you learn. And both of those platforms run on Windows. > people, on Windows, do care when Microsoft behaves against their interests and forces those decisions upon them. Any professional is very careful about OS and software version transitions. Microsoft has had glitches here and there but they have always been nothing but rock-solid-reliable in their support of the needs of their business customers. We might be looking at another glitch, I don't know, but I don't really care, they'll do the right thing. Not saying this because I love MS. It's just a matter of historical fact. Thinking back over 36 years, I can't remember the last time MS boned anyone. I can remember multiple times where both Apple and various Linux issues did.