4 ms·

That's why I like Vue. It's mix of the two with a synchronized ecosystem for the core libs and a simple API. Vue 3 kinda tanked all that though.

FractalHQ 4y ago
What do you think of Svelte? I haven’t used Vue since I discovered Svelte but I’m always curious about peoples perspectives and try to keep my finger on the pulse. The new Nuxt looks pretty awesome! Love the api design. I’m hoping Sveltekit steals a few ideas from it before 1.0.
- brimble 4y ago
  I looked at it the other day after the discussion thread about JS frameworks, but bounced when I saw ".svelte" files. I accept (demand, really) TypeScript but I've become allergic to any attempt to add much more on top of JS than that. I can just see the next poor bastard coming along in a short year or two and going "oh god, WTF is a '.svelte' file? What did my piece of shit predecessor fall for?" I'm looking into Vue today. Possibly I'll settle on something even simpler. React's certainly out, and thank god the mood is finally shifting enough that I can abandon it without harming my career (much). Slow, janky, and god they've made some weird choices with it in the last few years. It was always a bit heavy, but it felt like it had some degree of elegance to it before that—if only in parts of the API itself, not the implementation. [EDIT] Oh good lord, '.vue'. Don't any of these just use normal-ass code? Sigh.
  - bluefirebrand 4y ago
    Things like .vue and .svelte are really more like hints to your Editor for which linter to use, which code highlighting etc. Also your build chain I guess. I'll admit it's annoying but it's still just "normal-ass code". Vue, for instance, is just html, JavaScript and css. A .vue file is just all three in one file with special syntax to indicate each section. At least, last I looked at vue it was.
    - nightski 4y ago
      That's true of Vue. Svelte has a compiler which changes and augments your code with additional code for it's state management system. So it's definitely not normal code.
  - bradstewart 4y ago
    I generally agree with your don't "add much more on top of JS" sentiment, but I like .vue files. It's "just" HTML, CSS, and JS in one file, which I find convenient for components. But it's optional--you're free to use three separate files.
- conradfr 4y ago
  Seems interesting but quite young. When I looked it up it there was discussion about Sapper vs Sveltekit etc and quite frankly I can't stand that kind of thing anymore, it just leads to confusion, a lot of Googling and SO, partial or wrong docs etc and in the end a LOT of lost time and energy. And I say that as someone who is currently refactoring a Vue 3 app from JS/VueX to TypeScript/Pinia ... oh the irony.
tpetry 4y ago
Can you describe the vue 3 part more? As an outsider it just looks for me they just added another api with a different style, so people can choose what they like.
- conradfr 4y ago
  The official router and store were not ready when they released Vue 3, even kind of still not, and the store is moving to a new lib. Also there's now two competing APIs. The new one that they want you to use, and the old one that people like better. Also a lot of time your objects are actually proxies, which I'm sure there's good reason for but that's kind of annoying (personal opinion).
  - ipaddr 4y ago
    I dislike dealing with proxy objects because you have to serialize and unserialize to turn it into what it always was.
slipwalker 4y ago
that's why i started using Svelte[1] on my personal projects... simplicity ( and the godsend cross-compatibility between browsers/desktop/mobile ) [1] https://svelte.dev/ https://svelte.dev/

FractalHQ 4y ago

What do you think of Svelte? I haven’t used Vue since I discovered Svelte but I’m always curious about peoples perspectives and try to keep my finger on the pulse. The new Nuxt looks pretty awesome! Love the api design. I’m hoping Sveltekit steals a few ideas from it before 1.0.

brimble 4y ago
I looked at it the other day after the discussion thread about JS frameworks, but bounced when I saw ".svelte" files. I accept (demand, really) TypeScript but I've become allergic to any attempt to add much more on top of JS than that. I can just see the next poor bastard coming along in a short year or two and going "oh god, WTF is a '.svelte' file? What did my piece of shit predecessor fall for?" I'm looking into Vue today. Possibly I'll settle on something even simpler. React's certainly out, and thank god the mood is finally shifting enough that I can abandon it without harming my career (much). Slow, janky, and god they've made some weird choices with it in the last few years. It was always a bit heavy, but it felt like it had some degree of elegance to it before that—if only in parts of the API itself, not the implementation. [EDIT] Oh good lord, '.vue'. Don't any of these just use normal-ass code? Sigh.
- bluefirebrand 4y ago
  Things like .vue and .svelte are really more like hints to your Editor for which linter to use, which code highlighting etc. Also your build chain I guess. I'll admit it's annoying but it's still just "normal-ass code". Vue, for instance, is just html, JavaScript and css. A .vue file is just all three in one file with special syntax to indicate each section. At least, last I looked at vue it was.
  - nightski 4y ago
    That's true of Vue. Svelte has a compiler which changes and augments your code with additional code for it's state management system. So it's definitely not normal code.
- bradstewart 4y ago
  I generally agree with your don't "add much more on top of JS" sentiment, but I like .vue files. It's "just" HTML, CSS, and JS in one file, which I find convenient for components. But it's optional--you're free to use three separate files.
conradfr 4y ago
Seems interesting but quite young. When I looked it up it there was discussion about Sapper vs Sveltekit etc and quite frankly I can't stand that kind of thing anymore, it just leads to confusion, a lot of Googling and SO, partial or wrong docs etc and in the end a LOT of lost time and energy. And I say that as someone who is currently refactoring a Vue 3 app from JS/VueX to TypeScript/Pinia ... oh the irony.

tpetry 4y ago

Can you describe the vue 3 part more? As an outsider it just looks for me they just added another api with a different style, so people can choose what they like.

conradfr 4y ago
The official router and store were not ready when they released Vue 3, even kind of still not, and the store is moving to a new lib. Also there's now two competing APIs. The new one that they want you to use, and the old one that people like better. Also a lot of time your objects are actually proxies, which I'm sure there's good reason for but that's kind of annoying (personal opinion).
- ipaddr 4y ago
  I dislike dealing with proxy objects because you have to serialize and unserialize to turn it into what it always was.

slipwalker 4y ago

that's why i started using Svelte[1] on my personal projects... simplicity ( and the godsend cross-compatibility between browsers/desktop/mobile ) [1] https://svelte.dev/ https://svelte.dev/