What I meant by all of this is that, coming from the perspective of a developer and a user who has had to confront the nuances of intel design and library design and dependency hell and a million other buzzwords relevant to computer programming and computer science is this:

I am not presently a developer. I would not want to be one. I view a lot of people as wasting their time and effort grinding against the machine to extend and repair "broken ecosystems". Their crime is more that their efforts result in more people learning and grinding, thus prolonging the lifecycle.

I am not the kind of person who develops an extremely extensive and methodologically comprehensive understanding about specific subject matter. I think it's almost narcissistic how much some people batter others over the head with their relative insight into technical archeae relevant to specific subjects and specific systems. You act like you're smarter but isn't the reality that you're merely more familiar with the specific ARG that you have invested your entire life into?

I am the sort of person to be moderately familiar with everything. No matter the subject, no matter the field, i will vaguely understand what people are talking about.

What I see in computer science is that many billions of hours in manpower are being wasted maintaining vast machines we have essentially built on 40 year old technology. There is a saying "if it's not broke" which does apply here, but please try to appreciate where I'm coming from without regarding me on the basis that you consider me ignorant. It would be a great force multiplier to consider all of the pieces of this puzzle and their complexity together, and what you might gain by rebuilding all of it from scratch. The amiga, BEOS, PPC, all of these are great ideas that saw their day but ultimately fell before the juggernaut. C(with ++ going on to '14 now) on x86(with intel extensions)! A more insecure, broken, and easy-to-make-inscrutable madness there has never and will never be!

OOH it's powerful! yes, it sure is powerful. But the more powerful it gets the more effort you need to understand it and work in it and the more intelligence you need to really understand what's going on behind the scenes, which means there is a progressive reduction in the amount of work that can get done in the same number of hours.

And because it's a dominant juggernaut everything else is based on it. Enjoy your intel X86 based iphone modems! coming soon to a phone near you. Enjoy your 100+ languages BASED on and BOOTSTRAPPED in C, and therefore sharing many of it's traits and quirks.

With regards to living, not static ecosystems, by which I mean "deployment" and not "idea" - not languages, architectures so to speak but runtimes, libraries, programs, CRAP like electron and node and the continual cycling of thin vs thick vs mainframe focuses- we have docker on bare metal now-

The seemingly exponential increase in memory and computing demands to get marginally more done, or sometimes, LESS! done with newer runtimes and languages, all of that power going into the background because by god we have all of this power at our fingertips and it's so cheap now we dont have to worry about bloat. We can afford to have our users download 400MB every time they want to update their mobile webmail client, even if the core runtime is only 14mb and the core logic delivering their interface is only some 10kb.

No thank you! I would not write computer programs for you for any amount of money in the world!