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

State of JavaScript 2019

2019.stateofjs.com

Post reply on HN
Print view View original

251–260 of 372 posts

Re: State of JavaScript 2019

#251

Post by jermaustin1 »

irrational wrote: post #237
Chyzwar wrote: post #196

Earlier quoted context omitted.

That ok, but these people need to stop labelling themself as experts. It makes difficult for true experts to stand out.

Maybe experts don't call them selves experts. I have a friend that had some home remodeling work done, poorly. The friend said to me, "But, they were professionals!" I responded, "Well, that's the problem. A professional is someone who will do the least amount of work in the least amount of time for the most amount of money. If you want someone who actually cares about the work, hire a craftsman instead of a professi…

Yeah, this expert prefers Guru. /s

Re: State of JavaScript 2019

#252

Post by BiteCode_dev »

irrational wrote: post #237
Chyzwar wrote: post #196

Earlier quoted context omitted.

That ok, but these people need to stop labelling themself as experts. It makes difficult for true experts to stand out.

Maybe experts don't call them selves experts. I have a friend that had some home remodeling work done, poorly. The friend said to me, "But, they were professionals!" I responded, "Well, that's the problem. A professional is someone who will do the least amount of work in the least amount of time for the most amount of money. If you want someone who actually cares about the work, hire a craftsman instead of a professi…

Well, it is said that a wise man never calls himself a sage. Others do.

Re: State of JavaScript 2019

#253

Post by rustybolt »

5350-uiop-1130 wrote: post #21

Wow, 39.9% of respondents mark themselves as "Expert" at CSS. I've been doing front-end in various guises for 12 years and I would only rank myself maybe 5 or 6 out of 10. As I've gotten more experienced in my career I've become more aware of what I don't know as opposed to what I do know. It's funny that "Advanced" is mastering animations and transitions whereas "Expert" is being able to develop a full-front end con…

I'd guess it is because the basis of CSS is pretty simple.

"You have selectors and styles, and I can just can look them up, so I guess I know all there is to know about it."

Re: State of JavaScript 2019

#254

Post by tashoecraft »

buu700 wrote: post #248
fuzzy2 wrote: post #150

Earlier quoted context omitted.

Maybe because React is small (API surface) and does (or is felt to do) “one thing”. It is easy to wrap your head around it, even without fully understanding, say, the Virtual DOM diffing. Angular is very different in that regard. I recently had to read up on how Angular applies changes to the DOM. It was extremely difficult to get this information at all. For me, React with TypeScript is king. It trumps Angular in th…

* Angular templates are typed, but until version 9 (coming out in a couple weeks, but I've been using the RCs and they've been fine), any variable created in the template itself was defined as `any`, creating gaps in the compiler's coverage. A vscode plugin provides IntelliSense. * Agreed, this is an awful default and I don't understand why the Angular team hasn't already deprecated it. I suppose a slightly simpler "…

I think angular with zones will slowly start to fade away as the community moves more towards onPush components, with components hooks to trigger change detection. There is an ngrx proposal for a component that would handle this all nicely, but it's still only a proposal.

Re: State of JavaScript 2019

#255

Post by [deleted] »

stupidcar wrote: post #144

State of JS is always a fun and interesting survey, but I am wary about drawing conclusions from its results because of the self-selecting nature of the participants means they are probably not a representative sample of JS developers in general. They're inevitably going to trend towards English-speaking developers who read coding news sites, participate in social media.

[deleted]

Re: State of JavaScript 2019

#256

Post by abhas9 »

deathtrader666 wrote: post #6

EmberJS should not be in the "avoid' section.. it is one of the most well thought-out framework which just gets the job done.. and it is a bit contra-indicatory that Ember guys are the highest paid.

Agreed. Anyone who has not tried Ember should check out their getting started guide: https://guides.emberjs.com/release/getting-started/quick-sta.... Also, I highly recommend `ember-concurrency: An Ember Addon that makes it easy to write concise, robust, and beautiful asynchronous code.`

Re: State of JavaScript 2019

#257

Post by tashoecraft »

tannhaeuser wrote: post #117
734129837261 wrote: post #70

