State of the Art JavaScript in 2016

Post by danmaz74 » Sat, Mar 12, 2016, 12:20 PM UTC

f1hybrid wrote: post #158

natrius wrote: post #113

Earlier quoted context omitted.

React is a paradigm shift in UI development. If you've never tried it or a library inspired by it, that's why you're questioning the proponents. We're trying to spread the gospel that some folks found a better way to do things. Yes, I believe it is a mistake for any UI developer to delay learning React. It's fine to choose other tools later.

I come to HN regularly for advise. Should I be taking yours? I'm a web dev by proffession. React is a paradigm shift? Kind of like the paradigm shift 20 years ago where we said "separate your markup from your style, you'll be better off, promise"? Using css felt right, right from the start. I should really learn React? Mixing js and html in a react flavor does not give the the same sense of being on the right track.

Post by dsego » Sat, Mar 12, 2016, 12:30 PM UTC

girvo wrote: post #183

utku_karatas2 wrote: post #123

Earlier quoted context omitted.

JS scene desperately needs a moratorium on tooling just like Python did on language features 5-6 years ago. Actually the language also needs a total freeze in features. ES5, ES6, transpilers, this and that and bla bla. I used to love language geekery, not so much after a few years of JS exposure. And now there is WebAssembly which is supposed to be a "game changer". Fuck that. I don't want the game to change anymore,…

I don't understand this argument at all. You don't have to be on the bleeding edge. In fact I recommend against it for nearly all cases. If you want to write standard ES5, and skip all this stuff, you can! There is no one holding a gun to your head telling you to keep up "or else". I pick and choose the tools I need. Some are new, some are old. This goes for any language I use, too, not just JavaScript.

Post by yoklov » Sat, Mar 12, 2016, 12:38 PM UTC

spriggan3 wrote: post #166

leeoniya wrote: post #117

Earlier quoted context omitted.

Good ideas get standardized. Ideas from Coffeescript made it into es6, Promises, fetch, etc. Once there are sufficient standards that solve the pain points, the fragmentation will go away. JS is playing catch-up because it was pointless to advance the language when IE didn't even support the existing standards and had 90% market share. Now it has to distill all the good ideas from the past 2 decades and other languag…

Standardization isn't enough. No browser implements ES6 modules thus the webpacks and co.

Post by DrJokepu » Sat, Mar 12, 2016, 12:41 PM UTC

oneeyedpigeon wrote: post #206

andybak wrote: post #195

Disappointing that after months of moaning about the paralysis of choice, few of the comments are positive about a genuine and fairly defensible attempt to cut through that. He proposes a fairly simple stack (and for the sake of argument he assumes you're needs are beyond the 'static html and a touch of jQuery' stage). He spends time explaining them and makes a fairly good attempt to avoid the overly-new or overly-co…

"HN comments needs an on-topic vs off-topic filter. Or a "yes we already know that" filter..." They already do; if something doesn't positively contribute to the discussion, downvote it.

Post by k__ » Sat, Mar 12, 2016, 1:00 PM UTC

kenOfYugen wrote: post #200

> Avoid CoffeeScript. Most of its better features are now in ES6, a standard. This argument against CoffeeScript isn't very objective. One of CoffeeScript's best features is the minimalistic and expressive syntax. "CoffeeScript (#6) appears dramatically more expressive than JavaScript (#51), in fact among the best of all languages."[1] "CoffeeScript is #1 for consistency, with an IQR spread of only 23 LOC/commit comp…