It would be cool to see the same thing for VueJS just to get a sense of how much work one is versus the other.
Roadmap to becoming a React developer in 2018
51–60 of 153 posts
Re: Roadmap to becoming a React developer in 2018
#52There is missing just one point: prepare that in 2019 most of the things will be different, the rest will be obsolete.
Re: Roadmap to becoming a React developer in 2018
#53I'm torn. I don't think the aim should be "become a ${framework} developer" but just become a solid programmer with specialization in front-end technologies. If I needed to bounce out of front-end and into another tech role, I wouldn't have too hard of a time because I'm familiar with more than Javascript (I started learning programming with Ruby and Rails, but got my first professional gig doing analytics/seo). I fe…
> become a solid programmer with specialization in front-end technologies. Sure. In this case I would write that as "Software Developer with experience in Javascript, HTML, CSS, and React". Well... You could probably replace that with "Frontend Developer with experience in React". Except that React is a frontend framework, so you might as well simplify that as "React Developer". And now we're back where we started.
Nope, no, nah you really can't. I know React developers who do not know fundamental Web APIs.
Selling yourself as a "React Developer" has connotations to me; subtlety in all aspects of life has repercussions.
Re: Roadmap to becoming a React developer in 2018
#54Earlier 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…
It's a complicated issue because it of course depends on how reliant a product is on SEO. Maybe certain pages that bring in views from search engines shouldn't be part of the same client-side application in the first place, but if it must be then the developers have to decide if they're building a SPA to actually hand off workload to the client or because they want to use React. :)
But to the point of the person you were replying to, we definitely overcomplicate web development these days. There are some good reasons for this, like the fact that there's so much competition to contend with(so we all feel like we have to be rockstars), but it's good to remind ourselves that the end goal shouldn't be focused around the tools.
Re: Roadmap to becoming a React developer in 2018
#55Earlier quoted context omitted.
> 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…
Strong disagree to your strong disagree. I understand right tool for the right job, but for the job of"front end framework" React vs Angular isn't hammer vs screwdriver, or even sledge vs ball peen - it's like Dewalt vs Milwaukee, claw hammers both. For a given class of problem, your comfort with the technology will outweigh the edge cases you hit with one choice vs another. So pick your favorite hammer, screwdriver,…
React is a view library that doesn't even provide a way to do XHR requests. Angular is a complete framework. They are very much hammer and screwdriver, completely different and incomparable tools.
There seem to be a lot of people thinking front-end is just a mess of different options all doing the same thing. And the same people show little understanding of the complexities and nuances of front-end solutions.
Re: Roadmap to becoming a React developer in 2018
#56Earlier 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.
This Time It's Different™
No thanks :D
Re: Roadmap to becoming a React developer in 2018
#57There is missing just one point: prepare that in 2019 most of the things will be different, the rest will be obsolete.
Actually, no. I started working in React about two years ago and if anything, I think the ecosystem in the OP map has stabilised somewhat. I think that SASS use is starting to fade and grid layout is now a thing but not like the whole gulp to grunt to webpack thing. Plus create-react-app makes starting easier.
What frustrated me is that management had no idea of all the bases you needed to cover and expected me to be a backend dev and performant in Java, Spring, Elasticsearch and a whole variety of other things in Java land.
Re: Roadmap to becoming a React developer in 2018
#58Earlier quoted context omitted.
Don't throw away jQuery just yet.
Especially with the way Safari is being developed, I'm guessing we're going to go back to needing a jQuery library to handle all the browser inconsistencies.
jQuery does a whole lot more than just handle browser inconsistencies. I feel like a shim to the standard DOM API would be better suited for solving that problem. The DOM API has grown a lot.
Re: Roadmap to becoming a React developer in 2018
#59Earlier quoted context omitted.
Strong disagree to your strong disagree. I understand right tool for the right job, but for the job of"front end framework" React vs Angular isn't hammer vs screwdriver, or even sledge vs ball peen - it's like Dewalt vs Milwaukee, claw hammers both. For a given class of problem, your comfort with the technology will outweigh the edge cases you hit with one choice vs another. So pick your favorite hammer, screwdriver,…
React is a view library that doesn't even provide a way to do XHR requests. Angular is a complete framework. They are very much hammer and screwdriver, completely different and incomparable tools. There seem to be a lot of people thinking front-end is just a mess of different options all doing the same thing. And the same people show little understanding of the complexities and nuances of front-end solutions.
OK, to be explicit: React ecosystem vs Angular. The difference between to two is how to separate the concerns - inside on large package or into an ecosystem.
I work primarily in Django. I could have given the same comparison of Django vs Flask. The pedant would say flask doesn't have an ORM, and would be correct.
Given the context of this article and HN in general I thought the shorthand referring to React generally would be understood.
Re: Roadmap to becoming a React developer in 2018
#60Crazy to me how far we’ve come from HTML and some script tags. Part of me is really sad that the web is big and complicated and ugly now. I just don’t have the patience to read some new framework author’s long winded and grandiose tutorial and ode to themselves. Why is it so hard to do seemingly simple things? I can remember 10 years ago training up someone with no programming experience at all to competency in a few weeks, on the job. They had to learn HTML, some CSS, Perl, and JavaScript was left for extra credit.
Something is very, very wrong if you now need to master dozens of technologies to add the same value to the world you used to be able to 10 years ago without so much effort. And before someone says it the applications were of similar complexity and scope to today’s SPA behomths.
Too many cooks in the kitchen!