41–46 of 46 posts
Earlier quoted context omitted.
Someone should make an opinionated, batteries-included JS/TS framework like Elm, based on TS, React, Flux.
The JavaScript world doesn't like that. That's why no one has made a carbon copy of Rails. Even React, Flux, Router and etc comes in several parts. I know railties are modular but at least they come from the same project and repo and update together.
Earlier quoted context omitted.
Either you're stuck with ES4 (and worse, you can kiss goodbye to a large number of NPM modules which are ES6+) or you still need a transpiler and a system to package your scripts, handle polyfills, etc. It's just difficult to do non-trivial JS development without only "raw Javascript" in 2016.
RequireJS, jQuery, JSF, ASP.NET, Spring are what we use.
Earlier quoted context omitted.
Either you're stuck with ES4 (and worse, you can kiss goodbye to a large number of NPM modules which are ES6+) or you still need a transpiler and a system to package your scripts, handle polyfills, etc. It's just difficult to do non-trivial JS development without only "raw Javascript" in 2016.
RequireJS, jQuery, JSF, ASP.NET, Spring are what we use.
On the other hand, switching to React + Redux + webpack (and NPM) has changed development from "we can't do that" or "let's copy paste from some other component" to "I'll have something by tomorrow" and "I'll reuse the generic React widget I made last time". It's really a game-changer.
Also, ES6 >> ES4. Destructuring doesn't bring you what real pattern-matching does, but it's still a lot nicer than what ES4 gives.
Earlier quoted context omitted.
RequireJS, jQuery, JSF, ASP.NET, Spring are what we use.
We used to be RequireJS/jQuery based on the frontend. While this obviously depends on what kind of application you have, attempting to develop complex UI in jQuery is not an experience I'd describe as "pleasant", nor does it naturally lead to creating reusable components. On the other hand, switching to React + Redux + webpack (and NPM) has changed development from "we can't do that" or "let's copy paste from some ot…
Companies that still want to target IE 8 or even the old Safari for Windows.
Earlier quoted context omitted.
We used to be RequireJS/jQuery based on the frontend. While this obviously depends on what kind of application you have, attempting to develop complex UI in jQuery is not an experience I'd describe as "pleasant", nor does it naturally lead to creating reusable components. On the other hand, switching to React + Redux + webpack (and NPM) has changed development from "we can't do that" or "let's copy paste from some ot…
Now try that in the context of 30+ enterprise developer projects, composed with multiple outsourcing/offshoring partners. Companies that still want to target IE 8 or even the old Safari for Windows.