4 ms·

The fun part is often all that bullshit hyper optimized complexity can still be beaten on all the web core vitals by a humble LAMP server So not only are you w

The fun part is often all that bullshit hyper optimized complexity can still be beaten on all the web core vitals by a humble LAMP server So not only are you wasting your time on all the wrong things, you're also gaining nearly no benefit from it I'm pretty convinced that all these shiny new hotness tools and frameworks of the past decade are actually just meant to sabotage competition and small companies

bornfreddy 3y ago
I agree - for most of them. One exception would be React/Vue/other frontend frameworks that split updating the state and visualizing it. It sounds like a small thing, but it makes a world of difference in non-trivial projects, compared to native js / jquery. Then again, it's the idea itself that matters, overoptimizing the implementation is not beneficial. I.e., React classes are just as good (or better) as hooks as far as I'm concerned, it would be better if they would let it be at that stage.
- BoorishBears 3y ago
  Vercel and co managed to mangle the one benefit you mentioned. They introduced the concept of a "server component": one that is rendered once and cannot update state. And instead of making that opt-in, they made it the default. — That is to say, the default of React is to no longer allow updating state in components. No value proposition is safe from the forces of financially incentivized thought leaders.
  - leerob 3y ago
    The Meta team introduced Server Components: https://legacy.reactjs.org/blog/2020/12/21/data-fetching-with-react-server-components.html https://legacy.reactjs.org/blog/2020/12/21/data-fetching-wit...
    - BoorishBears 3y ago
      The RFC was driven by Vercel. Vercel announced RSC landing in experimental on stage before the React team even updated their docs I'm not even going to get into how ridiculous it is that the default config chosen was to break people's builds for a feature that isn't mature enough to have anything more than a single reference implementation from Vercel.

bornfreddy 3y ago

I agree - for most of them. One exception would be React/Vue/other frontend frameworks that split updating the state and visualizing it. It sounds like a small thing, but it makes a world of difference in non-trivial projects, compared to native js / jquery. Then again, it's the idea itself that matters, overoptimizing the implementation is not beneficial. I.e., React classes are just as good (or better) as hooks as far as I'm concerned, it would be better if they would let it be at that stage.

BoorishBears 3y ago
Vercel and co managed to mangle the one benefit you mentioned. They introduced the concept of a "server component": one that is rendered once and cannot update state. And instead of making that opt-in, they made it the default. — That is to say, the default of React is to no longer allow updating state in components. No value proposition is safe from the forces of financially incentivized thought leaders.
- leerob 3y ago
  The Meta team introduced Server Components: https://legacy.reactjs.org/blog/2020/12/21/data-fetching-with-react-server-components.html https://legacy.reactjs.org/blog/2020/12/21/data-fetching-wit...
  - BoorishBears 3y ago
    The RFC was driven by Vercel. Vercel announced RSC landing in experimental on stage before the React team even updated their docs I'm not even going to get into how ridiculous it is that the default config chosen was to break people's builds for a feature that isn't mature enough to have anything more than a single reference implementation from Vercel.