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

241–250 of 286 posts

Re: The State of JavaScript 2018

#241

Post by Bahamut »

AngeloAnolin wrote: post #169
pjmlp wrote: post #42

Earlier quoted context omitted.

> Angular is dead? Most don't even want to touch it again ( Great ). Yet what I see around me is enterprise customers on our projects adopting Angular as the official internal Framework, as React is seem as too advanced.

Yes, it is quite a fact that enterprise businesses tend to adopt Angular as it has more sort of an enterprise appeal due to its popularity and being backed by Google. I had a friend (F) interview for a FE developer position. He was more of a React adopter and he spoke with the architect (A) of the team. The company was heavily invested into MS technologies (think a lot of WCF Services) F: So, what technology stack ar…

That sounds more like a quality problem of the particular dev shop than an indictment on Angular.

Re: The State of JavaScript 2018

#242

Post by chrisweekly »

remify wrote: post #141
chrisweekly wrote: post #117

Earlier quoted context omitted.

One major reason is that Ng is its own thing. It's not JavaScript, nor HTML. Also, "batteries included" means buying into the whole monolithic framework. The React ecosystem requires more decisions, but also benefits from ability to pick and choose the right libraries for a given project. That said, Angular has some great parts, eg TypeScript and RxJS.

I think people will grow "hating" React because of the ease of use. Just like JS and PHP. I weep for the people that will maintain all the React mess that is being created. React is great, but the current ecosystem has too much liberty for too many junior dev using it. Angular being a framework has a lot to offer in term of maintainability and good practices.

A couple good points. I agree w/ your 2nd and 3rd sentences. That said, I'm personally glad I invested in React and its ecosystem.

Re: The State of JavaScript 2018

#243

Post by lostgame »

ksec wrote: post #18

People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…

>> And my biggest surprise is how Javascript turned from one of the most hated programming language ( besides PHP ? ) into being acceptable and loved.

For real?

I personally think JavaScript is awesome.

I personally think jQuery is awesome.

And I feel really alone a lot of the time in these opinions. I see a lot of disdain for JS here in comments in particular.

I also see a lot of people browsing with JS disabled, and who complain when a site doesn't function without it.

Re: The State of JavaScript 2018

#244

Post by chrisweekly »

ticmasta wrote: post #216
jakelazaroff wrote: post #206

Earlier quoted context omitted.

I find the "build your own framework" aspect of React to be as much a curse as it is a blessing. You can skip some of the bloat, but you also have to kludge together multiple libraries of varying quality to get the same things you'd get out of the box with a "batteries included" framework.

especially for new developers and organizations. You have a choice between a wide-open landscape and a script that you're deathly afraid to eject because you can never go back. Neither is great for someone considering adoption for a new commercial product.

Yeah, I hear you about the "eject" problem for create-react-app. In CRA1, react-app-rewired emerged as a reasonable approach to no-eject config extension, but CRA2's switch to Webpack 4 (itself having moved towards zero-config) broke almost all the rewired plugins. There are solutions in the works (eg babel-plugin-macros), and alt approaches like Neutrino, but timing is tough right now as there isn't a clearly-established and well-lit path for good defaults plus low-maintenance config.

Re: The State of JavaScript 2018

#245

Post by tabtab »

bryanrasmussen wrote: post #30
LandR wrote: post #12

> JavaScript is always changing. New libraries, new frameworks, new languages… It's part of the fun, No.. NO, it isn't.

I'm reminded of back in 1997 (maybe 98, anyway long time ago), I had been on a JavaScript course with a British guy, and went over to his house. He showed me the little cv site he'd been working on, it had quite a nice design, much better than I would ever do if asked to design something. I looked at the code - it was all tables, so I decided to show him CSS at the end of which he thunderously proclaimed "That's what…

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 steps and hope it all works. Bicycle science is now rocket science. I'd like scientific proof "it must be this way" to get whatever wonderful benefit non-WYSIWYG has. Device size handling? Make 2 UI's: fat and skinny; that's easier than parking the 18-wheeler.

Re: The State of JavaScript 2018

#246

Post by vyking »

rpeden wrote: post #191
vyking wrote: post #176

budding dev here! I'm so impressed with the :onhover action of 'Start' button of https://2018.stateofjs.com/ Can anyone provide me a direction how to achieve that?

First, see if you can figure out how to animate the boxes the way they are when you're not hovering over start: they're moving around the screen in a straight line until they reach the edge of the screen. The animation we're looking at is moving SVG boxes around the screen, so if you search for tutorials about how to animate SVG with JavaScript, you'll quickly figure out how to make the animation happen. Although the…

@rpeden: Thanks a lot for such detailed explanation! This is exactly what I wanted. I didn't even think that when I hover on 'Start' each box will have to come back with different velocities! Stupid me :P

And I really liked the idea of not putting a codepen -'think you know what's going on without really understanding it' - I totally agree and that has been happening quite a lot to me!

Just one more question - if I may! In the 'Connections' page, the graph looks a lot like D3js interactive 'Chord Diagram'. But I don't see d3js mentioned in tags. Is this due to the webpack that it's possible to hide the underlying dependencies? I'm sorry if this is a dumb question - I've never used webpack.

Re: The State of JavaScript 2018

#247

Post by tracker1 »

no_gravity wrote: post #146
vanderZwan wrote: post #145

Earlier quoted context omitted.

Fair point. I genuinely wasn't sure how to best compare it (also, I'm sure that growth slows down once a majority of users is awawre of your product, further muddying the picture).

Agreed. If I was to place a bet on which framework will grow faster over the next year, I would pick Vue.

I think React has pretty much reached saturation in terms of raw percentage. I think Vue is going to continue to erode from Angular. Also, I'd be surprised if a revised Polymer didn't see some growth since the other browsers are now starting to support a lot of the vdom features.

Re: The State of JavaScript 2018

#248

Post by tracker1 »

megous wrote: post #19
bigiain wrote: post #8

I guess people with javascript turned off are not the target market for this site, but I found this humorous: http://tinypic.com/view.php?pic=2v31s94&s=9#.W_KD0idx2Rs

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).

Re: The State of JavaScript 2018

#249

Post by liquidcool »

It seems to me that like last year, several countries with very large developer bases are underrepresented. I'm thinking of India and the Philippines in particular, where English is not an issue. I'm an American, but I'd like to get a good global picture.

In addition, it would be good to see other indicators such as downloads, jobs (admittedly hard to measure accurately), BuiltWith trends, etc. Considering the millions of front end developers, this seems a very small sample size.

Post reply on HN