top | item 31285650

(no title)

brimble | 3 years 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.

discuss

order

bluefirebrand|3 years 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|3 years 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|3 years 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.