2 Matching Annotations
- Mar 2021
Trying to force this one thing to work for everyone is the worst way to do that.
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.
- separation of concerns
- one size fits all mentality
- related but independent projects that can be developed independently
- avoid giving partiality/advantage/bias to any specific option
- uniformity: bad
- independent release cycles among peer dependencies
- single responsibility