Earlier quoted context omitted.
My "secret" weapon against tooling creep is https://parceljs.org it really lives up it its tagline.
I wish that was true.
It is :)
The State of JavaScript 2018
231–240 of 286 posts
Re: The State of JavaScript 2018
#232Earlier quoted context omitted.
> 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.
When having a few conversations a few years ago with enterprise devs, the React license was seen as a problem[0][1], and Angular wasn't, so the default path was from the top-down to go with Angular, for those I spoke to. This was also when Angular 2.0 was new and the comment was also "This is moving too fast". Once enterprise chooses a tool, that tends to stay the tool for that project, then all of the team is compet…
While 2+ is definitely better, I would still prefer to never use it again. To me, React + JSX is the most natural abstraction for component development. Vue is probably second, but tends to introduce complexities that make things harder for mid-large apps imho.
Re: The State of JavaScript 2018
#233Earlier 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} }
import React from 'react';
export default ({name}) => Hello {name}
;
Re: The State of JavaScript 2018
#234People 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…
And my biggest surprise is how Javascript turned from one of the most hated programming language ( besides PHP ? ) into being acceptable and loved. I enjoy modern JS myself, but I'd be careful about coming to a conclusion like that based on this survey. All it tells us is that JavaScript is very well liked among people who wanted to take the time to complete the State of JavaScript survey. People who dislike or hate…
[deleted]
Re: The State of JavaScript 2018
#235Earlier quoted context omitted.
as someone who tried Angular and was so relieved with the simplicity of React, I have no idea how they can come to that conclusion. But then again, I'm not very well know with the field of enterprise customers
I've got the same feeling but with bad connotation. React is easy the same way jQuery is. Easy, unstructured, foggy, too much permissive tool. Far too easy to end-up with spaghetti-code. I prefer not using it, Angular is far more organized.
Like another reply.
// MyHello.jsx
import React from 'react';
export default ({name}) => Hello {name}
;
Re: The State of JavaScript 2018
#236People 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.
I keep repeating myself here...
import React from 'React';
export default ({name}) => Hello {name}
;
Re: The State of JavaScript 2018
#237Website looks crisp and nice. Wondering if the source code for the site is available?
https://github.com/StateOfJS/StateOfJS. It's in the surveys/2018 folder
Re: The State of JavaScript 2018
#238People 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.
Of the several dozen people I know who've used Angular and React, I know only one that would prefer Angular. Also the only one that would use Angular over Vue with experience in both.
Re: The State of JavaScript 2018
#239One 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/
This makes total sense too. I was so hesitant to use something besides Sublime forever, then I tested out Atom and it was slow (this has probably since been improved) and didn't offer much more so the trade off wasn't worth it for looking pretty. Bounced around a few others and then thought I'll try out the VSCode thing, hooked right away and it seems to keep getting better.
After Atom and Brackets, I almost didn't even give VS Code a try... I'm really glad I did... everything I want in an editor (except maybe binary/hex mode). Integrated terminal and the directory tree are hands down my favorite features, I've seen the directory tree before, but never as good an integrated terminal..
Re: The State of JavaScript 2018
#240Ah, it's that time of the year again – always enjoy seeing where the JS ecosystem is moving. I would like to see two categories added for next year's survey: 1. Auth – would be interested to see if Passport is still the tool of choice 2. ORM – curious how Sequelize, Knex/Bookshelf, Objection, etc. compare in usage. I understand this survey will obviously skew towards frontend tools, but some of the categorization jus…
1. working on some of that now, going to hand-roll multi auth combined with password logins. I don't want to outsource my actual users' authentication beyond oauth to FB/Twitter etc.
2. I don't. If it's SQL, I use a tagged template string library, and just project from the response of the given library. If it's mono or similar, I don't see the point so much. I understand you can use type checking, but you can still do that at the API layer.
As to the data layer, I agree... client side libraries and abstractions should be different from server-side tech... though there's some overlap (libraries that sync client-server for you).