Not sure if this is unproductive or not, since I'm still learning. Basically, instead of constantly working, I'm trying to optimize my workflow and setup. I know this can be an issue with apps like Notion or nvim, because you can fall down the rabbit hole of constant configuration, but I think it's also a big problem in frontend. At least for me.
I've done my fair bit of config with nvim, Ghostty, and Aerospace setup. I'm done with that. But what I'm not done with are frameworks.
I started web dev with just regular vanilla HTML, CSS, and JS. I didn't think I'd need anything else, but also all of the frameworks seemed overwhelming. Then, after my first big project, I decided to take on React. I fiddled around with it for a project or two and got a grasp of the basics. However, I didn't really like it and found it complex, since I wasn't such a big fan of JavaScript, especially TypeScript, which I started using with React.
At one point I discovered glorious Svelte and SvelteKit. Svelte seemed sooo good and was very familiar when comparing with vanilla HTML, CSS, and JS, with its dedicated code blocks in components and pages. I started using Svelte everywhere I could and made my first and current portfolios in it as well. But everything isn't sunshine and rainbows.
After a while I realized that support for Svelte is still partial. Even though Svelte has been around since 2016, Svelte 5's runes only came out in 2024. Because of this, many services and packages might not have support for Svelte yet, or only have partial support. In addition, the job market is small as well.
Because of these very reasons, I gravitated towards React (Next.js) again. I actually grew to really like it, since I'm now more familiar and comfortable with TS, and React's syntax seems robust and logical. Buuuuut, there's so much to Next.js. This is good, of course, since it provides a lot of functions and solves many problems, but for a newbie like me it's just overwhelming. Despite that, I have still kept using Next.js as my main framework (with SvelteKit as second), because I quite like it.
Recently there have been talks about TanStack. This has intrigued me, but looking at the syntax and code, it just seems like a more optimized alternative in the same space as Next.js, since I've heard that Next.js has had some slight performance issues recently and is a bit slower compared to others, e.g. TanStack Start.
But TanStack hasn't been enough for me to try yet. The most interesting framework, and the one I think I will learn next, is Nuxt with Vue. There's a few reasons for this:
Firstly, the syntax seems to be something between React and Svelte, which I quite like. It seems compact and separated like Svelte, while still having TS/JS integration like React.
Secondly, I know the community and job market is bigger for Vue than Svelte, since Vue has been around for a while and has a pretty strong community. I once visited a big company in my country and found out that even they were using Vue. Also, the Nuxt DevTools seem sooooo cool and useful.
Finally, I learned that in the uni I want to go to, Vue is recommended when creating web projects. You can use others as well, but taking into account my interest and passion for frontend, this is probably the thing that will push me to learn Nuxt with Vue.
That's all. What I'm trying to say is, instead of specializing in and mastering one framework, I've been using multiple and will learn more in the future. Thinking about it, it seems counterproductive, but I just find them so interesting, and I've also learned that when you're young, it's good to learn as much as you can. Who knows, maybe I'll fall in love and end this with Nuxt.