Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The State of JavaScript 2018

2018.stateofjs.com

Post reply on HN
Print view View original

281–286 of 286 posts

Re: The State of JavaScript 2018

#281

Post by _Tev »

tracker1 wrote: post #279
_Tev wrote: post #273

Earlier quoted context omitted.

I cannot speak for GP but for me the complexity comes from stitching dozens of libraries to get similar "base" to build the app on. Ember/Angular have way more stuff baked in or standardized, while in React you have to handle ball of ever changing dependencies ... For seniors it's ok(-ish) tradeoff (you get much more choice / control), for juniors it is hell on earth. But that is more of an issue for projects maintai…

What do you need that isn't in the box with React? Aside from fetch, which is in all modern browsers? The new Context component interface pretty much flushes out the last of what you are likely to need. As much so as what you get in the box with Angular. Even then, with Angular you'll usually need at least a visual component library, and with React, disparate components tend to work together with less friction compar…

Well if you focus on components only in your app then sure, not much needed. But complex apps need much more, like testing infrastructure, routing, data layer, service layer, tons of utility functions (last time I toyed with React it did not even have debounce ... Library for UI w/o it seems weird for me) and likely something else.

But hey, most apps are simple, so no need for all the above. I would say Ng/Ember are more specialized / niche.

Re: The State of JavaScript 2018

#282

Post by Digit-Al »

sgdesign wrote: post #14
Digit-Al wrote: post #6

Earlier quoted context omitted.

Not a question but a suggestion. I live in England and am very aware that the residents of Scotland and Wales don't like to be classed as "English". You might want to change the title to the more neutral (and correct) Britain, Great Britain, GB, United Kingdom, or UK.

Oh I didn't even see that, thanks for the feedback!

You're welcome. I see you've changed it now. Glad to be of help :-)

Re: The State of JavaScript 2018

#283

Post by Digit-Al »

wackro wrote: post #65
Digit-Al wrote: post #6

Earlier quoted context omitted.

Not a question but a suggestion. I live in England and am very aware that the residents of Scotland and Wales don't like to be classed as "English". You might want to change the title to the more neutral (and correct) Britain, Great Britain, GB, United Kingdom, or UK.

It would be UK, as it includes NI. To the parent - Great Britain is the land mass containing England/Scotland/Wales. The UK is the whole thing.

Good point :-)

Re: The State of JavaScript 2018

#284

Post by megous »

tracker1 wrote: post #248
megous wrote: post #19

Earlier quoted context omitted.

I can't see anything even with their js enabled. Seems like they depend on google analytics and fail if that's not loaded too.

It's easy to wind up in that spot, irritating all the same though. I try to use everything I do with clean degradation with ad-block, etc... only local and/or cdnjs scripts required (if anything).

Me too. I develop with umatrix enabled, with font loading disabled, so that I can catch these problems, etc.

Forces you to use sensible technology, like svg and not fonts for icons, and catch these types of missing optional dependency errors, and not depend too much on a specific font in your design, so that if brwser forces something else, you don't start having overflowing text everywhere.

Re: The State of JavaScript 2018

#285

Post by tabtab »

marcosdumay wrote: post #258
tabtab wrote: post #245

Earlier quoted context omitted.

With HTML Tables, it's easy to switch on the grid (border=1) and see what's really going on. Maybe I'm old fashioned, but WYSIWYG sure the hell made life easier. Unless you are a dedicated UI specialist, you'll probably spend way too much time dinkering with the web UI because it's not WYSIWYG. It's like trying to park an 18-wheeler truck in a normal lot: you can't just "go there"; you have to plan it all out in 7 st…

> With HTML Tables, it's easy to switch on the grid (border=1) and see what's really going on. With CSS it's actually easy to display the grid `\*{border=1;}`. With tables, you have a lot of them, and must go into each line of your page adding that clause.

Then you border-tize all div's. That's messy. I suppose one could write jQuery to filter certain divs, but it's not a universal solution.

Re: The State of JavaScript 2018

#286

Post by BjoernKW »

tracker1 wrote: post #235
nkjoep wrote: post #113

Earlier quoted context omitted.

I've got the same feeling but with bad connotation. React is easy the same way jQuery is. Easy, unstructured, foggy, too much permissive tool. Far too easy to end-up with spaghetti-code. I prefer not using it, Angular is far more organized.

Like another reply. // MyHello.jsx import React from 'react'; export default ({name}) => Hello {name} ; Now do the same in Angular.

"Hello world!" programs or their slightly more sophisticated variation, the to-do list app, aren't a realistic measure when it comes to actual real-world software that has to solve real-world problems.
Post reply on HN