▲ | spartanatreyu 16 hours ago | |
> I can't speak to the complexity you've encountered, but for me it's pretty much zero. A button component is just a function. React-Router is good enough and code splitting is pretty much just changing how to import something. Component state is dead-easy to write by just adding a useState hook. Bundlers pretty much handle everything these days so not to much concern about size. For me, everything depends on the site and the host. For 80% of websites, a button is <button>, a router is just URLs that point to files, a state is just a json object in localStorage. For 15% of websites, a button is <button>, a router is a single file that imports an auth provider and a storage provider which are chosen based on the host. For the remaining 5% of websites which are actually true applications, I'd reach for a RoR inspired framework (so Laravel for PHP host, Adonis for js host, etc...). No react needed. |