Svelte Is Good For Beginners

Recorded live on twitch, GET IN

By: Cameron Kauffman

Become a backend engineer. Its my favorite site

This is also the best way to support me is to support yourself becoming a better backend engineer.

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

Hey I am sponsored by Turso, an edge database. I think they are pretty neet. Give them a try for free and if you want you can get a decent amount off (the free tier is the best (better than planetscale or any other))

[cameronkffn]

Thanks for reading my article Prime! ❤
I hope everyone has svelte on their New Year’s resolution

[danielvaughn]

Svelte has the easiest onboarding experience I've ever had with a framework. I actually barely had to read the docs, I just skimmed it a bit for literally like 1-2 minutes and then started coding. When I was unsure about syntax, I'd just kinda guess, and 90% of the time I was right. It felt so intuitive.

My first 20-30 hours was fantastic - I was building a relatively complex app and was having a breeze. But then the honeymoon ended when I hit a snag with their reactive model, and my brain melted for several hours. There are some extremely unintuitive things about how Svelte reactivity works.

But still, overall it's a fantastic framework.

[bmehder]

I work for a school that is starting a web development class for beginners in a week. We are using Svelte for exactly the reasons Cameron explained.

[markwenzy]

3:20 I thought it was only me finding Svelte’s tutorial so satisfying since I’m not a SE and I’m learning software engineering just for fun, but turns out professionals have the same thought!

[readywhen]

I personally started with page builders lol, and never intended to become a web developer. Then I transitioned to coding with Astro, where eventually I started writing in svelte syntax, and finally switched to completely to svelte.

[xlxlxl]

Svelte(Kit) was my first (and only) framework, and can confirm, it's been an excellent tool for a relative beginner.

[rando]

i write backend mostly but to show what i did to my friends they care a ton about ui since its what they see,
it helps that i can write some ui using a ui library/daisyui and svelte instead of smth hard.

[aiyazmostofa]

For me, getting into frontend development through a Javascript framework, svelte was so easy and buttery. So when I got to react, it was quite easy because I knew a lot of the theory and terms already.

[antontsvil]

Sup Prime, your reading skills are growing blazingly fast, also I am learning programming for three years yet didn't get any clue what's going on when I'm working with react and Typescript is a struggle but testing react is real pain for me

[TheMrSinek]

I started with svelte as beginer, ... and i'm happy that I don't need react :D

[theIbraDev]

been a hardcore svelte enjoyer since 2020. I love Primes love for it.

[nightshade]

I think Vue is underrated, Vue is very easy to use and is even easier than svelte, you can even use vue without a build step and put it directly in your html if you want, even the composable api, making it even easier for beginners while retaining all the power

[HyperionStudiosDE]

Nobody actually thinks React is good for beginners (or anybody really) unless the have Stockholm Syndrome. React was just one of the first, not the best.
I might try Svelte or HTMX but I'm pretty happy with Vue already.
Although it does get uncomfortably complex when I have to use SSR for SEO purposes which makes me want to go back to static websites.

[theangelofspace]

And here I am trying to decide if I should ditch react for vue, and now you said use svelte.

[XRENDERMAN]

Here I fixed your title: "Svelte is better."

[Lemmy]

Totally agree, svelte is the best place to start because it's the closer to vanilla js syntax and it easily integrates with everything that was built for vanilla js. React on the other hand is a very "closed" ecosystem and practically inacessible from any other framework.

[hoshiya]

That "what" at 6:10 is really really relatable

[baldpolnareff]

I’m curious about your opinion on Vue3. I tried it a little bit a few months ago and it felt quite intuitive after knowing a little bit of HTML, CSS and JavaScript.
I don’t have a comparison to be fair, but the composition API felt nice to use

[jamesmoynihan]

Svelte is what made web dev finally click for me. I think it's partly the presentation/interactive teaching, and partly the framework semantics.

1). The interactive tutorial IS amazing, and the REPL is a great place to prototype and play for anyone.
2) Svelte simplifies and streamlines a lot of the issues beginners deal with (DOM manipulation, data binding, scoping CSS, build/dev tools, etc.) and lets you use terse syntax to just MAKE STUFF.
3). Opinionated frameworks --ones with a specific/singular way to do something, like naming or routing-- are inherently easier to learn.
4) There are still "gotchas" in complex Svelte apps, but they're actually getting fixed and improved with new versions. There's something to be said for the strength of the community, and the energy of the maintainers. Rich Harris embodies "It doesn't have to be hard -- we can do it better!"

[nic_s]

As javascript frameworks go, I think Svelte is probably the better one in general. However, it suffers from the same tool chain problems. Sure, you can follow the tutorial and get things running, but do you actually understand what it's doing? If you're just starting out, probably not which will be incredibly frustrating when things go wrong and you don't know why.

Another drawback for me was that my front end was one project while the back end was a different project. This created this weird split in our team as some were front end and others were back end and a lot of time went into just keeping these 2 projects in sync which was something we only realized after we moved away from this structure.

This is what makes HTMX, and concepts like HTMX, so great. There's no front end project templates, no setup, and no build step... it's a vanilla JS library you add to your page and that's your front end setup done. Here and there you write a little bit of vanilla JS, but it really is almost nothing. You are left with pretty much just the back end and a single project and your team is no longer split in 2 as everyone is now working on the same project as just 1 team.

HTMX, or concepts like it, is not the answer to everything, but you will be very surprised how often it is and it's fantastic.