3 ms·

> BiomeJS started its life as a fork of the now-defunct Rome project Looking at the pace of frontend development tooling I cannot help but loose trust and conf

> BiomeJS started its life as a fork of the now-defunct Rome project Looking at the pace of frontend development tooling I cannot help but loose trust and confidence with every step and every new release. Major ecosystem player decides to break all previous compatibility with the vast infrastructure accumulated over the years [1]; the main officially recommended linter released under a major brand goes silently abandoned [2]; etc, etc. I didn't even knew Rome died. A wise queen once said, "it takes all the running you can do, to keep in the same place" [3]. She meant frontend web development. [1] https://eslint.org/blog/2023/10/flat-config-rollout-plans/ https://eslint.org/blog/2023/10/flat-config-rollout-plans/ [2] https://github.com/airbnb/javascript/issues/2961 https://github.com/airbnb/javascript/issues/2961 [3] https://en.wikipedia.org/wiki/Red_Queen%27s_race https://en.wikipedia.org/wiki/Red_Queen%27s_race

90s_dev 1y ago
This is the reason I stopped trying to write high-level tools that change every 1-2 years, and moved to creating/publishing low/mid-level tools that should still be relevant in 10 years. In other words, instead of creating Jekyll, I created a library that makes it trivial to make your own Jekyll however it makes sense to do so that year.
kccqzy 1y ago
You have choice. You can choose parts of the frontend ecosystem that is not crazy about tooling, like ClojureScript. You can follow a ten-year-old tutorial and it will still work.
- egorfine 1y ago
  Not on modern node.js. Not with modern frameworks. So all the running I can do is a requirement, unfortunately.
  - kccqzy 1y ago
    You can choose not to use node.js. You can choose not to use modern frameworks. Remember that React came out more than ten years ago and doesn't count as modern; so even if you choose a ten-year-old React it's still very good as compared to vanilla JS.

90s_dev 1y ago

This is the reason I stopped trying to write high-level tools that change every 1-2 years, and moved to creating/publishing low/mid-level tools that should still be relevant in 10 years. In other words, instead of creating Jekyll, I created a library that makes it trivial to make your own Jekyll however it makes sense to do so that year.

kccqzy 1y ago

You have choice. You can choose parts of the frontend ecosystem that is not crazy about tooling, like ClojureScript. You can follow a ten-year-old tutorial and it will still work.

egorfine 1y ago
Not on modern node.js. Not with modern frameworks. So all the running I can do is a requirement, unfortunately.
- kccqzy 1y ago
  You can choose not to use node.js. You can choose not to use modern frameworks. Remember that React came out more than ten years ago and doesn't count as modern; so even if you choose a ten-year-old React it's still very good as compared to vanilla JS.