This is more like Vue now. Nice. In Vue though there are more options to create multiple components in one file. Like Render functions, Jsx, or createReusableTemplate from Vueuse (which I prefer). 😊
my question is what would multiple components in a single file even look like? Svelte markdown is already at the "top-level" of the document, so would it now have to be nested?
Just a separating line like in the "Front Matter" format? It can be assigned a special meaning given that few HTML-s out there have a bunch of dashes aligned to the start of the line...
even if using detached jsx fragment everywhere in react feels good, it doesn't mean it's good. Often, innate reflexes push you towards anti-patterns. Multiple component per file and tons of fragment dangling are messy, harder to maintain and read
Great video def checking out Svelte 5! Stoked for Vue-ish stuff that just wrings out simplicity. Aside: are you aware of any mobile/hybrid options using Svelte? Research has turned up mixed results
i was happy with Svelte 4, but i'm also happy with Svelte 5. if we put aside the large ecosystem and more job opportunities it's still much better than React. Choosing over Vue 3 etc. is just a personal taste. Nothing new. We need more impressive innovations for future versions.
Guess I'll just go back to react. It was nice while it lasted, we all enjoyed the old svelte because of the syntax & simplicity...it's hard to go from that(the old svelte) to this...the simplicity of svelte was what made us all love it & chose it over react & the others
You clearly haven't tried svelte 5 yet. Everyone that has tried svelte 5 went in with a lot of bitterness and came out happier. You don't know what you're missing, but be my guest and go to react again. Can't wait to see you manually tracking dependencies and debug rerendering performance issues 😄.
@@Hugos68 I'm about to start to use svelte on my side projects. do you have any tips or recommendation to het through it? or make my experience somehow fun?
Multiple components in one file is hell. I know people think is better. Its not. Sometimes the restrictions makes you better. Snippets are just the thing we need, because it makes componentes more readable.
Same thing as React just different buzz names. I'm not surprised everyone keeps choosing React. First hooks, then "composables" and now "runes". Things are not evolving.
Its a common first observation. Looking at it there are similarities. Hands on shows you the difference. Your conclusion seems wrong. But hey go go go react
Why would you want more than one component in a file? How would you and other people navigate this codebase when you no longer know where to look for it?
it can be useful when you have a part of a component that you just want to abstract out, like say a list item, but it isn't worth creating an entirely new component file because you're not doing much in terms of logic, just templating.
@@pookiepats I don't care how it's generated, but I do care about verbosity, code base size, mental load etc, etc. Basically, it is about future velocity and ease of supporting the code base. React is the worst thing ever created in that regard that happened to become popular. It just slows your dev process to a halt, unnecessarily complicates things and forces you to write tonnes of boilerplate code. I don't think that ANY step in that direction should be applauded.
I wished, they would be more clear with the "Stores". Purely seen from Svelte 5, they are gone. However, to not break backwards compatibility, their functionality still exists. The new Method isn't exactly "Stores". It's just State-Vars wrapped in different Scopes. I'm a bit torn on that one. On one the positive side, anyone can now define themselfs how their "Store" should work. On the negative side, anyone can now define themselfs how their "Store" should work. So 10 different people, means 10 different ways for a "Store" to work.
yeah but isnt svelte more performant? And being able to build to vanilla code is useful. But yeah all these frameworks are the same now. Might as well just use react 🤷♀️
Even with it's compiler, the speed improvement is marginal since Vue's reactivity is already signal based, and once Vue releases it's Vapor compiler, it won't matter at all. Also, Vue follows the HTML spec closer than Svelte. In fact, Rich Harris of Svelte has just realized the importance of this and is making improvements in Svelte 5 to be more HTML spec compliant, while Vue has been spec compliant for years. Svelte 5 removes the point of differentiation from Vue with its addition of runes, computed, and refs. You might as well just use Vue for the same API with larger support and job opportunities, unlike Svelte.
@@bmdavis419 yeah I have seen your video on Theo's channel I had no idea about that looks good but still curious what's in your arsenal I am sure it's goona be banger.
The documentation was probably my biggest gripe about Svelte 3 when I tried using it last. Nice to see improvements and consolidation there!
This setup is too similar to Theo's (I love it btw)
it is theo's setup
With way less ego
@@JamesHoffmannLover its literally the same setup
Hopefully with less deceiption.
They filmed it together 😂
I prefer one component in one file for naming conventions for the file
Me too but there are certain scenarios where snippets are nice
I personally think snippets are a great solution to multiple components in a file, if you want more than that then you just want React
This is more like Vue now. Nice.
In Vue though there are more options to create multiple components in one file. Like Render functions, Jsx, or createReusableTemplate from Vueuse (which I prefer). 😊
Look who I found here😂😂😂
@@zayne-sarutobi 👋🏾😅
my question is what would multiple components in a single file even look like? Svelte markdown is already at the "top-level" of the document, so would it now have to be nested?
{#component} or something maybe
Just a separating line like in the "Front Matter" format? It can be assigned a special meaning given that few HTML-s out there have a bunch of dashes aligned to the start of the line...
Would be so funny if Theo in your video and you in Theo video
can you make a tutorial for svelte 5 and how to use it in sveltekit
why did you compare a standard writable with a custom rune state ? Compare the rune with a custom writable
where can I get your vscode settings? looks damn pretty
even if using detached jsx fragment everywhere in react feels good, it doesn't mean it's good. Often, innate reflexes push you towards anti-patterns. Multiple component per file and tons of fragment dangling are messy, harder to maintain and read
Says you, freelancers love it
Sweeping statement, definitely false
Deja Vu
why? React?
what vscode theme are you using? looks different from your latest vscode setup video
GitHub dark default
Svelte single component per file is super clean, multiple components would only makes the files bigger and harder to read.
Great video def checking out Svelte 5! Stoked for Vue-ish stuff that just wrings out simplicity. Aside: are you aware of any mobile/hybrid options using Svelte? Research has turned up mixed results
The snippets thing you can do that in react too. You would make a function and then use the function in both places {render()}
Yeah they said they'll be removing the legacy mode in Svelte 6 in the release candidate announcement IIRC.
Thanks a ton for the video....can you please name an updated ui library for svelte5
For now they don't actually need to be! Svelte 5 is fully backwards compat so u can upgrade slowly
@@bmdavis419 Thanks that helps..
Multiple components in one file enables developers to do stupid stuff. Let's not allow it. 😱
They did, do and would any way and day.
God the code at 8:51 made my eyes bleed. How are javascript devs ok with this? Do they not see the problem that this is all unneeded complexity?
They are used to it
$effect is complained when using with async
i was happy with Svelte 4, but i'm also happy with Svelte 5. if we put aside the large ecosystem and more job opportunities it's still much better than React. Choosing over Vue 3 etc. is just a personal taste. Nothing new. We need more impressive innovations for future versions.
They definitely fucked it up. I will stick to the versions before the deprecations.
Guess I'll just go back to react. It was nice while it lasted, we all enjoyed the old svelte because of the syntax & simplicity...it's hard to go from that(the old svelte) to this...the simplicity of svelte was what made us all love it & chose it over react & the others
I'm of the same sentiment... I however won't be going to react either
You clearly haven't tried svelte 5 yet. Everyone that has tried svelte 5 went in with a lot of bitterness and came out happier. You don't know what you're missing, but be my guest and go to react again. Can't wait to see you manually tracking dependencies and debug rerendering performance issues 😄.
@@Hugos68 I'm about to start to use svelte on my side projects. do you have any tips or recommendation to het through it? or make my experience somehow fun?
@@franklinsecretario3862 Go through the svelte tutorial!
Multiple components in one file is hell.
I know people think is better. Its not.
Sometimes the restrictions makes you better.
Snippets are just the thing we need, because it makes componentes more readable.
Is it just me, or does this look like VueJS composition API from 5 years ago? :D
Always has been. Svelte is just a Vue knock off without job listings lol
@@hamm8934hell yea brotha, with a worse ecosystem and jankier API 😂
holy shit the vue fanboys are insufferable. Imagine bringing down other frameworks just to gas your own. It's not that deep 😂
@@hamm8934ok
@@pookiepats"worse ecosystem" its literally a javascript ecosystem...
"jankier api" yeah this guy doesn't read the docs
Same thing as React just different buzz names. I'm not surprised everyone keeps choosing React.
First hooks, then "composables" and now "runes". Things are not evolving.
Its a common first observation. Looking at it there are similarities. Hands on shows you the difference. Your conclusion seems wrong. But hey go go go react
Except performance. React is slow
Why would you want more than one component in a file? How would you and other people navigate this codebase when you no longer know where to look for it?
React exist and does this, foolish question. Obviously it is viable
@@pookiepats react existence is foolish in itself.
it can be useful when you have a part of a component that you just want to abstract out, like say a list item, but it isn't worth creating an entirely new component file because you're not doing much in terms of logic, just templating.
@@XRENDERMAN it’s foolish to spend so much energy caring should how html gets generated
@@pookiepats I don't care how it's generated, but I do care about verbosity, code base size, mental load etc, etc. Basically, it is about future velocity and ease of supporting the code base. React is the worst thing ever created in that regard that happened to become popular. It just slows your dev process to a halt, unnecessarily complicates things and forces you to write tonnes of boilerplate code. I don't think that ANY step in that direction should be applauded.
I've barely started learning and I've just stopped enjoying it :(
I wished, they would be more clear with the "Stores". Purely seen from Svelte 5, they are gone.
However, to not break backwards compatibility, their functionality still exists.
The new Method isn't exactly "Stores". It's just State-Vars wrapped in different Scopes.
I'm a bit torn on that one.
On one the positive side, anyone can now define themselfs how their "Store" should work.
On the negative side, anyone can now define themselfs how their "Store" should work. So 10 different people, means 10 different ways for a "Store" to work.
Here is an advise so you don't depend on framework author decisions: decouple your view from your logic. You're welcome
Wake up!
IMHO nothing beats React at making things easy to reason about. I would put Vue in second!!
so why not use react now？
That;s all !? That's all the good parts of svelte 5? Wow. Clearly not someone who followed svelte since Svelte 1.
Clueless.
Just use Vue lol. Its the second largest ecosystem and is 95% the same exact API.
yeah but isnt svelte more performant? And being able to build to vanilla code is useful.
But yeah all these frameworks are the same now. Might as well just use react 🤷♀️
Even with it's compiler, the speed improvement is marginal since Vue's reactivity is already signal based, and once Vue releases it's Vapor compiler, it won't matter at all.
Also, Vue follows the HTML spec closer than Svelte. In fact, Rich Harris of Svelte has just realized the importance of this and is making improvements in Svelte 5 to be more HTML spec compliant, while Vue has been spec compliant for years.
Svelte 5 removes the point of differentiation from Vue with its addition of runes, computed, and refs. You might as well just use Vue for the same API with larger support and job opportunities, unlike Svelte.
Still waiting for the cyber Stack video please make something like CJ did on the syntax channel building NextJS boilerplate from scratch Please.
Was gonna post that tmrw, but uh the svelte team kinda nerd sniped the FUCK out of me. They made something better: "npx sv create"
@@bmdavis419 yeah I have seen your video on Theo's channel I had no idea about that looks good but still curious what's in your arsenal I am sure it's goona be banger.
first lol hehe
all these frameworks now look the same.. dont really like it.. javascript folks are real sheep like.. same setups, same styles...