Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Roadmap to becoming a React developer in 2018

github.com

Post reply on HN
Print view View original

41–50 of 153 posts

Re: Roadmap to becoming a React developer in 2018

#41

Post by cutler »

mosdl wrote: post #34
aggronn wrote: post #13

Earlier quoted context omitted.

styled-components is what got me to switch from LESS to css-in-js, and I'm so grateful. Anyone interested learning about css-in-js for the first time would benefit from understanding the styled-components model, but there's already churn in that category, and new libraries inspired by styled-components that take it further. Here's an interesting perspective on the history of CSS-in-JS: https://github.com/streamich/fr…

5 generations to make something that is less efficient (slow build times, caching not always possible) that straight up css processors. Its kinda sad really (but hey my css is in my js file now, so useful).

Yes, notice the trend: web develeoper > Javascript developer > React developer. Soon we'll have CSS developer as a career in itself.

Re: Roadmap to becoming a React developer in 2018

#43

Post by cutler »

sbjs wrote: post #27

This chart is over complicated and I feel like it's meant to throw you off and make you feel like React programming is over complicated, which it isn't. Don't let this scare you away from React. React is simple. Remember, React is just the view layer. You can do whatever you want outside of React. You don't have to buy into anything else. And if you want to, you can buy into them piecemeal. You're not locked into any…

You are my hero for having the courage to say front-end unit testing is optional. Functional testing has served me well for over a decade. Just put your app through its paces and watch what happens. I've copied your post into Vim and will save it in my ~/wisdom folder :)

Re: Roadmap to becoming a React developer in 2018

#44

Post by whatyoucantsay »

cmjqol wrote: post #21
SirensOfTitan wrote: post #12

I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. Learning happens contextually as you figure things out. I see no use to learning half of the things on here that you'll never use. You do risk, however, in the confusing and complex JavaScript landscape, getting paralyzed by choice and never getting off the ground. I shutter thinking about…

> I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. I strongly disagree there. The only way for an engineer to make good decisions as to what tools / framework to pick from is to know and understand as much tech as possible. It is fundamental for an engineer to do this job of tech-watching in order to not become religious and blinded by th…

I'd much rather work with a developer proficient with C, Java, JS, React, DDD and a deep knowledge of Unix than someone who has spent the majority of their time on JS, Backbone/Knockout/Angular/Ember/React/Vue/Mithril, Redux/MobX/Vuex and Grunt/Gulp/Brunch/Webpack.

Knowing how a technology works is important. Knowing technologies needed to accomplish tasks to be done is important. Knowing seven different technologies that accomplish the same thing is at best a marginal benefit.

Re: Roadmap to becoming a React developer in 2018

#45

Post by cutler »

tomc1985 wrote: post #42
cutler wrote: post #38

I'll take Rails + turbolinks over this tangled mess any day.

A thousand times yes! I am amazed that nobody seems to look at that chart and say, "holy shit, how much of this is necessary? how much of this is good?"

I'd love to see a contest between a bunch of devs using Rails + turbolinks pitted against a team using React + Redux + Express measuring how many working apps they could produce in a weekend. I know which team I'd be betting on.

Server-side rendering has to be the biggest joke. I mean you spend half a lifetime mastering the art of pushing everything onto the client and then realise it borks your SEO because it breaks what the WWW is based on - hypertext. So you now have to go back and duplicate everything on the server. That's progress?

Re: Roadmap to becoming a React developer in 2018

#46

Post by [deleted] »

cutler wrote: post #45
tomc1985 wrote: post #42

Earlier quoted context omitted.

A thousand times yes! I am amazed that nobody seems to look at that chart and say, "holy shit, how much of this is necessary? how much of this is good?"

I'd love to see a contest between a bunch of devs using Rails + turbolinks pitted against a team using React + Redux + Express measuring how many working apps they could produce in a weekend. I know which team I'd be betting on. Server-side rendering has to be the biggest joke. I mean you spend half a lifetime mastering the art of pushing everything onto the client and then realise it borks your SEO because it breaks…

[deleted]

Re: Roadmap to becoming a React developer in 2018

#47

Post by brlewis »

pjmlp wrote: post #26
SirensOfTitan wrote: post #12

I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. Learning happens contextually as you figure things out. I see no use to learning half of the things on here that you'll never use. You do risk, however, in the confusing and complex JavaScript landscape, getting paralyzed by choice and never getting off the ground. I shutter thinking about…

As one grows old we learn to avoid learning every new fad until dust settles. I saved a few brain cells by not bothering with GWT, CoffeeScript, mootools, YUI, prototype...

Now is a good time to learn front-end tech. Skipping YUI was good, but you should learn at least one of Mithril, React, Preact, Inferno. I recommend Mithril for learning and React for job opportunities.

It's OK to have skipped CoffeeScript, but you don't want to skip TypeScript in 2018. The past couple of years have been good as it has increasingly harmonized with ES6.

Re: Roadmap to becoming a React developer in 2018

#48

Post by pjmlp »

brlewis wrote: post #47
pjmlp wrote: post #26

Earlier quoted context omitted.

As one grows old we learn to avoid learning every new fad until dust settles. I saved a few brain cells by not bothering with GWT, CoffeeScript, mootools, YUI, prototype...

Now is a good time to learn front-end tech. Skipping YUI was good, but you should learn at least one of Mithril, React, Preact, Inferno. I recommend Mithril for learning and React for job opportunities. It's OK to have skipped CoffeeScript, but you don't want to skip TypeScript in 2018. The past couple of years have been good as it has increasingly harmonized with ES6.

Sure, native front-end tech.

Re: Roadmap to becoming a React developer in 2018

#49

Post by amalag »

cutler wrote: post #38

I'll take Rails + turbolinks over this tangled mess any day.

Absolutely. There are so few places where you actually need an SPA. And now with form_with doing remote forms by default and getting inline responses from the server it is a real stretch for someone to say they absolutely need some of these JS frameworks to get some simple non page load functionality.

Re: Roadmap to becoming a React developer in 2018

#50

Post by amalag »

cutler wrote: post #45
tomc1985 wrote: post #42

Earlier quoted context omitted.

A thousand times yes! I am amazed that nobody seems to look at that chart and say, "holy shit, how much of this is necessary? how much of this is good?"

I'd love to see a contest between a bunch of devs using Rails + turbolinks pitted against a team using React + Redux + Express measuring how many working apps they could produce in a weekend. I know which team I'd be betting on. Server-side rendering has to be the biggest joke. I mean you spend half a lifetime mastering the art of pushing everything onto the client and then realise it borks your SEO because it breaks…

Exactly what Sam Stephenson talked about here: https://youtu.be/SWEts0rlezA?t=6m36s
Post reply on HN