Comment by interstice
Comment by interstice 7 hours ago
I remember vividly the chaos before React and what it was like to not know whether it was worth investing in a framework because it might not be around for long. Vue was the first one that I stuck with for a while, but Nuxt was being updated slowly at the time and none of the packages ever seemed quite as seamless as the guys in React land had it. I don't even use more than a handful of unique packages per site generally, I just really need those to work out of the box (tm). It's amazing how many very popular slideshow libraries just.. Break.
I love the idea of a modern & efficient framework that replaces it all, but in terms of hiring, training, maintaining and all of those boring yet vital things it's going to have to be something quite special to make a case for itself. Being able to render 100k table line updates simultaneously instead of 10k or whatever isn't fundamentally going to make the difference for all of those other requirements.
When did I become this person. How depressing. At least there always fun new tech on the backend to play with on weekends.
> Being able to render 100k table line updates simultaneously instead of 10k or whatever isn't fundamentally going to make the difference for all of those other requirements.
React's performance are way more severe and ubiquitous and user impacting.
I'd really love to see the websites you're writing in React and lunch a lighthouse or to simulate how do they perform for somebody on a slightly slower connection or not being on the latest iPhone.
Because I know my users include bank clerks or post office cashiers on 10+ year old computers being used at work as much as people on vacation with very poor signal on the beach.
Of course, if you only experience your website from your MBP on cable you thing the issues are only at "10k rows" level.