rewritten an nuxt+vue2 svelte like 2 months ago, and I love it, it just works, no gotchas
bind:this is amazing, just lack of IDE support
Thoughts on Svelte
91–100 of 194 posts
Re: Thoughts on Svelte
#92> I'd use it again for personal projects, maybe not for large company projects if I was the architect. Questions about large projects always arise when talking about Svelte. Did you / would you use it and why not? I would certainly NOT suggest using Svelte on enterprise projects. Why not? Because other people don’t do it, and that means that it is very likely that there are no (not many anyway ) experienced Svelte de…
> React and Angular are safe bets in THAT space.
But they weren't always. And a lot of people that 'know' React don't feel entirety comfortable using React because of complexity - ever seen someone want to know how to store a variable and watched the life drain out their eyes as they read a Dan Abramov essay on what true reactivity means?
Re: Thoughts on Svelte
#93I switched my game's UI from Vue2 to Svelte maybe a year ago, and I agree with almost all of the article. One thing I think the author overlooks: the appeal of Svelte's built-in animations and transitions is that they work correctly when the element's lifecycle is being managed by Svelte. E.g. with code like this: {#if showFoo} Foo! {/if} When `showFoo` changes to false, Svelte will first play a flyout transition and…
Can i ask you what type of game it is? Web or desktop? I wanted to dive into the topic of UI in desktop/native games for a while
Mine is web-based - a bunch of HTML DOM that lives on top of a canvas rendering the game. Afraid I don't know much about desktop/native, sorry!
Re: Thoughts on Svelte
#94Vue 3 and Svelte feel very similar to use. I prefer Vue because of the ecosystem. Using it with TypeScript and Pinia is pure joy! Surely, Svelte will catch up, but it will take a while.
+1 for Vue3's offering a lot of the simplicity that svelte is praised for while having much better tooling and being more polished.
Re: Thoughts on Svelte
#95What's a good frontend setup right now if you want strong static typing? I know Vue 3 supports TypeScript for example but it doesn't look like that's their core audience? I don't get the appeal of frameworks introducing template tags like `{#if showFoo}` vs JSX personally. You have the learn new syntax for things you already know how to do in JavaScript but with less expressibility, and JSX can at least be type check…
I don’t know if there was an implicit “besides Svelte” in there, but if you’re open to it, Svelte works well with TypeScript. The types flow into the HTML expressions too. I also like how little boilerplate there is compared to e.g. adding types to React component props. With Svelte, the prop typing is as simple as: export let name: string; export let age: number; FWIW I kinda agree with you about the #if syntax. I l…
In Svlete (which doesn't use JSX?), are your templates type checked? Non-JSX approaches have to reinvent not only JavaScript loops and control-flow, but also the type checking that TypeScript gives? This feels like a big downside to me.
Re: Thoughts on Svelte
#96So basically, using $ with expressions and no side-effects within the expression will not cause the issue the article is having?
Re: Thoughts on Svelte
#97> I'd use it again for personal projects, maybe not for large company projects if I was the architect. Questions about large projects always arise when talking about Svelte. Did you / would you use it and why not? I would certainly NOT suggest using Svelte on enterprise projects. Why not? Because other people don’t do it, and that means that it is very likely that there are no (not many anyway ) experienced Svelte de…
> Because other people don’t do it
This isn't true, I build enterprise software with Svelte (and have for years), and I know others who do too. We just don't contribute to the technology hype cycle.
Re: Thoughts on Svelte
#98I used Vue in the past and decided to use Svelte early this year, I do not need SEO or anything SSR, just the original SPA with CSR. then I found out Sveltekit is really a SSR-first design, and Svelte itself has no client side routing etc. While Vercel sells Sveltekit(and Next.js) to be CSR ready, I don't buy it, I don't need the complexity of SSR in the code when I just need a clean CSR, however you paint the SSR-is…
This is a pretty bizarre comment, given svelte isn’t intended to be a web framework and sveltekit makes it extremely simple to do client side rendering.
Re: Thoughts on Svelte
#99We have a pretty huge codebase [1] in svelte for Windmill, probably one of the biggest SPA on it. We are an open-source n8n/temporal + retool alternative so we are building both an advanced flow builder and an advanced app builder. The article is on point. There is 1 caveat to animations that I'd like to add. Everytime we ended up using animation without the `|local` specifier, it broke completely our app, and that's…
What are your build times like?
On a broader note, does anybody know of any build time comparisons for UI frameworks? Whenever I search for build time speed comparisons, I only find runtime speed comparisons...
Re: Thoughts on Svelte
#100I'm a React dev, I recently rewrote my websitein Svelte. Svelte is my favorite by far, it does so many things in a smarter way so its really hard to go back.