1. Convenience usually transfers to less development time, which means less cost. Unless the performance is so poor that it’s unacceptable to a majority of users, many companies are willing to ship less-performant software if it means saving on development time and cost. 2. There is a lot of software that is used because people must use them. If your workplace uses Microsoft Teams despite its problems, then you’re es…
Without sounding elitist I think number 3 is a big one. If you once learn how, writing decently performing software is often straightforward without taking any extra labour.
Every month or so there's a thread here asking if college is worth it. Answers are typically mixed, depending on lived experience.
My own lived experience (I could program before I went to college) is that we didn't (especially) learn "programming". We learnt about fundamentals like algorithms, P vs NP, coupling, 3rd normal form, and so on. That affected our programming, but we didn't have "programming classes" (well except the first 3 weeks or so.)
I feel, looking back, that this served me well in the niche I traveled. My day job is basically writing performant libraries.
BUT I'm not in the camp of "computer science for all." There are other degrees at college, in programming, IS, IT and so on. There are lots of shorter courses that can train you up to get a job.