5 ms·
Isn't it easier just to learn ES7, use async/await whenever possible, learn how to do div display=none/block, read some CSS tutorials and forget about learning
by bitL 3y ago
Isn't it easier just to learn ES7, use async/await whenever possible, learn how to do div display=none/block, read some CSS tutorials and forget about learning any JS framework?
- duxup 3y agoFor a page with a couple forms sure. For an application with state and such, maybe not.
- bitL 3y agoIt's easy to make your own SPA using div display: none/block, so is routing. Global store is also pretty easy to do including update events. Async/await makes backend calls super simple, one could still use promises for a few more advanced cases as well, or even go full Saga pattern. Why is a framework needed these days?
- pwb25 3y agothen everyone who joins your company gonna learn this home made framework?
- bitL 3y agoThere is no framework. Just simple JS calls and bindings to HTML with somebody defining REST or GraphQL backend. And some eye candy CSS. The point is that with ES7+ JS can be finally readable and not a spaghetti code monster so anyone can easily understand and extend any code.
- pwb25 3y agogood luck with that
- duxup 3y agoIt really sounds like you don’t have any need for a framework and so of course it doesn’t seem like you need it.
- bitL 3y agoI was involved with some deep React apps that utilized all kinds of advanced patterns and I simply don't see the need for most apps I see around. React is neat if you have thousands of concurrent updates coming in all the time where dependency graph is a killer. But only a few companies need it - why then force this on all frontend devs by default? It's like with big data - let's push everything to Hadoop/Spark when our SQL database fits into 20MB etc.
- duxup 3y agoThere are a lot of sites that use react that don’t need it. Some uses benefit from a good framework.
- NERD_ALERT 3y agoReact is an industry standard tool. If you want to have relevant frontend skills you should know React.
- bitL 3y agoTell that to authors of angular, svelte, nuxt etc. They are all obviously missing something.
- suddenclarity 3y agoHe's saying you should know it since it's industry standard, not that it's always best.
- rafark 3y agoI don’t like this suggestion. I mean, it’s a good, solid suggestion. But I don’t like everyone using the same thing. A market dominated by a single entity means less competition which means less innovation. If we didn’t have competition we’d all still be using jquery.
- NERD_ALERT 3y agoI agree, but also I think it’s fair to say many FE jobs today are basically React dev jobs. I was really excited about Elm, but it seems like that’s not gonna take off.
- pjmlp 3y agoRelevant frontend skills is what the browser supports, that will stay the same regardless of ASP.NET, Spring, Rails, PHP, express....
- mablopoule 3y agoAs a long-time Angular user I had the exact same feeling, and was glad when I finally could switch job to one with a React and Next.js stack. Which is when I truly discovered the state of the React ecosystem, and noped the f*ck out of it. Design systems that recreates the <strong> tag but with a React component, the abomination that is CSS-in-JS and "typed CSS", mixed with some of absolutely brilliant libraries with well-thought out APIs, mixed with "best practice" du jour made by clueless frontend devs rehashing arguments in a truly blind-leading-the-blind fashion. And I do like React, and might probably use it again, but it has the downside of being the defacto choice for new devs, which creates a huge spread in the ecosystem quality that other "second languages" ecosystems such as Rust or Elixir won't tend to have. (I know that I'm mixing a framework with a language, my point also stand for the whole JS/node ecosystem, just doubly so when you focus on the React side of the NPM ecosystem.)
- rafark 3y agohttps://cdnmetv.metv.com/z50xp-1619719725-16226-list_items-no.jpg https://cdnmetv.metv.com/z50xp-1619719725-16226-list_items-n...
- andix 3y agoLearn a a frontend framework first, and once you know all their tricks you can go back to vanilla js.
- jon-wood 3y agoSure, why not? I assume you’re volunteering to rewrite however many billions of lines of Angular are in the wild in that manner.
- bitL 3y agoIf it makes my app simpler, sure. It often does.