4 Matching Annotations
- Mar 2021
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
- programming languages
- level playing field
- neutral ground
- independent release cycles among peer dependencies
- one size fits all mentality
- related but independent projects that can be developed independently
- competition in open-source software
- programming languages: choosing the best language for the job
- avoid giving partiality/advantage/bias to any specific option
- software freedom
- single responsibility
- runtime environment
- good idea
- Nov 2019
It’s not enough to check the stuff that is suspicious: if you apply your investigations selectively, you’ve already lost the battle.
This made me reflection on biases. If our research methodology is biased from the very beginning, then everything that comes after will also be biased.