Re:PR converts the Three.js codebase to ES2015 modules
by sergiotapia on Sunday July 24, 2016 @09:01AM
(#12153190)
>You seem to be complaining that innovation is happening.
Not at all. I'm complaining that all of these seemingly similar tools keep superseding each other and solve...what exactly.
Re:PR converts the Three.js codebase to ES2015 modules
by nilliams on Monday July 25, 2016 @04:48PM
(#12161516)
Why do you think competitiveness of tooling is a bad thing? I understand why it could feel overwhelming, but you really can just pick one (assuming it appears to do what you want) and if it does, stick with it.
If you don't want to deal with the inevitable 'options' that are going to be offered up by a community as large as the JS community, you could 1. pick a smaller community, 2. stick to old tech (e.g. at our company we still have an app running on RequireJS that runs just fine -- RequireJS is over 6 years old). 3. calmly re-assess tech choices every year or so.