Is server-rendered HTML that bad for 2026 web or is everyone building complex apps?
Many of my customers insists on using Next.js or similar but when I browse their website I don't get the point. They are downloading and executing megabytes of JS while in-page interactions tends to be limited to few basic stuff. Never seen one of their project requiring offline mode. Maybe that's being able to easily replace a [FRAMEWORK] dev with another.
I think the unfortunate truth is the simplest. Web development has long been detached from rationality. People are drawn to complexity like moths to a flame.
> People are drawn to complexity like moths to a flame.
Not to complexity, but to abstraction. The more something is abstracted away, the more fungible "developers" become, to the eventual tune of Claude Code.
No one cares that trying to debug a modern application is as hellish as its performance, the KPI that executives go for is employment budget.
I don't know if Next.js, TanStack, etc are more abstract than Rails, Django, etc. They're undoubtedly more complex though. I also find it hard to believe that it's some sort of conspiracy by management to make developers more fungible. I've seen plenty of developers choose complexity with no outside pressure.
Can't remember in details that part of the film. Was it explicitly eugenics? Otherwise it could be seen as not getting the same education, depending on parental situation.
It's in the opening scene, where poor, "low IQ" couple complains about getting another child again by accident while a suburban "high IQ" couple was hesitant to start making children until it was too late (the husband dies). "Low IQ" couple's son grows up into a stupid, sexy jock and it goes on from there for generations.
So yes, eugenics was pretty much an integral part of the premise. IQ bubbles even pop up on the screen during those scenes, just to remove any shadow of a doubt.
> So yes, eugenics was pretty much an integral part of the premise. IQ bubbles even pop up on the screen during those scenes, just to remove any shadow of a doubt.
Is that really how we use the word "eugenics", though? That scene you refer to explicitly explained that Natural Selection does not necessarily select for intelligence.
So while some people are calling it "Eugenics", it's what we more typically call Natural Selection, Evolutionary Pressure, etc.
Eugenics implies that the selection criteria was not natural. The scene you mention makes it clear that, in-universe anyway, the selection criteria was entirely natural and not a pressure imposed by humans.
I agree that it doesn't explicitly show someone tilting the scales, but that doesn't mean that eugenics are not an integral part of the premise in a "if we don't do something about this, this is what the world will look like" kind of way.
I still like the movie, but like with any 20+ years old comedies, I can recognise issues with its premise which would be more-or-less unacceptable today. In 2006... not as much. The future is now, old man!
> does that scene imply that we should do something to tilt the scales in the opposite direction?
No, it did not.
> I agree that it doesn't explicitly show someone tilting the scales, but that doesn't mean that eugenics are not an integral part of the premise in a "if we don't do something about this, this is what the world will look like" kind of way.
And, to you, "Do something about this" means only one thing - forcefully stopping classes of people from reproducing?
The cost is not just tokens, you need an actual human contributor looking into the issue, prompting, checking output, validating, deploying,... Difficult to compute the actual AI ROI. If $300K didn't matter without AI, it probably still doesn't matter with AI.
Crypto didn't "win", the technology is there but people are mostly gambling, or doing shady stuff. Shall I mention NFTs? It didn't change the life of the average joe, nor business. It's a niche.
Many people are still coding without AI and doing perfectly fine. When you design serious things, coding is not where most time is spent anyway. Maybe it'll become unavoidable at some point, by that time the experience will be refined and it'll be easier to learn.
Point is, it's never too late. If you don't need to be cutting edge on a new tech, it may not make sense to put the extra effort of early birds. If you put that effort, you better not do it for free.
Now it doesn't really impact build time and Railway offers Next.js hosting.
reply