This is what we in the business call a "skill issue."
There are ways around it, yes. But none of them are plug-and-play unless you're lucky, and a reliable solution will require a combination of technical ability, stealth and social engineering.
True, but it's uniquely bad in the JS world. Developers tend to rely on libraries in almost cartoonish excess.
The language is shit in general, leading to an endless parade of frameworks and packages designed to paper over the sore spots.
The lack of a well-rounded One True Standard Library™ means lots of trivial functionality needs to come from somewhere.
Micro-dependencies are commonplace, leading to bloated dependency trees. I'd guess this is caused by a combination of both culture and the fact that you often want your JS artifacts to be as lean as possible.
Off the top of my head, for those that are curious:
The show depicts radiation as similar to a contagion. In real life, once you strip and wash someone exposed to radioactive contaminants, they pose no danger to others.
The reactor was never in danger of turning into a nuke or rendering huge swathes of Europe uninhabitable. Nuclear explosions only happen under tightly engineered conditions.
A big pile of molten reactor slag, while certainly dangerous, can't turn into a bomb.
However, the utter incompetence of the USSR is very accurate.
Bevy is definitely nice, but it's probably a bridge too far for (say) an indie team moving off Unity. (Rust learning curve + ECS learning curve + no editor yet + still pre 1.0)
I wonder if distributors could get away with doing that automatically. My gut instinct tells me that Unity isn't stupid enough for that to be feasible long term, but... like you say, the C-suite bozos clearly aren't listening to the engineers.
This is what we in the business call a "skill issue."
There are ways around it, yes. But none of them are plug-and-play unless you're lucky, and a reliable solution will require a combination of technical ability, stealth and social engineering.
Just read a book my man.