The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.
3 Matching Annotations
- Mar 2021
-
www.sitepoint.com www.sitepoint.com
-
-
JavaScript needs to fly from its comfy nest, and learn to survive on its own, on equal terms with other languages and run-times. It’s time to grow up, kid.
-
If JavaScript were detached from the client and server platforms, the pressure of being a monoculture would be lifted — the next iteration of the JavaScript language or run-time would no longer have to please every developer in the world, but instead could focus on pleasing a much smaller audience of developers who love JavaScript and thrive with it, while enabling others to move to alternative languages or run-times.
Tags
- runtime environment
- programming languages
- competition in open-source software
- separation of concerns
- related but independent projects that can be developed independently
- programming languages: choosing the best language for the job
- avoid giving partiality/advantage/bias to any specific option
- one size fits all mentality
- neutral/unbiased/agnostic
- single responsibility
- independent release cycles among peer dependencies
- good idea
- neutral ground
- JavaScript: as a process VM
- software freedom
- level playing field
Annotators
URL
-