2 ms·
I started webdev some years back from the other direction; I had read of the countless JS web frameworks and their countless dependencies, and I had read the ar
by FireInsight 3y ago
I started webdev some years back from the other direction; I had read of the countless JS web frameworks and their countless dependencies, and I had read the arguments against using "uncessary" JS (talking about genuine bloat) on websites. So, I thought I'd just explore options like those based on Go; fast, compiles to a single binary, no need to touch JS. Then I wrote my first totally website with Hugo and and a custom theme for it, had fun doing it too. Tried to write a couple selfhosted web apps with Go frameworks too but never got that far.
Then I moved to doing all my projects with Astro/Svelte and webapps with SvelteKit. I was surprised at how good and fun it was. The templating languages less esoteric, more integrated. Reactivity was something I never even dreamed of with a hard line on JS. All the while, the websites got better. I could finish them more quickly and there was still no or a miniscule amount of JS shipped by default. I could also, when making a content-driven website with Astro, easily reach for Svelte for a small bit of interactivity / reactivity. I could've just as easily used Alpine or whatever else someone might recommend.
That's to say, I've found a comfortable DX in current-gen JS frameworks, while finding the server-side giants a bit too sturdy for my use. Reading about new frameworks is fun to me, because I can easily switch from Svelte to something else on my Astro sites, if I find something that fits my tastes even better.
- alabhyajindal 3y agoI prefer traditional server side frameworks precisely because they have a rigid pattern of doing something. And also because they have been around for a while. I don't get excited about learning a new frontend framework because I'm fairly certain it won't allow me to do something new. It may be more convenient in terms of syntax or have fewer client side code being shipped, but it doesn't enable me to do something in terms of functionality I couldn't already do. I would prefer pick one framework and get better at it, rather than learn the templating language of 5 frontend frameworks.