4 ms·

I believe when people consider using Angular or React they are simply not informed and make a mistake. I was in that camp myself. It’s important to be aware of

I believe when people consider using Angular or React they are simply not informed and make a mistake. I was in that camp myself. It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

KronisLV 3y ago
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons. Would you like to elaborate on that? In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one mainstream package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same. For example, using https://angular.io/guide/i18n-overview https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/ https://react.i18next.com/ Or something like https://angular.io/guide/form-validation https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/ https://formik.org/ Or perhaps https://angular.io/guide/router https://angular.io/guide/router vs https://reactrouter.com/en/main https://reactrouter.com/en/main Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ https://primeng.org/ or https://primereact.org/ https://primereact.org/ React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly. Now, projects like Next https://nextjs.org/ https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
- strogonoff 3y ago
  There are a bunch of compatible packages, sure, I just meant what you are getting is not actually a proper Web framework, that’s all. It’s a reactive renderer library with another library (ReactDOM) that makes it work with DOM.

KronisLV 3y ago

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons. Would you like to elaborate on that? In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one mainstream package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same. For example, using https://angular.io/guide/i18n-overview https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/ https://react.i18next.com/ Or something like https://angular.io/guide/form-validation https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/ https://formik.org/ Or perhaps https://angular.io/guide/router https://angular.io/guide/router vs https://reactrouter.com/en/main https://reactrouter.com/en/main Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ https://primeng.org/ or https://primereact.org/ https://primereact.org/ React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly. Now, projects like Next https://nextjs.org/ https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

strogonoff 3y ago
There are a bunch of compatible packages, sure, I just meant what you are getting is not actually a proper Web framework, that’s all. It’s a reactive renderer library with another library (ReactDOM) that makes it work with DOM.