I use react at work, but your videos + svelte's runes introduction (fantasy nerd here) made me delve into svelte whenever I have some spare time. kidas brate!
Amazing video as always! I really love your content. I've noticed there isn't a good video explaining all the i18n options for sveltekit available and comparing them. It could be a good idea for a future video and I'm sure that your audience would be very interested to it.
"Svelte's runes are giving me serious MobX vibes! The computed values, reactions, and tools like when and trace feel so familiar. I am big fan of a mobx , now svelte too
I love your content, I am about to start getting into Svelte and am super excited, this looks so much easier than other frameworks. You should start exporting in 4k. Even if you recorded in 1080 it increases the bitrate and makes it look much better. Your videos are beautiful they deserve max bitrate
Looks like MVC is back on the menu boys! Having written a diagram app using Svelte 3 and interactive components derived from class states, Runes look like a dream come true.
I am just waiting for melt-ui to be runified. It would be a pain to start coding with its stores paradigm and then change to runes. The refactoring required is akin to rewriting the client code from scratch.
Please is there like a PDF document that one can learn about svelte 5 ... i really loved Real-World Svelte: Supercharge your apps with Svelte 4 by mastering advanced web development concepts By Tan Li Hau cant we have something like that for svelte 5
@@francoisbouchet9907I’ve found that having side effects similar to subscribing to a store is a bit rough (outside of svelte components). Runes don’t really replace stores imo.
@@francoisbouchet9907 Sveltekit 5 supports stores and even introduces local stores with .svelte.js extension. I am running SK5 Runes mode with local and global stores. No rewrites needed except local need that extension.
@@JoyofCodeDev its very sad. Really good video otherwise. Im guessing its because of the dark nature of the video. These compression strategies usually compress many dark values together because its more difficult to distinguish between them. Next time i would recommend you upload in a higher resolution like 4k or use 30fps instead of 60
svelte is for lazy people like me who dont wanna dive into overcomplicated react bullshit and its stupidass ecosystem. if i have to use this effect and state fake ass react shit, i will use react directly
Svelte 5 == Almost Solid.js but with $ prepended so they can continue to implement a compiler and experiment with abstractions instead of finding elegant ways to do simpler functional programming. In my opinion Solid.js is superior, simpler, more elegant, not because it adds terser syntax or more bells and whistles, but simply because it achieves the same things using just the programming language itself and well design, and just the right amount of, abstractions. It's also my opinion that learning the language itself is the biggest problem in the JS FE world. No offence but too many people learn JS by learning React first or some other framework, because that's what they want to do at work, but that's not what being a good programmer is. /endrant
Nope. Solid doesnt reach what Svelte can reach. Solid is just react with signals. Svelte is quite different, in the big picture it shows how simplicity at its finest can improve your day to day.
I like abstractions. I'm not a hardcore developer, just a hobbyist, so having some opinionated magic is great. No disrespect to solid, is a great framework, but it didn't clicked for me although it was on top of my list. To be honest, if not for some great svelte edutainers I would be using solid, or maybe vue.
I think you misunderstood completely how Svelte3/4 worked and how Svelte 5 it does. Just because Svelte5 is using Signals ( like Vue ) you think that is almost Solid. This is like the people who thinks that Svelte5 looks like React because has $effect(). Please, try to learn and read deeper: devs are responsible at some point about companies decisions in the future regarding tech stack to use.
If you don't use these libraries with your side-project as they would make your development easy, don't ever use them. They are dead for professiononal web development and you wouldn't learn anything about anything because you'd take everything as granted, React is popular because you do everything, it's plain javascript that poops html, thats it
I hope I'm misunderstanding your sense of humor, but I personally prefer my development to be easy rather than hard. As for not learning anything, how is that possible? After all, "these libraries" are open-source, and the code is there to be examined and learned from. And furthermore, I truly believe you need to learn, and learn well, how to use them despite their (apparent) simplicity.
@@paolo-e-basta yes, a javascript junior developer would go through source codes. React is not hard, nor Next, they are tools to make something work, if this something is too much for your project, of course don't use it, but then don't talk about it either.
@@ddddddkkkaSvelte is also a “[tool] to make something work.” So what’s your point? Ironically, the layout of svelte is closer to vanilla html/js/css than something like react/jsx; if anything, a beginner learning svelte will learn more about vanilla html/js/css vs one learning react.
@@JJCUBER React is not there to make you learn html, I was talking about normal people who are not 5 years old and jump to a framework without knowing basic concepts of frontend. You too know that frameworks like Vue and Svelte is out there because PHP developers didn't want to learn frontend, these are frameworks that gives everything out-of-box and can make basic projects that are mostly/strictly bound to some backend. Not so great for a student that wants to know how a real application should work and the inner concepts of a frontend system, they are great if you want "magic" with a one click though.
Great overview. I've spent a lot of hours on svelte and am quite comfortable with the quirks of the current version. I find it more kinda hard to wrap my head around what magic happens with $state. Especially the props thing doesn't seem super intuitive. I'm sure I'll get used to it but saying it's "easier" or clearer kinda feels like a lie.
I think `let count = 0` is more magic than `let count = $state(0)` which works the same inside and outside Svelte components - what makes Svelte special isn't `let count = 0` but `=` for reactive assignments.
Before I learned Svelte, I used React, then SolidJS. When I learned Svelte 3, in my opinion, it was simpler and it was the best language and framework. In my opinion, Runes will destroy this framework, something that was simple now start going to React again. The only difference between SolidJS and Svelte now is where you have XML and where JS.
Currently rewriting a mess of a nextjs project in sveltekit. Im using svelte 4 because rich said svelte 5 is not yet ready for production but man does svelte 5 seem like a MAJOR upgrade from svelte 4. excited to see when is comes out officially to start migrating!
Any issue with runes and form submission? On initial load I initialize form fields to the last record added, except one "index" field which is incremented by 1 - Its a read only field. Works fine on initial form load. I can change field value and using state, derived, effect everything works fine. When I submit, record gets saved fine but then the form fields will not reinitialize as when component first loaded,/ Instead fields values default as if I have no records despite setting them correctly. Worked fine with SK4 reactives. Any thoughts? (@ 11.56 on:keydown )
i love svelte, i am always afraid to dedicate myself to learn it fully because i feel i can't get a job with it, but i really enjoy so much developing in svelte.
@@JoyofCodeDev Oh, sovereign joy of code, no matter how metaphorical or cheesy it may seem, I was waiting with the greatest subtlety for any response from you, and since you have heard this sentence, I must enjoy coding what I love. Furthermore, if UX and UI are for the user, from now on I proclaim DX & DI: Developer Experience & Developer Interface :) however, thanks a lot
