Website looks crisp and nice. Wondering if the source code for the site is available?
The State of JavaScript 2018
161–170 of 286 posts
Re: The State of JavaScript 2018
#162Earlier quoted context omitted.
Loved? Well, it's a point of view. I personally hate it, due to the tooling and the dependency management (npm and yarn are catastrophic, an "hello world" example with React downloads on average more than 100 packages).
What's 'catastrophic' about Yarn?
Not exactly Yarn or NPM. The problem is that JS is suffering from extreme dependency hell, due to overly fragmentation of modules. It's appalling. It is not a good thing starting a project, doing a install and having hundreds and hundreds of modules on node_modules, some with less then 50 lines of code. Of course things must be modular, but unwraping everything in a folder like this is far from good.
Re: The State of JavaScript 2018
#163People 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…
Rust do a survey, https://blog.rust-lang.org/2018/08/08/survey.html
Re: The State of JavaScript 2018
#164Earlier quoted context omitted.
Is there any reason to suspect Flow users are less likely to do the survey than, say, TypeScript users?
I can speculate here a little bit. Majority of survey users has less than 10 years of experience. That makes them susceptible of being Visual Studio Code users. VSC - Microsoft product. Typescript is Microsoft product as well.
I am curious (as a VSCode user) what makes you conclude that junior devs are likely to use VSCode?
Re: The State of JavaScript 2018
#165One important data point there is Visual Studio Code. It used to be really popular in 2017 (double the popularity of Atom/Sublime/Webstorm), now it's just eating everyone's lunch (triple the popularity of Sublime/Vim/Webstorm/Atom, almost equal to all of them combined). Also Atom is declining sharply. Compare https://2018.stateofjs.com/other-tools/ to https://2017.stateofjs.com/2017/other-tools/
VSCode does everything so well, that it is hard to compete right now. It really was built upon the lessons learned from several others code editors.
Re: The State of JavaScript 2018
#166Earlier 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…
The funny thing is, we've just been finding more and more complicated ways to make table-based layouts ever since, but they're better because they are CSS based? I dunno, I don't have to squint hard at CSS-Grid to see old table layouts peeking back at me.
It could also have to do with no longer requiring, say, a 1x1 invisible pixel...
Re: The State of JavaScript 2018
#167I don't understand what is "Native Apps"? No links are provided. The description is "tools_descriptions.native-apps", on the page https://2018.stateofjs.com/mobile-and-desktop/native-apps , which is probably, a bug. My guesses are: 1) Non-JS mobile native apps built on Java and Swift. 2) Native script https://www.nativescript.org/ 3) Smth idk about.
Most likely it is Non-JS native apps, Java, Swift etc.
Re: The State of JavaScript 2018
#168People 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…
> Angular is dead? Most don't even want to touch it again
Quite the opposite is happening from what I'm seeing. More people seem to move away from React towards Angular, but that's just my anecdotal observation.
Re: The State of JavaScript 2018
#169People 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…
> 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 are you moving into? A: We wanted to retain as much of our backend WCF stuff, while we move our front-end into Angular. F: So has there been a project that was started? A: Yes, we have started to move 8 of our enterprise apps to Angular. F: Any challenges so far? A: Well, the code seems to become a little too complicated for our developers to work on. We'd like to get it to a cleaner and more maintainable state. F: Have you considered other frameworks? A: Sadly, no. Company has invested more than 2 years in re-designing the app. And besides, Angular is backed by Google, hence, we seem to think that it will be the right tool for the business. We've invested a lot of time as well with it. F: But you are saying that productivity overall is low because the complexities of your Angular code base is taking a toll on your developers? A: Yes, in some sort of ways. There are Angular constructs which just does not make sense. And nipping the warnings and errors in the console is just a task that's too heavy and tedious. Although we like the fact that Angular can play nicely with our backend stuff with very minimal changes required on that side.
Practically, the architect was saying that the enterprise adopted Angular due to its immense popularity way back then and being heralded as an Enterprise framework.
Although my friend was offered a very good salary (by Canadian standards), he politely declined the offer, after inspection of some of the code base and the challenges that he would be facing.
Re: The State of JavaScript 2018
#170that salary breakdown must be for world wide, including third world countries... $10K-$30K category?