5 ms·
> JS is still very "wild-west" because the community is still making rapid progress towards an ideal environment. Most of the churn seems to come from people
by flukus 10y ago
> JS is still very "wild-west" because the community is still making rapid progress towards an ideal environment.
Most of the churn seems to come from people reinventing the wheel over and over again.
- ng12 10y agoCould you elaborate? I hear that a lot but I suspect it only comes from people who don't do a lot of web development.
- flukus 10y agoLook at the number of binding/UI frameworks, look at the package managers, look at the number of unit test libraries, look at the number of build tools. Many get reinvented in a bubble when there are plenty of options already. Now half (maybe more) of the libraries are being written in languages that aren't javascript so now there are multiple competing ecosystems on top of javascript. And then you have things like angular creating churn within the framework.
- ng12 10y agoSo the argument is essentially "there's a lot of stuff I don't really understand, a lot of it must be redundant"? React isn't just Angular with a different name -- they have fundamentally different views on how web development should be done. They also fit different use cases (Angular is a one-stop-shop, React is minimalist by design). Same thing with the build systems. Add in the fact that a lot of this wasn't possible until recently (i.e. Webpack is fundamentally enabled by ES6-style imports) and of course things are going to change rapidly. > Now half (maybe more) of the libraries are being written in languages that aren't javascript so now there are multiple competing ecosystems on top of javascript. I'm not sure what you mean by this. Elm-html is the only example I can think of that is non-Javascript. If you're referring to Angular2 being Typescript you can still use it just fine with regular JS.
- flukus 10y agoSure react and angular are different, what about the dozens of others? I posted elsewhere the number of crappy make clones alone: https://www.npmjs.com/search?q=make+build https://www.npmjs.com/search?q=make+build
- BigJono 10y agoWhat about them? As a front-end develop I don't know or care about them until they solve a problem I have with the existing toolset. I couldn't care less whether there's one alternative to React/Angular or a thousand.
- Klathmon 10y agoFor starters, why is that a problem? You aren't forced to use them all, you aren't forced to use any of them. But secondly, what makes them crappy? I've used make, and IMO it's pretty crappy itself. Have you had to maintain a recursive makefile? It's a complete nightmare to say the least. And i'm far from the only one to think make is worthy of a "remake". In fact even in just the C/C++ world there is cmake, qmake, autotools, scons, ninja, bazel, premake, waf, shake, tup, etc... If you run your same search in pip, or ruby gems, or composer, or cargo, or cpan, or any other package manager for any other language and i'm sure you'll see it's fair share of build tools, frameworks, libraries, and unmaintained stuff. It's not a problem, and it never will be.
- flukus 10y ago> For starters, why is that a problem? You aren't forced to use them all, you aren't forced to use any of them. It's a problem because every time I need $tool I might have to evaluate dozens of choices, check for compatibility, investigate the ones that suit, hope to god the rest of the community is familiar with it, hope it is supported in future, etc. And then with the rate of churn you might have to do the same in a year. Make has been supported for 30 years, I know it's not going anywhere. > In fact even in just the C/C++ world there is cmake, qmake, autotools, scons, ninja, bazel, premake, waf, shake, tup, etc... So there's already dozens of tools, why reinvent them in javascript? Every ecosystem does this but it least most seem to settle on one or two tools, this doesn't seem to be happening in the javascript world.
- stephenboyd 10y agoIn this case, the wheel started off with an impractical oval shape and the reinventions are usually making it rounder. If you'd stopped the churn two years ago, people would be using Bower for front-end package management in addition to NPM, and Gulp or Grunt for task automation. Now a few churns later, NPM is the only package manager you need since you can use Webpack to automatically cut out your duplicated front-end packages. And now NPM provides all the task scripting most devs would need, so no more Gulp or Grunt. Things are getting simpler and easier, but if you're looking from the outside you'll just see a long list of names of tools.
- antihero 10y agoThe wheel design of today is far superior to the first wheels invented. Why is reinventing the wheel a bad thing?
- flukus 10y agoIt's fine if you keep the good, throw out the bad and make some improvements. But very often the good parts get forgotten, like the roundness.