I work in the corporate event space so I’m used to seeing companies do the big song and dance thing to get their message out. I love that this just gets right to the core of what the audience/community needs and wants to know. The fact Rich didn’t even need to leave his desk to convey it is a plus to me; it sets the tone that this may be important but it’s only work and no one should be spending their time learning songs and dances (or having to endure them) to promote the idea when the idea speaks for itself. Thx to all involved.
i didnt think it was possible for Rich’s talks to get better than theyve been, but my god the entertainment and information value on this one. LOVE IT gang!
@silaspy-ff2ne one example is inside your svelte markup and you try to access an object from your script tag {object.aNumber}, I can't use a type assertion. Say I have a component that expects a string, but my variable is a number, I can't use {object.aNumber as string}. This is just one example, but in a larger SvelteKit project it leads to a fair a amount of just TypeScript work / work arounds to get rid of transpiler errrors, that don't really matter
lol funny and informative, thank you so much guys! I coded in v4 last year for personal stuff and loved it. These new changes look great, I'm going to start a new project with v5-rc next days
As usual Rich just being great. I wonder, if the angular people had known or thought about doing the same call Rich did here, instead of assuming that people would just happily migrate when they released Angular 2, if things would have been different today and React might just be a side player. Communication trumps everything!
I also dont agree on dropping slots. Slots are a native html feature, while snippets are not. So dropping slots is a bit wierd in my opinion. I been trying svelte 5 for quite some time now, I find snippets confusing and not easy to understand at all. On the bright side, I am very pleased with the other changes of svelte 5, runes make svelte so much better to work with.
Idk about the part. I feel like Rich glossed over that so hard. I personally tried it and it didn't feel like it solved problems for: - Being hard to use (There's literally more code you have to write) - Typesafety (I might be doing something wrong?? But I get no intellisense as to what slots are required, optional, etc?) In JSX, I find it a lot simpler because I can literally just pass a component into any prop and call it a day. I was hoping for the same kind of simplicity with Svelte but it's probably still ways to go.
are being replaced by `snippets` in svelte 5, which can be created like creating functions and passed as props between components. The issues you mention are with slots, not `snippets`.
@@ankitsaini2642 I didn't write "snippets" because I assumed that was already implied by "". That's my bad. But I am well-aware of slots being replaced by snippets. And as I've said "I have tried it" and it doesn't seem to solve the problems I've listed (which is what Rich was saying in the video btw). How is it (snippets) typesafe? How is (slots being) "hard to use" solved (by snippets)? It was just glossed over in this video.
I have seen many "great" projects getting the podcast treatment to buy more and more time, just to come late and short. I can only wait so much to try it out or move to next framework. Thanks
I have a project in production built with v4 and, while I understand the best intentions of these changes, I am starting to wonder if picking Svelte for a long-term project was a good idea. I have to rewrite so much that I am going to be done in time for v6 and its the next wave of changes of mind in Svelte core team. Worried.
It should be backwards compatible. So you can refactor bit by bit. I can assure you that its not a big deal, repacling props etc with its runes counterpart
I’m pretty sure I remember Rich saying he is British. He used to work for the Guardian newspaper before moving to the states to work at the New York Times.
I really loved svelte till v4. I don't care what's happening behind the scenes, I love svelte 4 black magic. Writing plain html javascript css and having the framework magically understand what I want it to do, that's amazing. Now if I have to learn framework specific terminologies anyway, why wouldn't I do it for frameworks with bigger communities and job market. I'll be sticking to v4 for as long as it's supported.
No one is arguing if it's better or worse. It's just not "svelte" anymore. The great thing about Svelte was that you didn't have to learn Svelte. That's not the case anymore.
Наука
"Some of you have yolo'd it into production" ... sets the tone perfectly :)
I work in the corporate event space so I’m used to seeing companies do the big song and dance thing to get their message out. I love that this just gets right to the core of what the audience/community needs and wants to know. The fact Rich didn’t even need to leave his desk to convey it is a plus to me; it sets the tone that this may be important but it’s only work and no one should be spending their time learning songs and dances (or having to endure them) to promote the idea when the idea speaks for itself. Thx to all involved.
Rich is as proud of svelte as I was as a child when I first fixed my bike on my own.
That glow in his eyes, so nice to see.
i didnt think it was possible for Rich’s talks to get better than theyve been, but my god the entertainment and information value on this one. LOVE IT gang!
I really like seeing influencer cross-over in the ecosistem
@@antoinelebaux3918haha havent been js influencer for a long time
I am super excited about the better TypeScript support in Svelte files :)
@silaspy-ff2ne one example is inside your svelte markup and you try to access an object from your script tag {object.aNumber}, I can't use a type assertion.
Say I have a component that expects a string, but my variable is a number, I can't use {object.aNumber as string}.
This is just one example, but in a larger SvelteKit project it leads to a fair a amount of just TypeScript work / work arounds to get rid of transpiler errrors, that don't really matter
@silaspy-ff2neOnly in the script part, not in the template part. Both work now.
@silaspy-ff2ne4:45
Boo hiss TSsss 🐍
HUGE and needed! You werent lying, Svelte 5 really is big
I don't even use Svelete for much, but I'm Rich Harris fan!
lol funny and informative, thank you so much guys! I coded in v4 last year for personal stuff and loved it. These new changes look great, I'm going to start a new project with v5-rc next days
What a great presentation! I've recently started learning about frontend development and I'm looking forward to giving svelte 5 a go.
Awesome job!
Another fun and informative talk from Rich! Thank you! ❤
Awesome and very promising. Loved migrating to Svelte 5, went smoothly
You give one of the best talks ever ❤
An upvote just for the confetti trick! And an upvote for the interesting info on Svelte 5.
As usual Rich just being great. I wonder, if the angular people had known or thought about doing the same call Rich did here, instead of assuming that people would just happily migrate when they released Angular 2, if things would have been different today and React might just be a side player. Communication trumps everything!
Estamos ansiosos del lanzamiento de Svelte 5
I also dont agree on dropping slots. Slots are a native html feature, while snippets are not. So dropping slots is a bit wierd in my opinion. I been trying svelte 5 for quite some time now, I find snippets confusing and not easy to understand at all.
On the bright side, I am very pleased with the other changes of svelte 5, runes make svelte so much better to work with.
Idk about the part. I feel like Rich glossed over that so hard. I personally tried it and it didn't feel like it solved problems for:
- Being hard to use (There's literally more code you have to write)
- Typesafety (I might be doing something wrong?? But I get no intellisense as to what slots are required, optional, etc?)
In JSX, I find it a lot simpler because I can literally just pass a component into any prop and call it a day. I was hoping for the same kind of simplicity with Svelte but it's probably still ways to go.
are being replaced by `snippets` in svelte 5, which can be created like creating functions and passed as props between components. The issues you mention are with slots, not `snippets`.
I liked the slots approach better, it was better separation of concerns
@@ankitsaini2642 I didn't write "snippets" because I assumed that was already implied by "". That's my bad. But I am well-aware of slots being replaced by snippets.
And as I've said "I have tried it" and it doesn't seem to solve the problems I've listed (which is what Rich was saying in the video btw).
How is it (snippets) typesafe? How is (slots being) "hard to use" solved (by snippets)? It was just glossed over in this video.
6:46 HAHA *important keystroke sounds*
So excited!!
Cleaner syntax! Nice!
Hahaha i like that old style phone :)
I love the mindset!
i remember my teacher used to say "Ask not what the school can do for you, but what you can do for the school".
You pay the school. If it is you do even more of it, it is a scam. If they teach you nothing, do not bless them with your wisdom.
This is 🔥🔥🔥, super excited
Hyped!
I wish there comes a tool like expo specifically for svelte cross platform application development
Someone reply to this comment when a really good Svelte 5 course drops. I'm willing to pay good money for one, I just need something really good 🙏
wow, very exited !!!
🎉🎊
Let's go!!!
Rich just gets it.
I have seen many "great" projects getting the podcast treatment to buy more and more time, just to come late and short. I can only wait so much to try it out or move to next framework. Thanks
Is there going to be a interactive tutorial about everything Svelte 5?
I have a project in production built with v4 and, while I understand the best intentions of these changes, I am starting to wonder if picking Svelte for a long-term project was a good idea. I have to rewrite so much that I am going to be done in time for v6 and its the next wave of changes of mind in Svelte core team. Worried.
It should be backwards compatible. So you can refactor bit by bit. I can assure you that its not a big deal, repacling props etc with its runes counterpart
i love svelte and i love this video
I have learnt Laravel waiting for Svelte 5.
Niiiice
🎉🎉🎉
Good talk thank you!
Sorry if my question is rude and/or off topic but what's his accent called? Is this something British?
Its a New Yorker accent
British
I’m pretty sure I remember Rich saying he is British. He used to work for the Guardian newspaper before moving to the states to work at the New York Times.
:)
Rich has been hanging around so many reactjobs at Vercel that they have brainwashed him into making svelte more like react.
I really loved svelte till v4. I don't care what's happening behind the scenes, I love svelte 4 black magic. Writing plain html javascript css and having the framework magically understand what I want it to do, that's amazing. Now if I have to learn framework specific terminologies anyway, why wouldn't I do it for frameworks with bigger communities and job market. I'll be sticking to v4 for as long as it's supported.
@@shubhindu Agreed and same here. If i'm going to learn some shitty syntax like what is introduced with svelte 5, I might as well learn to like react.
Goodbye, we won't miss the script kids who don't understand why svelte 5 is better for everyone
No one is arguing if it's better or worse. It's just not "svelte" anymore. The great thing about Svelte was that you didn't have to learn Svelte. That's not the case anymore.
@@JoshYxVdMchatgpt is comming 😂
🤣🤣🤣🤣🤣
Who are all the washed up thought leaders you speak of