3 ms·
> I disagree that the constant churn in FE/JS is necessarily a sign of "rapid progress", It's the field that is progressing rapidly. Browsers are constantly ad
by gotofritz 10y ago
> I disagree that the constant churn in FE/JS is necessarily a sign of "rapid progress",
It's the field that is progressing rapidly. Browsers are constantly adding new APIs, problems are being solved, etc. The difference is that it's open source
> a lack of strong stewardship/leadership
You can't have leadership in a field which has no owner. It's not like Oracle owning Java and deciding what happens with it.
> people reinventing the wheel.
This is a stereotype by people who don't really know the subject. Every new tool improves on the previous one. For example, grunt was the first JS build tool, it had some issues (huge configurations, and speed) some someone invented gulp, which uses streams for speed and code instead of configuration. But streams don't handle splitting files in bundles and other problems so well, so webpack was invented. There are overlaps but they all solve different problems, and all improve on the previous generation. They are not "reinventing the wheel"
- douche 10y agoHow many times do we have to rewrite make in nodeJS?
- gotofritz 10y agoMake doesn't solve all the problems those tools solve.
- flukus 10y agoA lot: https://www.npmjs.com/search?q=make+build https://www.npmjs.com/search?q=make+build
- deleted 10y ago[deleted]
- Klathmon 10y agoYou mean the same make that has multiple abstractions built on top of it (cmake, scons, autotools, etc...)? Snark aside, just because a product exists doesn't mean it's perfect, it doesn't mean that it can't be improved on. Gulp is significantly easier to work with than make for many usecases, and tools like webpack aren't really comparable to make.