[neilv]

I'm currently using some of the latest popular stack, for a simple Web site that could've appeared almost the same 25 years ago[*], with static HTML and a little client-side JS. (And could've been implemented faster then, and would've operated much more efficiently.)

158 NPM packages already, and the page load requests are insane.

Two reasons I'm doing this monstrosity of an implementation anyway:

1. Resume-driven-development, on a personal/indie project.

2. Using the framework's interactive SSR just to make it harder for freeloaders (AI company scrapers, copy&paste developers) to copy the information or the implementation tricks.

[*] Except for a little flexbox "responsive" flowing, corner rounding (without kludges), and some fade transitions, none of which are necessary.

[dihydro]

This is absolutely insane to me. Native HTML5 gives so much power and it seems like front end devs love to jargon and buzzword the next big thing to death every other year. I primarily work in networking and if we added the layers of complexity like I see front end work does we would have SDN configuring an internal PtP VPN for every device on a LAN just because it's the hot new tech.

[neilv]

I made a powerful HTML5 Offline app a long time ago, for some technical requirements (and cool-sounding user) that would be challenging, no matter what stack was used.

Then I was in an interview, where some junior openly sneered at me, for not using a recent popular RDD framework for it.

Part of the problem, even for highly experienced people, is that even the good jobs usually have "technical interview" gatekeeping that's not very enlightened.

(Yes, no matter what framework or stack you're using, I've probably done related things before, and I can pick it up quickly. No, a Leetcode hazing won't tell you how I think, nor what I can do, and it just seems like you're jerking off.)