[mellosouls]

I read the main article which took some time to reach the conclusion a small footprint was the main point.

So I googled, found the Svelte homepage, and I'm still none the wiser as to why it might be an easy intro to web development.

Honestly, if Svelte is as easy as you suggest to get your head around, somebody needs to work on the presentation of that.

[spoiler]

I feel like like saying svelte is an "easy intro to web development" is misleading. The svelte compiler "abuses" (I don't mean it in a bad way) existing technology so it doesn't have to create special tooling and works with existing tools. I think that's okay _only if_ you're aware of this as a developer.

If I was hiring a JS dev, and someone _only_ had svelte on their CV, I'd be a bit reluctant to hire them, only because the svelte compiler hides a lot of JS warts (which I think people should be aware of).

[cpfohl]

Genuine question: where does the svelte complier hide JS warts? I've used Svelte for some production tools and personally in a few projects.

My experience thus far is that if you don't have at least a base-level understanding of JS you really can't use Svelte to its fullest. I can back up that intuition by having observed the svelte support channel on discord, where many of the questions really wind up being questions about javascript rather than Svelte.

[Vanderson]

I've been working with Vue for front end, but always keeping my eyes open to the future.

What do you feel Svelte is doing that hides "warts"?

Hacky stuff tends to turn me off from a tech. (I consider all my Vue work to be instant tech debt, because I know I will be replacing it down the road...)

[mvolkmann]

If you are referring to my article, "small footprint" is not the main point for me. The main point is ease development due to features like easier component state management, app state management with stores and sharing data between components with context.

[mellosouls]

To be fair to you I clicked on the article expecting a summary review rather than a technical run through and got as far as Why Consider Svelte on my small phone screen before googling. I can see on a revisit on my tablet it is rather more comprehensive.

[cpfohl]

Did you walk through the tutorial? It's _easy_. And the tutorial is kept almost 100% up to date with svelte version changes.

[mellosouls]

No, tbh by the time I got there I had lost interest. I'm not commenting on the value of Svelte, just saying I felt the benefits of investing time in investigating it in the context of a myriad of established tools and frameworks needed to be more clearly sold.

[treggle]

Agreed. Lots of praise, no explanation.

[nailer]

Svelte is:

- smaller (it compiles your app, and doesn't include itself in the results)

- faster (no virtual DOM, the data to elements are mapped at compile time)

- simpler - `age = 30` no boring state management.

You're right about the web page - I wanted them to drop 'Cybernetically enhanced web apps' for 'smaller faster simpler' - there was a GitHub issue for it: https://github.com/sveltejs/svelte/issues/3269