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.
State of JavaScript 2019
61–70 of 372 posts
Re: State of JavaScript 2019
#62Wow, 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…
[deleted]
Re: State of JavaScript 2019
#63The state of Javascript in 2019 is that it should be deprecated. I have never had more problems, undefined behavior, mysterious errors and malfunctions, dependency hell and generally shitty syntax as when dealing with Javascript. God, please, just destroy this language. The web needs something different, something not broken and flawed.
A friend of mine worked on JavaScript at Netscape. He says he's sorry.
Re: State of JavaScript 2019
#64Interesting that GraphQL is slowly gaining interest - I kind of thought the hype would fizzle out. Good to also see Typescript making a foothold - it's a great alternative to pure JS.
I've rarely seen a technology so eagerly embraced by both bleeding edge tech enthusiasts and also enterprise behemoths (granted, tech behemoths, but still)
Having API documentation that is guaranteed not to go out of date with your code. Having a shared standard for describing your endpoints in a machine-consumable way. Being able to automatically generate typescript types from any schema (correct me if I'm wrong but I don't think there's any tooling that would do the same for arbitrary REST APIs). Being able to get autocompletion when writing queries for free ^ Those were all things I didn't know I needed until I started using them, and like Typescript, it feels painful to go back to not having them
Re: State of JavaScript 2019
#65I dream of an alternate timeline in which today we would release "State of ClojureScript 2019" with Javascript being listed as a ClojureScript flavor :)
Re: State of JavaScript 2019
#66Do other languages do these types of surveys? e.g. is there a "State of Python 2019"?
Java (2018, 10500 responses) https://blogs.oracle.com/javamagazine/the-largest-survey-eve...
Re: State of JavaScript 2019
#67Wow, 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'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 performance (paint, composite, layout) they rarely–if ever–even get your point.
Most applicants we get don't even understand basic HTML semantics. I mean, shit, I've seen applicants submit their application projects with EVERYTHING being a div-element. Including links and buttons, which would have onClick events...
The technical aspect of frontend development allows backend developers to bleed into the frontend. "Oh, look, typescript! Finally JS looks like Java! Which means that silly HTML and CSS is going to be easy!"
Buzz off back to the backend, you strong-typed clown who doesn't understand what UX and a11y mean.
I could go on and on about the horror that is typescript. But that's for another day. I know most people love it. I fucking hate it. I'm using it, because I have to, but I never needed it. It literally offers me nothing of value.
But on topic: CSS experts? They are rare. Maybe 1 in ever 30 applicants can actually claim that level of knowledge.
Re: State of JavaScript 2019
#68I'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.
It takes 1 afternoon to learn React and it never requires you to open the doc again.
Angular, on the other hand...
Re: State of JavaScript 2019
#69Do other languages do these types of surveys? e.g. is there a "State of Python 2019"?
• Go 2019 — https://blog.golang.org/survey2019 (survey only) • Go 2018 — https://blog.golang.org/survey2018-results • Go 2017 — https://blog.golang.org/survey2017-results • Go 2016 — https://blog.golang.org/survey2016-results • Rust 2018 — https://blog.rust-lang.org/2018/11/27/Rust-survey-2018.html • Rust 2017 — https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Resul... • C++ Global Insights 2019 — https://isocp…
Re: State of JavaScript 2019
#70I'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.
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 whatever you want as you go.
The JSX syntax is infinitely more intuitive compared to the Angular way of doing things. Which also gets me to the point of Angular having a specific way of doing things, "the Angular way".
With React there's less thinking required to get things done. The learning curve is steep (as in: you pick up the knowledge quicker) because the amount of information to take in is relatively low.
Angular takes months to master. It's very opinionated. And it requires typescript.
I for one hate typescript with the passion of a thousand suns. I know it very well because I have to if I want to keep my job, but it's so freaking unnecessary...