> One of my coworkers made a completely static portfolio website with a single page and used react.
People love hating on react, but I mean this is pretty common. Raw is fine, but even in a "static" thing, you'll eventually go "ok now I want to reuse some text here.." Or have some common elements with x things shared. So I'm gonna have to write some hacky imperative JS? Or messy CSS? And what starts as static very easily becomes slightly dynamic. I hate overengineering, so if React were hard to setup or deploy I'd agree (eg Kube), but the cost-benefit of React makes it worth it in most cases for me
Yeah pretty much this. I tend to use Astro but I think your point still stands.
I wanted to make a basic online agenda in a few different formats for a Toastmasters club and though I could have used raw html and css to build it, but each agenda had slightly different layout that would have been a lot of copy pasting in html and lots of room for error.
With astro and react islands it was fairly simple to implement.
People love hating on react, but I mean this is pretty common. Raw is fine, but even in a "static" thing, you'll eventually go "ok now I want to reuse some text here.." Or have some common elements with x things shared. So I'm gonna have to write some hacky imperative JS? Or messy CSS? And what starts as static very easily becomes slightly dynamic. I hate overengineering, so if React were hard to setup or deploy I'd agree (eg Kube), but the cost-benefit of React makes it worth it in most cases for me