Email or username:

Password:

Forgot your password?
Top-level
Alex Russell

@loke @mensrea Sorry for being obtuse; lots of orgs have picked up React because they were told it's industry-standard, that they would be able to hire for it easily, etc. etc. It turns out that React on its own doesn't get you very far, and so there's a ton of time and money that needs to be spent either building infra to support some agglomeration of state tools + SSR configs + component libraries, or investment in learning metaframeworks like Next.

The savings never materialise.

2 comments
cuan_knaggs

@slightlyoff i think there is another aspect to this. the "modern way" with frameworks, language abstractions (typescript), build pipelines, et al. make people think they're doing "real programming". so they keep layering complexity to solve problems caused by complexity because they're really smart @loke

Elias MÃ¥rtenson

@slightlyoff @mensrea
Thanks. That's another layer of problems that I'm not directly familiar with as I have never done web development recently on a large team.

My experience with react is mostly as a user of sites built using it, as well as my personal attempts at using it myself.

In the latter case, I was quite unimpressed.

Sorry, I was impressed by how the simple vases seemed almost magic. Less impressed by the hoops one has to just through to make sightly more complex usecases possible.

@slightlyoff @mensrea
Thanks. That's another layer of problems that I'm not directly familiar with as I have never done web development recently on a large team.

My experience with react is mostly as a user of sites built using it, as well as my personal attempts at using it myself.

In the latter case, I was quite unimpressed.

Go Up