Earlier quoted context omitted.

Angular ng-is ng-very ng-opinionated and requires a ton of boilerplate knowledge. It requires typescript knowledge, and I've noticed that (finally!) a lot of developers are realising that typescript actually doesn't make life easier at all. React, on the other hand, is a very intuitive library instead of an all-encompassing framework. You can easily setup a React application in a few seconds and get started, adding w…

Just the other day I had a look at a friend's customer Angular project. My eyes! I knew Angular from past experiences, but once again it stuck out to me that Angular devs tastelessly found it necessary to equip HTML with additional meta-syntax such as parens and asterisk as part of attribute names. Now I can get that some people dislike markup languages (SGML/XML), but going in there and invent a whole new syntax on…

I probably wouldn't go around discrediting a large group of extremely knowledgeable devs with extensive experience. My opinion is generally, if I see something a ton of people have spent countless hours building and I think it's stupid, I should atleast think about why.

Angular uses parens to bind to existing element classes, so if you use an html element, and it has a src field, you want to pass a string just do the normal src="string" you want to pass something from javascript [src]="variable". Boom, you just learned the biggest part of angular template syntax, congrats. This allows for using any existing element, or newly developed elements, web components, without worry about clashing, (jsx class...).

I do agree they went a little to heavy with OOP thinking, it's a weird balance between the functional reactive pushed by rxjs, and a more classic OOP line of thinking. I believe Angular will move more towards a functional way of developing as the team is coming off of the rendering refactor, ivy, and the community is working on the functional reactive component.

Re: State of JavaScript 2019

#258

Post by chasd00 »

gherkinnn wrote: post #77
734129837261 wrote: post #67

Earlier quoted context omitted.

I've been taking job applications from other frontend developers in the Silicon Valley fortune 500 area of work. Most resumes that get past the initial recruiter interview and make it to a tech review and claim expert knowledge of CSS... They don't. They don't know shit. They can often not answer basic flexbox questions. Not to mention CSS grid questions. And if you start questioning them about CSS animation performa…

CSS is just key-value pairs. How hard can it be? /s There is absolutely an air of arrogance when people approach seemingly simple things such as styling. And then they implement all sorts of atrocities.

You see this arrogance everywhere and it's really annoying. The classic joke about it is the "..first assume a perfectly spherical frictionless horse.." one.

or https://en.wikipedia.org/wiki/Spherical_cow

Re: State of JavaScript 2019

#259

Post by hateful »

samspenc wrote: post #61

I'm surprised to see Angular drop in ratings and rank so poorly compared to React. I personally prefer Angular myself because it's (a) opiniated and (b) has everything included (HTTP REST calls, Material UI, etc). Just curious why so many people prefer React and mark it so positively.

Personally, I've switched from angular to vuejs after angular 2 (3, 4) came out. I found that vuejs was a better update from angular 1 than angular 2 was.

Re: State of JavaScript 2019

#260

Post by kabes »

fatbird wrote: post #243
kabes wrote: post #166

Earlier quoted context omitted.

Meteor 0.8 was released in 2014, and I'm sure your app would still work on the latest Meteor release without much changes, while in the meantime offering all the latest JS features (JS in 2014 was a completely different world). How many other JS build tools & frameworks from 2014 can say the same?

Good lord has it been that long? It's on Meteor 1.6 now, and you'd be mistaken about "much changes". Blaze to React was a nearly a rewrite; Atmosphere packages to npm was a significant change for the internal dependencies we developed; removing the custom file loader itself that preceded Atmosphere packages meant touching every single file. The original code might have still worked, but the code would be helplessly o…

But if you had picked any other tool from 2014, you'd probably also be stuck with a legacy code base now, without any clear transition path except a big bang rewrite. You would have probably picked angularjs or backbone back in 2014 and a switch to react would have been even more trouble. Meteor allows you to mix blaze & react, mix atmosphere & npm packages, mix their old module systems with commonjs and ES6 modules.

We made the same transition, but just replacing one package/ui part at a time when it suited us, so we always kept releasing new features each sprint while gradually modernizing our code base.

Post reply on HN