3 ms·

I never jumped into the React wagon, just as I never took the Wordpress train. You do not hire an 18-wheeler to deliver a pizza. Engineers on any subject have o

I never jumped into the React wagon, just as I never took the Wordpress train. You do not hire an 18-wheeler to deliver a pizza. Engineers on any subject have one job: design the optimal solution, be it a bridge or an SPA to take online orders. React makes sense for FB's bloated, complex web app. Your CRUD app will do fine with far simpler dev tools. Even vanilla JS does the job in most cases. 99% developer feels compelled to learn and adopt what is trendy because that is what the client/market/boss demands; but it is you the 'engineer' who has to tell the client/boss how that bridge is to be built. When was the last time you went to a doctor and said: hey doc I have this, give me that medicine.

netizen-936824 5y ago
>When was the last time you went to a doctor and said: hey doc I have this, give me that medicine. Allow me to introduce to you: pharma advertising in the US
waffle_maniac 5y ago
> When was the last time you went to a doctor and said: hey doc I have this, give me that medicine. My physician friend fires patients for doing this kind of stuff. Usually they demand unnecessary x-rays and CT scans.
H1Supreme 5y ago
> React makes sense for FB's bloated, complex web app. Your CRUD app will do fine with far simpler dev tools. And that would be what? Exactly? I did a personal project last year that was vanilla HTML/CSS/Js, with some templating in Go (I know it's templating isn't the best, comparatively). By the end, I wish I would have done it in React. I ended up re-inventing the wheel for a lot of things, and ended up with something that was decidedly messier. All while attempting to be more simplistic. I wish Web Components would have taken off. When Polymer first launched, I was totally on board. I loved the idea of writing vanilla frontends, and using Web Components where I needed extended functionality (vs a full framework). But, it didn't, and unless your site is super simple, and mostly static, React et al. are the best ways to create frontends.
- zozbot234 5y ago
  Svelte is quite nice.
- finiteseries 5y ago
  Tools actually intended for building non bloated, non complex CRUD apps. Django, Rails, Laravel, .NET, Spring, I can go on. Instead Go was selected, templating HTML by hand, and assumedly doing nearly everything else by hand well. That is not the optimal solution for a simple CRUD app’s implementation, and isn’t reflective of anything but poor engineering.

netizen-936824 5y ago

>When was the last time you went to a doctor and said: hey doc I have this, give me that medicine. Allow me to introduce to you: pharma advertising in the US

waffle_maniac 5y ago

> When was the last time you went to a doctor and said: hey doc I have this, give me that medicine. My physician friend fires patients for doing this kind of stuff. Usually they demand unnecessary x-rays and CT scans.

H1Supreme 5y ago

> React makes sense for FB's bloated, complex web app. Your CRUD app will do fine with far simpler dev tools. And that would be what? Exactly? I did a personal project last year that was vanilla HTML/CSS/Js, with some templating in Go (I know it's templating isn't the best, comparatively). By the end, I wish I would have done it in React. I ended up re-inventing the wheel for a lot of things, and ended up with something that was decidedly messier. All while attempting to be more simplistic. I wish Web Components would have taken off. When Polymer first launched, I was totally on board. I loved the idea of writing vanilla frontends, and using Web Components where I needed extended functionality (vs a full framework). But, it didn't, and unless your site is super simple, and mostly static, React et al. are the best ways to create frontends.

zozbot234 5y ago
Svelte is quite nice.
finiteseries 5y ago
Tools actually intended for building non bloated, non complex CRUD apps. Django, Rails, Laravel, .NET, Spring, I can go on. Instead Go was selected, templating HTML by hand, and assumedly doing nearly everything else by hand well. That is not the optimal solution for a simple CRUD app’s implementation, and isn’t reflective of anything but poor engineering.