3 ms·
This was the same thought I had about Vue when I first used it. I knew vanilla javascript - Vue is vanilla javascript. I knew HTML and CSS - Vue's component-ba
by fraktl 7y ago
This was the same thought I had about Vue when I first used it.
I knew vanilla javascript - Vue is vanilla javascript.
I knew HTML and CSS - Vue's component-based approach looks exactly like HTML.
It didn't take more than 20 minutes to get some code running using Vue and it made me significantly faster.
Then I stumbled upon Svelte and after using it for a day, I asserted it won't make me much faster and I'd have to learn yet another tool.
That's why I stuck with Vue, and then I discovered Vuetify and Nuxt, awesome tools that made my life even easier. I really can't draw a parallel between Svelte and Vue in terms of "better", so I started using my subjective feeling to justify my decision of going with a tool.
Subjectively speaking, I don't like Svelte. I don't have a solid, objective reason except this one: I really don't want to abandon 3 years of work I've put into projects that are based on Vue and TypeScript and go with Svelte without obvious gains.
There's nothing so different that it'd justify yet another downtime in order to swap the toolset so I can satisfy my peers online who approve or disapprove my choice of tooling.
- sireat 7y agoInterestingly the more common view is that Vue feels less vanilla Javascripty than React. When I am writing React I am writing Javascript (usually a bit obscured with JSX). With Vue a large part of functionality is in v-directives. That doesn't change the fact that Vue is easier to learn for those new to webdev than React. Students who just started learning Javascript can usually pick up Vue but I am yet to see someone with little JS experience pick up React in a hurry.
- Can_Not 7y agoIf you value larger ecosystem, more mature ecosystem, and superior error handling/tracking, then you've made the right choice