4 ms·
>Most banks and airlines I use rewrote their perfectly fine and fast sites and apps to reactjs and now they seriously suck. This is not the fault of react but m
by kgeist 5y ago
>Most banks and airlines I use rewrote their perfectly fine and fast sites and apps to reactjs and now they seriously suck. This is not the fault of react but more of this idea of tech people that everything has to be new.
I doubt they rewrote it just for the sake of rewriting it in a new framework, it costs money for no benefit. What's more likely, which I have witnessed multiple times, is that the original codebase was an unmantainable mess, hard to support and extend, with abandoned/unmaintained third-party dependencies, and fewer and fewer developers on the market who know the stack. Sometimes it costs as much (or even less) to rewrite the whole thing than to refactor the original. And when the decision to rewrite the codebase is made, they choose the most popular tools/frameworks so that it was easier to find new developers, and today it happens to be react and the like.
- JKCalhoun 5y agoWhy does it seem (I'm not a backend engineer) that a company moves off of one technical-debt ridden backend to another, even bigger, more complex framework for their backend. It's like we're in a downward tech-debt spiral. Is it going to take an Ever-Given-like or Covid-like disruption of e-commerce that shuts down society to cause us to wake up and take this seriously? (Or have government step in and set standards and requirements for e-commerce.)
- nicoburns 5y agoPresumably because they didn't fix the organisational issues that caused the first codebase to become a mess. If they had those sorted then they could most likely have stuck with the original codebase AND a rewrite would likely be succesful.
- deleted 5y ago[deleted]
- tluyben2 5y agoI really do not think so; the places I saw, just go from crap to crap because tech leads/new ctos need to put their mark on things. I consulted for clients in the past years who were told to dump react (in 1m$+ apps) for svelte because react is yesterday. That is insane. One of the larger insurers is doing this now; I told them not to because it makes no sense. But they drank the koolaid and doing react to svelte rewrites for no reason besides a new cto. The churn in companies is high and it is not good.
- stjohnswarts 5y agoNone of that matters to the customer if the new interface is completely different and much less functional. You should make sure there is an easy transition or you're going to lose a lot of business with your "improved interface".