The most tiresome thing in #webdev is picking the techstack. So many choices to make: plain #javascipt or a more restricive language like #typescript , which ofc is often depending on the overall frontend framework to use: #svelte , #react , #preact , #solidjs ?
Or do one completly deviate from the classical way and use rather a techstack via #wasm , such as #rust with #dioxus ?
So many questions to answer and that still is only the js side of things, you then have to think about your css framework (if you want to use something like #tailwindcss ), your font choices, and ofc if and what styling library you actually use ontop of our frontend framework; e.g. #bootstrap , #blueprintjs , #tabler.io and so on.... which also often depends on your framework of choice!
@mai_lapyst I only ever get to pick a stack for my own projects, everything else my employer or client has done all that already (for better or worse)...
@danjac For me to (also talking in the toot more about personal projects!); that being said, I mostly deal for my employer / with clients that primarly use some php software, only a bit vue here and there when for example dealing with bigger projects where a own plugin for shopware is needed xDD....
@mai_lapyst yes my approach is to ask why I'm doing the project: is it to make a thing or to learn a thing? If the former, I have a tried-and-true stack (for me that's Django+HTMX+Tailwind but YMMV), if the latter then it's whatever it is that I want to learn about, and if it turns out to be worth learning then it gets added to my tried-and-true stack.
@danjac Yeah thats true. Only problem is when you are burned out by your current tried-and-true stack (ruby w. sinatra+mustache templates & manual js) and tried to many different other frameworks, libraries and languages in a maybe too quick manner xDD
Also: Actually didn't knew about HTMX so one thing more to look into lol
Add comment