4 ms·

> The overhead involved in building a react app is nearly nil with all the tooling we have. All the tooling we have is exactly why React has an overhead which

> The overhead involved in building a react app is nearly nil with all the tooling we have. All the tooling we have is exactly why React has an overhead which is far from nil. Every package goes through a period of changing its best practices, some go through multiple. Entire packages go in and out of season, seemingly depending on the phase of the moon. There's a new bundler every year, each with its own quirks. For some things there's 4 "go to" packages that achieve the same thing but take a different path to get there. You have all these packages and tooling you have to learn, stay in touch with, maintain and fight against. All of that so you could ship megabytes of JS that ultimately just changes some text on a page. You can do all of that with vanilla JS and spare yourself the headache.

rmilejczz 3y ago
Strongly disagree npm install -g vite vite init my-react-app npm install npm run dev The most popular build tools have mostly stayed the same. Some things have fallen out of fashion sure like gulp. But overall the abstractions built over complicated tools have only improved and only made it easier to get started with web dev. I’d argue it’s never been easier to start a modern statically typed react app.
willsmith72 3y ago
It takes work to keep up with the latest-and-greatest in modern web frameworks. 100% agree. But if you're already doing that, because you work in the field, or are passionate about it, then that checkbox is ticked. I wouldn't do all that JUST to build a static portfolio, but if you already learnt and kept up with all of that stuff, then I still don't see why not use it.
- sfn42 3y ago
  Because in a professional setting the guy who takes over after you also has to know or learn whatever tech you chose. I worked on a team maintaining solutions in React, Vue, angular, Svelte, JQuery and more. It sucked. Basically every task I ever did there was my first time doing that thing with that framework.
  - willsmith72 3y ago
    I totally agree, simpler is better. Except for extenuating circumstances, teams working anywhere remotely close to each other should aim to stick to the same technologies and practices. If that's vanilla js, sure, go for it. I'm not arguing everyone needs to move to react. I'm saying the opposite. Stick to the tools you know. I once worked in a strict java-angular.js shop, and it was awesome. Everyone was familiar with the tech and the company saved energy otherwise wasted on tool-related decisions. My point is this > it is more of a flex in this SPA era to show you know how to make a website the old-fashioned way. is not valuable to me at all. If I were giving advice to a new programmer, I'd tell them learn the basics first, like your html, js, css, and then familiarise yourself with one of the frameworks. Then if you want to build your portfolio, build it in whatever you like, but for people at that level, it can be a great chance to practice and show off their skills to employers. If you're shipping 2MB, who cares.

rmilejczz 3y ago

Strongly disagree npm install -g vite vite init my-react-app npm install npm run dev The most popular build tools have mostly stayed the same. Some things have fallen out of fashion sure like gulp. But overall the abstractions built over complicated tools have only improved and only made it easier to get started with web dev. I’d argue it’s never been easier to start a modern statically typed react app.

willsmith72 3y ago

It takes work to keep up with the latest-and-greatest in modern web frameworks. 100% agree. But if you're already doing that, because you work in the field, or are passionate about it, then that checkbox is ticked. I wouldn't do all that JUST to build a static portfolio, but if you already learnt and kept up with all of that stuff, then I still don't see why not use it.

sfn42 3y ago
Because in a professional setting the guy who takes over after you also has to know or learn whatever tech you chose. I worked on a team maintaining solutions in React, Vue, angular, Svelte, JQuery and more. It sucked. Basically every task I ever did there was my first time doing that thing with that framework.
- willsmith72 3y ago
  I totally agree, simpler is better. Except for extenuating circumstances, teams working anywhere remotely close to each other should aim to stick to the same technologies and practices. If that's vanilla js, sure, go for it. I'm not arguing everyone needs to move to react. I'm saying the opposite. Stick to the tools you know. I once worked in a strict java-angular.js shop, and it was awesome. Everyone was familiar with the tech and the company saved energy otherwise wasted on tool-related decisions. My point is this > it is more of a flex in this SPA era to show you know how to make a website the old-fashioned way. is not valuable to me at all. If I were giving advice to a new programmer, I'd tell them learn the basics first, like your html, js, css, and then familiarise yourself with one of the frameworks. Then if you want to build your portfolio, build it in whatever you like, but for people at that level, it can be a great chance to practice and show off their skills to employers. If you're shipping 2MB, who cares.