I wish “salary” wasn’t the way people were asked about pay. Everyone I know who’s over 200k only has 1xxk salary and like 100% of that in stock compensation. It’d give a different picture of what more people are making.
State of JavaScript 2019
121–130 of 372 posts
Re: State of JavaScript 2019
#122Earlier quoted context omitted.
What’s with all the TS hate?
In my experience, people who have been experts on JS before TypeScript became a thing hate it. - It doesn't give them any advantages, while severely limiting their options and workflow. For newer developers with background in other languages it is quite nice though.
For developers coming from other languages, typescript and the tool support in VS Code is what makes frontend engineering tolerable these days. A big difference with just a few years ago. I insist on it in most projects I'm responsible for. I see no good technical reasons not to use it at this point.
Re: State of JavaScript 2019
#123Earlier quoted context omitted.
I don't know how any sane person could have picked to use it in their project over MobX.
MobX adds a weird new syntax to JavaScript. I don't see why anyone would want that.
What syntax is that? Decorators?
Why use mobx? To write less boilerplate? To be more productive?
Re: State of JavaScript 2019
#124Redux has the largest shift towards "negative opinion" out of all technologies. Did people just get fed up with the boilerplate or is there something else going on?
Hi, I'm a Redux maintainer. There's been a lot of reasons for a shift in opinions over the last few years: - Redux is well past the initial burst of enthusiasm in the "hype cycle" - As you mentioned, there are a number of common concerns expressed by a lot of folks, most of which revolve around "boilerplate" - There are now a wider variety of other options that overlap with ways you'd use Redux: React's Context and H…
How do you feel about runtime type checking and model validation in Redux? Will that ever be a thing? This is the killer feature that made me abandon it for MobX State Tree.
Re: State of JavaScript 2019
#125Earlier quoted context omitted.
A friend of mine worked on JavaScript at Netscape. He says he's sorry.
Thanks, I appreciate it as I go on to the third day of trying to find why Javascript cannot get the correct width of an image but only under some circumstances unconnected to the JS code.
Maybe sometimes it is not loaded yet? (Just a wild guess)
Re: State of JavaScript 2019
#126The 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.
Tell me about it. I have tried my darndest to use types and tests to make things predictable. But there is always something that comes up. It might be Javascript itself. It could also be the endless permutations of environments(browsers, resolutions, devices, etc) that we have to cater to. Front End Web Development is hard.
It would be much easier without the moving target of new Javascript features that browsers have to keep up with. With a real, mature, nonbroken language there would be no need to add new features every year. Someone said that Python is badly suited for the web because not event-oriented, whatever that means. Well, JS didn't have async/await until recently, and there's still lots of code that uses promises, yet even promises aren't supported by ancient browsers. It would have been so much easier to use a language that had ironed its sophomore mistakes somewhere on the desktop, before the web limelight. Instead, they created an all-new "web language" to ensure decades of volatility and reinventing the wheel for all the world wide web...
Re: State of JavaScript 2019
#127Re: State of JavaScript 2019
#128Earlier quoted context omitted.
Thanks, I appreciate it as I go on to the third day of trying to find why Javascript cannot get the correct width of an image but only under some circumstances unconnected to the JS code.
Maybe sometimes it is not loaded yet? (Just a wild guess)
Yes, that's the typical explanation, but no, the images are most definitely loaded, thanks.
Re: State of JavaScript 2019
#129Wow, 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…
(Survey author) yes, it seems like I made a mistake with the different level descriptions. For me knowing how to do things like transitions and animations is comparatively "simpler" than being able to architecture an entire CSS front-end including managing a design systems, naming, specificity, etc. but I guess many respondents didn't see things that way.
> "(Survey author) yes, it seems like I made a mistake with the different level descriptions. For me knowing how to do things like transitions and animations is comparatively "simpler" than being able to architecture an entire CSS front-end including managing a design systems, naming, specificity, etc. but I guess many respondents didn't see things that way."
So you spun up a survey with questions based entirely on personal anecdata, and subjective ideas of what expertise is? And now it's the "State of JS in 2019"? I'd say that's quite awkward. Wouldn't you agree?
Re: State of JavaScript 2019
#130What a holy mess is the landscape of the testing frameworks, even worse than that of the front end frameworks itself.
Jest with Enzyme/react-testing-library seems to be consolidating things in the way React did for frameworks. It's batteries included, and everything "Just Works".