It's an excellent article, and the work within is very well done, but there's a part of me that screams "Why would you introduce this much complexity for what should be a simple scroll?" (overcoming technical hurdles to produce the desired end result aside).
From time to time I dip my toe in and try new things, but as productive as I can get with Astro, the illusion vanishes as soon as I have to understand any of the plumbing.
Fortunately, I can still party like it’s 1999 just fine: just yesterday, I worked on a janky brutalist web app (the same way I did back in 2002, cribbing from the O’Reilly “Dynamic HTML: the Definite Reference”) and “deployed” it with rsync to pico.sh. It’s practically unstyled and I didn’t even use jquery, but it works.
But frontend stuff is messy. How do you tell a person what they're trying to do is wrong and they need to change their inputs? Oh, maybe we can highlight the input or we can pop a modal message. Haha, psyche! Users ignore that shit! Now what you gonna do, buddy?
Frontend is a mess because all you people are a mess.
Not saying that you're totally wrong, but I think this difference is not necessarily a deliberate decision by individual engineers, or caused by personality or skill level.
The employee market demographics surely play a role, but this is about concretions, not generalizations.
There is no lack of (often poor) generalizations when it comes to the skills and requirements demanded by BE and FE roles, respectively.
Not wanting to dismiss your idea / the grain of truth. But IMO you are falsely generalizing.
Also, there are not only FE devs claiming to be "full stack" when they don't know HTTP basics.
There are also BE developers with similarly daunting knowledge gaps.
Or in other words, in both worlds there are juniors masquerading as seniors and the other way around, depending on the organization.