Now that it’s been around for some time, what’s the general thought on it?
Anyone use it then go back to the traditional frameworks? Anyone love it and still think it’s the next big thing?
Anyone use it then go back to the traditional frameworks? Anyone love it and still think it’s the next big thing?
The ecosystem isn't there yet, and I probably wouldn't try to use it in a work project. For my personal projects though, I use it for everything front-end. More than that - I've stopped making desktop apps and just default to using svelte instead.
Happy to answer any specific questions you've got! Bottom line - given the opportunity, I will use Svelte.
I'm a web developer and I like the power and flexibility it has compared to native GUI development but I think a big problem is we now have an entire generation that doesn't even know what they're missing.
I'm guessing that the Windows and MacOS frameworks were less hostile, but it seemed like the web was surely ideal, at least in the last several years. Sure, you had to learn a web framework to build simple applications, but you could at least use a high level language with a reasonably sane package manager (for those who haven't developed in C or C++, it might come as a surprise that JavaScript and NPM are "sane" tools) and a reactive programming model.
I guess I'm not sure if my expectations for web development are too high or if GTK and Qt are especially bad representatives of native development.
I echo this sentiment, with the exception of Delphi circa version 5-7, though that's probably through rose-tinted glasses since I had just come off trying to make Win32 UIs using MASM. GUI development has always been a crapshoot of learning esoteric bugs masquerading as features. Windows and MacOS UI development is no different, just more locked in. At the very least the web is somewhat consistent between platforms.
The JS ecosystem’s penchant for giving you small components that you have to choose individually and then glue together can get a little exhausting. Hopefully the library whose approach you prefer has decent documentation, keeps up with changes to svelte, doesn’t get abandoned, etc.
Edit: apparently Sapper is a Next.js like framework that provides all the components you need for svelte in one package. Someone else said on this thread it’s eventually getting deprecated by the svelte team’s own thing called SvelteKit. Not ideal, but at least they’re working on something more integrated.
> The UI component libraries for Svelte are still lacking in maturity
The typical counterargument usually made at this point would be "those two points are related" (to paraphrase Bjarne Stroustrup: "every ship gets barnacles as it ages").
So let's anticipate that: do you have any reasons to believe that Svelte will avoid adding accidental complexity/verbosity to it as it/the surrounding ecosystem matures, and if so, how do you think that will be mitigated?
Enough time has passed to firmly conclude that Stroustrup was wrong on that point. Other languages have withstood the test of time better than C++<11 and C++>=11 has dramatically improved the language by copying features from those other languages. C++'s issues were poor design choices, not simply some "maturity" force that causes a language to accumulate incoherent features.
The maintainers are very paranoid about adding complexity, and are not being funded by large corporations paying for features to get added.
The initial pages are Go templates which are hydrated with Svelte components. It took a bit of trial and error to get the flow right so that I don't have to write double the code.
I don't know if it's the next big thing or not but it works really well for me.
What is the advantage of doing this over using http.FileServer to serve html which imports your svelte generated javascript directly ?
Are you using Svelte in a part of your application instead of the entire application?
Maybe there's a better way to do it, but I like writing smaller components that can replace initial server-rendered HTML, and can then be imported into larger components.
https://undefined.fm/radio/vue-vs-svelte-with-evan-you-and-r...
I've used React, HyperApp and Flutter and Svelte (with Tailwind for CSS) is in my opinion clearly superior. But I also know someone who thinks Flutter is better.
I love it and will slowly be replacing my React/Vue/(old angularJS) projects with it.
The nice thing is, you can read the entire docs and just follow the interactive tutorial in a few hours and get up to speed incredibly fast.
I also get the feeling that the Svelte maintainers do not particularly care what the community wants and are building what they want, which is totally cool, but unfortunately I disagree with a lot of their choices so I guess it's not for me.
We have faced the usual wild west frontier situations where nobody really had an answer for something we wanted to do, but we have worked out solutions without a huge deal of frustration.
And it's important to mention that the development and maintenance experience of Svelte is very pleasant.
Svelte has been around for "a while" and seems to be hanging around and people are enjoying it.
I'm still really comfortable with React, and would love to know how people have found the transition between the two and how Svelte compares.