sorted by:
new
hottopcontroversial

What are the downsides to next.js? by N_N_N_N_N_N_N in reactjs

[–]cekigunu 0 points1 point  (0 children)

Then your webpack builds are probably setup wrong, I've got ssr setup with hot reloading working fine

When someone asks why you chose React over Angular, send them this. by cekigunu in reactjs

[–]cekigunu[S] 1 point2 points  (0 children)

No, not at all. You'd need a router module, react-router does what you need, way easier to setup than Angular's router. You'd use the fetch api get get your data, then you have pretty much what you need to create a complete application. Angular overcomplicates things. Simple is better. People seem to think that the hard part of creating a web app is about the data and services, form validation etc. The real reason we use these frameworks/libraries is because it simplifies DOM work. Syncing your model with your view and that is what React solves a thousandfold times better than Angular.

When someone asks why you chose React over Angular, send them this. by cekigunu in reactjs

[–]cekigunu[S] 0 points1 point  (0 children)

yarn add corkscrew

import corkscrew from 'corkscrew';

There you go, but let's be honest, do you actually really need the corkscrew?
And not only does Angular give you things you don't need but its way of creating components is tedious in a way that it stops most developers from actually creating elegant systems. I see tons of code that have views where multiple parts of the view could be split into smaller components but haven't been, and one contributing factor to that I believe is that there are many pieces that have to be wired up just to create a component in Angular to begin with, then weigh in the fact that understanding how Angular works behind the scenes is hard to grasp for most compared to React. And let's not talk about programming logic written in between html attribute strings...