[ameyv]

In your opinion, what expected changes in JavaScript are going to be the most important?

"The best thing we can do today to JavaScript is to retire it. Twenty years ago, I was one of the few advocates for JavaScript. Its cobbling together of nested functions and dynamic objects was brilliant. I spent a decade trying to correct its flaws. I had a minor success with ES5. But since then, there has been strong interest in further bloating the language instead of making it better. So JavaScript, like the other dinosaur languages, has become a barrier to progress. We should be focused on the next language, which should look more like E than like JavaScript."

Well he is right about that, the amount bloatware in terms of frameworks, libraries. I wish JS would have better goal or vision than to just make it like all for one kind of language mentality. These JS committees are hell bent on creating browser OS so they could eventually force everything to subscription based garbage software in running browsers requiring 64GB of ram. I guess we might be headed for those future sooner than we think. PS: Sorry for grim outlook but it kind makes sense from business perspective.

[jongjong]

If you count frameworks and libraries, I agree that the amount of bloatware is insane, but I don't think this is because of JavaScript. It's just that a few large companies which happen to use JavaScript (as most tech companies do) have been pushing their complex frameworks and tools onto everyone else and these happen to be bloated; they're only really effective in an environment where the employee headcount is not a concern - The real purpose of bloated tools (which are obsessively focused on 'code safety' as opposed to good architecture) is to allow companies to throw 10x more employees at a problem and not reduce the reliability of their development processes... But if they had chosen to hire better employees in the first place (with better hiring processes), they wouldn't need 10x more employees to get the job done in the same amount of time.

[Pet_Ant]

Framework bloat is community-scale efficiency. [Everybody uses a different 20% of the framework](https://www.joelonsoftware.com/2006/12/09/simplicity/), but it means that the core infrastructure, team, QA, etc are pooled. If you need to expand to 21% you already have that covered. If you look at the popularity of Spring Boot you see that people want more integration and between libraries not less. Now, it drives me nuts and definitely offers many sub-optimal solutions, but we need to face it, large frameworks are here to stay. Large frameworks are the new operating systems. You can do better with custom on bare-metal but there is a reason the Linux nevermade it on the desktop.