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

251–260 of 286 posts

Re: The State of JavaScript 2018

#251

Post by beefalo »

vyking wrote: post #246
rpeden wrote: post #191

Earlier quoted context omitted.

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 m…

Yes, d3 is loaded by webpack and you can find it in the webpack sources where it is loaded from node_modules.

Re: The State of JavaScript 2018

#252

Post by nobleach »

tincholio wrote: post #172
kabacha wrote: post #36

Earlier quoted context omitted.

As much as I dislike Javascript OP is right. The latest stack overflow survey[1] puts #7 on most loved languages and it's not even in top 25 most dreaded ones. [1] - https://insights.stackoverflow.com/survey/2018#most-loved-dr...

I do wonder how much of that love is from devs who basically only know JS, and have done nothing by web stuff.

I hear a lot of complaining like this from Java devs. Oddly, they are often okay only knowing one language (Java). The exact words from a Java dev were, "well, when all you have is a hammer, everything looks like a nail".

Re: The State of JavaScript 2018

#253

Post by nobleach »

sAbakumoff wrote: post #112
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…

IMHO Angular in its recent versions is the most simple front-end framework ever. It's not even JS anymore. It's type script + reactive framework. Those 2 things makes programming extremely easy.

After having dropped Angular in the 1.3.x days, I was pleasantly surprised by how much it's changed. There are still a few mental concepts a new programmer would have to grasp (DI, observables, OO, type-safety) but overall, it's not too bad. I'm not sure I could call it "simple" though. Maybe I'm conflating simple with "easy". I'm of the few that still believe in Redux though. A one-way data flow, a finite state-machine, a new version of the state on every action.... that just defines "simple" to me. (not arguing at all)

Re: The State of JavaScript 2018

#254

Post by pb060 »

atom-morgan wrote: post #131
esistgut wrote: post #114

Earlier quoted context omitted.

> Angular is dead? Most don't even want to touch it again ( Great ). I don't get the Angular hate. I work with it daily and seems like a productive environment. I did some tests with React and Vue too and couldn't find any relevant advantage. Angular has batteries included tools for a lot of tasks: i18n, routing, isomorphic builds, web components, etc.. You get a cross platform mobile development environment too usin…

I think they could have avoided 90% of their problems by just giving it a different name.

Agree, I can't believe that the company owning the major Internet search engine gave the same name to two different frameworks.

Re: The State of JavaScript 2018

#255

Post by erik_seaberg »

addicted wrote: post #201
untog wrote: post #193

Earlier quoted context omitted.

I'm curious: why is it bad? I very, very rarely have to delve into my node_modules folder to take a look at something.

The leftpad fiasco (which I believe NPM has now mitigated), and the recent security issue where a certain popular package was uploading any passwords it found showed the current dangers with NPM.

The lesson from left-pad should have been to vendor all your deps rather than bet your org on third parties with no SLA commitment to you.

Re: The State of JavaScript 2018

#256

Post by marcosdumay »

srgpqt wrote: post #142
pjmlp wrote: post #103

Earlier quoted context omitted.

React requires too much FP concepts for the typical average enterprise developer. It feels like doing Haskell with JavaScript.

You can write haskell style in any language. but you don’t have to. function MyComponent(props) { return Hello {props.name} }

> You can write haskell style in any language.

It would be great if that was true. The fact is that you can not copy Haskell in any mainstream language (Lisp gets the closest), and that hurts.

Re: The State of JavaScript 2018

#257

Post by marcosdumay »

Etheryte wrote: post #33
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…

Regarding GraphQL, I think the reason is at least partially that there aren't too many applications that actually benefit from the all-dynamic approach of it. It's neat and useful in certain applications, but I wouldn't use it everywhere. The tooling isn't quite there yet also in my opinion, but the friction will probably go away with time.

It's a data access language where data sources are a far secondary concern for the tooling, and it looks like the tooling does not care about access control at all.

The standard looks great, and with some time some useful tools will probably arrive. But not right now.

Re: The State of JavaScript 2018

#258

Post by marcosdumay »

tabtab wrote: post #245
bryanrasmussen wrote: post #30

Earlier quoted context omitted.

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

Re: The State of JavaScript 2018

#259

Post by gagege »

bryanrasmussen wrote: post #120
gagege wrote: post #119

Earlier quoted context omitted.

I think he kind of had a good point. It would be nice to have a single set of tools that can always get the job done no matter what.

yes that would be nice, but then lots of things that do not match reality would be nice.

The second step to making things better is to believe they can and should be improved.

The first step is knowing that the current state of things is deficient in some way.

Re: The State of JavaScript 2018

#260

Post by Etheryte »

nepeckman wrote: post #148

The weirdest part of this survey is in many categories, the most experienced developers (and by extension, the highest paid) were using a less popular technology. Over 50% of people surveyed had heard of ClojureScript and were not interested, but the developers who used it and liked it had the highest average years of experience and highest average salary. Same goes for Ember and Polymer for frameworks, and Relay for…

For some insight, my experience is that oftentimes the more experienced developers are the only ones let near legacy, but valuable projects. Newer developers are often not familiar with the technologies and thus the risk of regression is higher.
Post reply on HN