I empathize with how you're feeling... There's a constant argument about which frontend framework is the best(react? vue? svelt?), which CSS solution(tailwind?

I empathize with how you're feeling... There's a constant argument about which frontend framework is the best(react? vue? svelt?), which CSS solution(tailwind? bootstrap? MUI?), which DB scheme, which host, "can I just go serverless? If so, which service do I use?", "what about edge function!?". And of course, startups come along here and there with an attempt to unify the options(RedwoodJS, NextJs~), but eventually, new disruptive tech comes and breaks it apart now the cycle starts again. I think as engineers, we are trained to do things the best way, the right way, or the most efficient way. But when it comes to hobby projects that don't quite have a hard deadline, that mentality can get us trapped in the research phase for way too long. I think the antidote here is the good'ol Nike slogan... "just do it". Understand that you'll never have complete information and that ultimately you're making a bet with your decision to go with one solution or another. With side projects, almost all of your decisions are *reversible and have low consequences. So just keep moving, and if you make the wrong move, take a step back. Or just start over! (personally, with simple web apps, I'm a fan of the t3 stack. TS, React, Next-Auth, tRPC, Prisma)