2 ms·

I hate it because of announcements like this; we are, as a small team, just getting to terms with react 18; a lot of libraries still are not working well with i

I hate it because of announcements like this; we are, as a small team, just getting to terms with react 18; a lot of libraries still are not working well with it and there is 19 already. It sucks. So yeah nothing wrong with the concept of react, just the usual and terrible javascript ecosystem churn with stuff we don't need, but now everyone will have to update and so do we. Nice if you have a dedicated frontend team for every of your apps, not so nice for a small team that has to manage many apps across many clients. I like major (potentially) compatibility breaking updates every 10 years or so, not every 3 weeks. So yeah, we went off react to vanilla js, htmx and liveview type stuff which makes this all far simpler. Dev is also far simpler for us; all the pitfalls are no longer there. There might be some advantages to react in some cases; we won't look back; we never had a more relaxed team especially since we ditched nextjs and react; the trying out of other tech for frontend made us realize react was wrong for us all along anyway. ymmv of course.

KronisLV 2y ago
> ...just the usual and terrible javascript ecosystem churn with stuff we don't need, but now everyone will have to update and so do we I don't think that there are many good options for front end that are maximally stable out there: https://endoflife.date/react https://endoflife.date/react https://endoflife.date/vue https://endoflife.date/vue https://endoflife.date/angular https://endoflife.date/angular Unless you want to look at something way more niche, you probably won't find something that has a main version supported for 5-10 years without major changes. Then again, that's usually not even the case with back end frameworks either, the closest you can get is either language runtimes like JDK (2014-2030, albeit the open source versions seem to end support in 2026), or maybe OSes like RHEL (e.g. 8 has a support timeframe of 2019-2029 or the extended option is until 2032). In short, there is churn everywhere and I don't think you can simply pick any stack that is used for web development and will get exposed to the world (and therefore needs security patches), that will still work okay with no breaking changes along the way in 5-10 years or so. The only difference is how bad the individual choices will be.
mephitix 2y ago
React 18 was released in March 2022 though. It’s been over 2 years, not 3 weeks. I’ve also actually thought the React team is pretty careful about breaking changes. Their 19 breaking changes doc is mostly about removing already-deprecated APIs.
mendocinox 2y ago
how many libraries does your project depend on?
robertoandred 2y ago
I guarantee rebuilding your whole site in htmx was more effort than installing React 18 when it came out three years ago.
- phist_mcgee 2y ago
  I'd also venture that this was a backend dominated decision to take control of the full-stack.

KronisLV 2y ago

> ...just the usual and terrible javascript ecosystem churn with stuff we don't need, but now everyone will have to update and so do we I don't think that there are many good options for front end that are maximally stable out there: https://endoflife.date/react https://endoflife.date/react https://endoflife.date/vue https://endoflife.date/vue https://endoflife.date/angular https://endoflife.date/angular Unless you want to look at something way more niche, you probably won't find something that has a main version supported for 5-10 years without major changes. Then again, that's usually not even the case with back end frameworks either, the closest you can get is either language runtimes like JDK (2014-2030, albeit the open source versions seem to end support in 2026), or maybe OSes like RHEL (e.g. 8 has a support timeframe of 2019-2029 or the extended option is until 2032). In short, there is churn everywhere and I don't think you can simply pick any stack that is used for web development and will get exposed to the world (and therefore needs security patches), that will still work okay with no breaking changes along the way in 5-10 years or so. The only difference is how bad the individual choices will be.

mephitix 2y ago

React 18 was released in March 2022 though. It’s been over 2 years, not 3 weeks. I’ve also actually thought the React team is pretty careful about breaking changes. Their 19 breaking changes doc is mostly about removing already-deprecated APIs.

mendocinox 2y ago

how many libraries does your project depend on?

robertoandred 2y ago

I guarantee rebuilding your whole site in htmx was more effort than installing React 18 when it came out three years ago.

phist_mcgee 2y ago
I'd also venture that this was a backend dominated decision to take control of the full-stack.