This one does not make sense, because not matter how good some framework is, first u are working on current app in different framework and if u are from 3rd world country, probably u will work on app made with svelte kit, after 2-3 from now, when the app is already dead and badly developed from other people testing and play around the framework just for CV entries
@@danielbolivar9134 Ok here is explanation in nutshell: I'm working on a project in 3rd world country. The project was inherited from 1 developer that was jerking on the project, and probably have some weird fetish too. After his baby playground, he runaway from the company and now after puting crap and crap and crap and crap code on frontend, because client thinks more people, more developers on FE, even he works backend (hey!, how smart, right?) After the project is in post mortem stadium, we are returning the app from the dead, for 2+ weeks, and u know what, u get new API from stupid backend developers, just fo fun, instead solving performance issue. And now, go to your church and let everyone knows svelte is the new kid in the town because someone made todo app on youtube.
I was truly amazed when tried Svelte for the first time. It seems so elegant and simple that I was asking myself all the time: "why didn't humanity create it much earlier and was doing `this.foo.bind(this)` instead".
The creator himself knows how to simplify things while explaining them. No doubt they will be reflected in the creativity of the framework. Super simple and powerful features. Loving the power of Svelte Kit✌Thanks for giving us such a simple to use powerful framework.
That was an amazing presentation! Super clear, to the point and concise. This is up there with my favourite tech videos! The single super small note I could maybe add is that the sverdle part was a very little bit rushed. But then again: it also makes me want to find out how it works for myself.
Excellent presentation, Rich! It will be a good idea if you update the Documentation with these Must Have code snippets - CSRF tokens, XSS protection, Security Header policies, and everything other related to Security because many people want to use SvelteKit for serious projects with user authentication, database access, and SvelteKit must offer out of the box features like a Laravel and Django following the best practices. I think Sveltekit is the Only JS framework right now that do it in the right Way - Write Less code and have a Much More Joyful Developer Experience!
By comparison, both React and Vue have taken an enormous amount of time to onboard with as compared to Svelte. I'd say I was up and running with Svelte in about 3-4 hours. In those few hours, I was about as productive as I was with React or Vue when I had been using each for a number of months. I am so excited to see SvelteKit 1.0 has dropped and I hope I can find the time to build something with it soon! Seems like it may have a lot of the missing features needed to even consider it at my job!
Quite excited for 1.0 Svelte is really easy and even ships less javascript than Nextjs. I know Nextjs is more mature and more feature packed but still not every project needs that much of power. Svelte is a really a good fit and would developers and companies adopting it.
New to svelte(kit) and really enjoying it. One thing I’m confused about is the type generation. Rich mentions at 11:49 that svelte creates the types behind the scenes but I can’t figure out where that happens. I don’t see new types being generated when I add code that I’d like to type. Where can I read more about types and svelte? Thanks!!
Types are generated for load functions, page data etc when the dev server is running. They are placed under the .svelte-kit directory (it's something like .svelte-kit/generated).
Have been fooling around with SvelteKit for a while now. Looks fantastic so far! The only thing I am missing is server-side debugging with source maps :)
Great video, I do wish there was way more on how vite.config and svelte.config worked. I'm trying to build a static site AND a dynamic site with backend into two separate build folders and its not easy to understand documentation on that. Or if its even possible to create a custom output path.
Is there a way to post a form action without any form or input tag, just within a JS function? This would make posting data to the server so much easier and more flexible.
You wouldn’t have to, the folder name is the “unique” page name you’re looking for. Can just search that and the folder with your +page and other files will be on top.
The way he throw acid and stabbed Remix in the face was pretty respectful. However, I wish sveltekit had a couple of features that Remix does. Having said that, SvelteKit is likely my next app.
Which features from remix would you like sveltekit to have? It’s interesting to see how many frameworks are consolidating on this new approach that is very similar between them
@@alexandrodisla6285 I believe Vercel is only funding Rich to develop Svelte further. I don't think Vercel is involved in development except funding Rich.
Sounds like an interesting project, is it open source? I'm interested in dropping SPA's altogether and using compile time generated templates with something like htmx in front of a Rust API.
@@theLowestPointInMyLife Hmm, that's a strong opinion about the big picture. Also, I think I saw your comment on Theo's recent video about the rat race. It sounds like you've been programming for longer than I have and I like the stack that you use, would you be willing to bounce ideas off each other in a Discord or Matrix chat? Or make a friend?
@@oceanusdigital3621 Based on your github were on very similar timelines, 2017 start for me, 2018 for you. I just followed you on Github and added on discord.
Svelte had potential, but decision to invent a new dialect of JS kills it dead in the water. SolidJS has all of the benefits of Svelte and none of its flaws.
$: is not "a new dialect". Also, JSX is an abomination. If you think any framework that depends on JSX has no flaws, you are either delusional or suffering from Stockholm Syndrome. HTML&CSS in JS was a bad idea 10 years ago. It's an even worse idea today. Svelte is the closest you can get to plain HTML, CSS, and JS while using a framework. This means whether you are making a static HTML site or dynamic with Svelte, it's all basically the same.
@@mileselam641 Svelte decided to use module exports for properies. Let me directly quote the docs "Just like $:, this may feel a little weird at first. That's not how export normally works in JavaScript modules! " It only takes trying to make your first generic component or component with union props to realise, just how bad the idea is.
@@MagicNumberArg You are trying to write HTML&CSS in JS like React and therefore "fixing" a problem that shouldn't exist in the first place. When HTML is your base mental model to start with, this largely becomes a non-issue. And yes, export has been overridden. So now you've listed two bits of syntax that you equate to a whole distinct dialect while completely ignoring the cognitive overhead of createSignal(…) with [foo, setFoo], props object access, onCleanup(…) handlers, createEffect(…) to track reactivity, a render(…) function just to show some HTML, string template literals to use the framework, worrying about when to use createMemo(…) or not, explicitly subscribing and unsubscribing to stores, etc. But sure... Svelte redefined $: and export. 🙄 I reiterate: any framework that relies on JSX and other React-like library nonsense is fundamentally flawed. It's like Subversion's early motto "CVS done right" where CVS was a fundamentally broken model to start with.
@@mileselam641 you make it sound like Svelte is somehow different in its approach, does not have onDestroy or $:console.log(...). If you are using it, you already don't have HTML mental model. Compared to SolidJS, Svelte uses the same mental model, but with more magic and less well thought out synyax.
@@flogginga_dead_horse4022 people switched fromjQuery fast once other more organised frameworks came out, people are not switching from react because no other framework is AS organised. You missing the point of enterprise apps.
@@kivylius What exactly do you mean by organized? React is just a library. How is it organized? Now if you said Next or something that would make sense. Even Angular and Vue are more organized. I've been writing enterprise apps for 20 years. you? Also there is a whole lot of JQuery use still out there...
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Everything about svelte(kit) just screams developer experience. Props for building it, Rich!
This one does not make sense, because not matter how good some framework is, first u are working on current app in different framework and if u are from 3rd world country, probably u will work on app made with svelte kit, after 2-3 from now, when the app is already dead and badly developed from other people testing and play around the framework just for CV entries
@@MrEnsiferum77 wtf?
@@danielbolivar9134
Ok here is explanation in nutshell:
I'm working on a project in 3rd world country. The project was inherited from 1 developer that was jerking on the project, and probably have some weird fetish too. After his baby playground, he runaway from the company and now after puting crap and crap and crap and crap code on frontend, because client thinks more people, more developers on FE, even he works backend (hey!, how smart, right?)
After the project is in post mortem stadium, we are returning the app from the dead, for 2+ weeks, and u know what, u get new API from stupid backend developers, just fo fun, instead solving performance issue. And now, go to your church and let everyone knows svelte is the new kid in the town because someone made todo app on youtube.
I was truly amazed when tried Svelte for the first time. It seems so elegant and simple that I was asking myself all the time: "why didn't humanity create it much earlier and was doing `this.foo.bind(this)` instead".
@@MrEnsiferum77 can you write in English please?
The creator himself knows how to simplify things while explaining them. No doubt they will be reflected in the creativity of the framework. Super simple and powerful features. Loving the power of Svelte Kit✌Thanks for giving us such a simple to use powerful framework.
Sveltekit is very intuitive and simple. Really enjoying it so far!
That was an amazing presentation!
Super clear, to the point and concise. This is up there with my favourite tech videos!
The single super small note I could maybe add is that the sverdle part was a very little bit rushed. But then again: it also makes me want to find out how it works for myself.
Excellent presentation, Rich!
It will be a good idea if you update the Documentation with these Must Have code snippets - CSRF tokens, XSS protection, Security Header policies, and everything other related to Security because many people want to use SvelteKit for serious projects with user authentication, database access, and SvelteKit must offer out of the box features like a Laravel and Django following the best practices.
I think Sveltekit is the Only JS framework right now that do it in the right Way - Write Less code and have a Much More Joyful Developer Experience!
I agree with you. The documentation should be updated
By comparison, both React and Vue have taken an enormous amount of time to onboard with as compared to Svelte. I'd say I was up and running with Svelte in about 3-4 hours. In those few hours, I was about as productive as I was with React or Vue when I had been using each for a number of months. I am so excited to see SvelteKit 1.0 has dropped and I hope I can find the time to build something with it soon! Seems like it may have a lot of the missing features needed to even consider it at my job!
Quite excited for 1.0
Svelte is really easy and even ships less javascript than Nextjs.
I know Nextjs is more mature and more feature packed but still not every project needs that much of power.
Svelte is a really a good fit and would developers and companies adopting it.
Vite and Svelte are 2 of the coolest tech tools I have discovered in the last 5 years
Can't believe it's finally in 1.0 😭 so good
New to svelte(kit) and really enjoying it.
One thing I’m confused about is the type generation. Rich mentions at 11:49 that svelte creates the types behind the scenes but I can’t figure out where that happens. I don’t see new types being generated when I add code that I’d like to type.
Where can I read more about types and svelte? Thanks!!
Types are generated for load functions, page data etc when the dev server is running. They are placed under the .svelte-kit directory (it's something like .svelte-kit/generated).
Congrats on the 1.0 milestone, and thanks for sveltekit!
SvelteKit is the best framework ever.
Have been fooling around with SvelteKit for a while now. Looks fantastic so far! The only thing I am missing is server-side debugging with source maps :)
This looks amazing.
Incredible project, thanks!
That cookie state example on a server side is amazing 10:54
Simple yet powerful 👌
it there a repo for this presentation?
Great video, I do wish there was way more on how vite.config and svelte.config worked. I'm trying to build a static site AND a dynamic site with backend into two separate build folders and its not easy to understand documentation on that. Or if its even possible to create a custom output path.
Can we get a source code too look through this small app?
Does it support BOOSTRAP?
does it have server side debugging?
Now i have using sveltekit for my project. I hope in next version of sveltekit have websocket support's
The component structure is really similar to vue js which makes it’s very for beginners to pickup
I wish sveltekit had endpoint layouts (per endpoint hooks)
Does anybody know how the "hover component to open in vscode" is possible?
Just a guess:
The development server adds the feature to your page, on components selection it communicates with vscode debug api to make the match
@@MrEvilGalith in all cases, a top notch DX
I'm wondering if it's possible in neovim
Is there a way to post a form action without any form or input tag, just within a JS function? This would make posting data to the server so much easier and more flexible.
You can without js though. Really easy
Im so happy 1.0 is out❤!!
Legendary 👌
Love you Rich !!
Awesome 🤩
great overview
6:15 lol. most of the time when i navigate to another page, i do not want to select a needle in a haystack of the same names.
You wouldn’t have to, the folder name is the “unique” page name you’re looking for. Can just search that and the folder with your +page and other files will be on top.
@@danisimeonov4759 fair point!
The way he throw acid and stabbed Remix in the face was pretty respectful. However, I wish sveltekit had a couple of features that Remix does.
Having said that, SvelteKit is likely my next app.
Which features from remix would you like sveltekit to have? It’s interesting to see how many frameworks are consolidating on this new approach that is very similar between them
Wow! inspector: true; 😲
1.0 loading
finding a good svelte tutorial is not easy. that's what's holding me back from learning it, that i might not find resoucres to fix bugs
search for crash courses
I’m stalking svelte kit 1.0 milestone page
We need websocket support
Just run a second server
I feel bad for all those people who are still working with jQuery 😅
9:37 gosh my dirty mind
Man he types very fast
Its sped up
I didn't realize Svelte was developed by Vercel. Vercel does a lot of huge things nowadays, don't they.
Rich Harris develop svelte, sapper (abandoned) and sveltekit with the core team.
Vercel offer them to come and work fulltime on svelte and sveltekit
@@alexandrodisla6285 I believe Vercel is only funding Rich to develop Svelte further. I don't think Vercel is involved in development except funding Rich.
I'm using Solid JS with C++ backend, good luck with your server side rendering.
Sounds like an interesting project, is it open source? I'm interested in dropping SPA's altogether and using compile time generated templates with something like htmx in front of a Rust API.
@@oceanusdigital3621 not open source no, unfortunately everyone is pretending money is important and forcing each other to have some in order to live
@@theLowestPointInMyLife Hmm, that's a strong opinion about the big picture. Also, I think I saw your comment on Theo's recent video about the rat race.
It sounds like you've been programming for longer than I have and I like the stack that you use, would you be willing to bounce ideas off each other in a Discord or Matrix chat? Or make a friend?
@@oceanusdigital3621 Based on your github were on very similar timelines, 2017 start for me, 2018 for you. I just followed you on Github and added on discord.
9:39 pushy and fussy 👁👃👁
Common good? İ disagree on that, united nations has nothing to do with common good. 🇵🇸🇵🇸🇵🇸
😚 promo sm
UN... DoT.... The comparison of Vite with them is just plain idiotic.
Svelte had potential, but decision to invent a new dialect of JS kills it dead in the water. SolidJS has all of the benefits of Svelte and none of its flaws.
When solid decided to call a component “A” I stopped trying it immediately. Bad design.
$: is not "a new dialect". Also, JSX is an abomination. If you think any framework that depends on JSX has no flaws, you are either delusional or suffering from Stockholm Syndrome. HTML&CSS in JS was a bad idea 10 years ago. It's an even worse idea today. Svelte is the closest you can get to plain HTML, CSS, and JS while using a framework. This means whether you are making a static HTML site or dynamic with Svelte, it's all basically the same.
@@mileselam641 Svelte decided to use module exports for properies. Let me directly quote the docs "Just like $:, this may feel a little weird at first. That's not how export normally works in JavaScript modules! " It only takes trying to make your first generic component or component with union props to realise, just how bad the idea is.
@@MagicNumberArg You are trying to write HTML&CSS in JS like React and therefore "fixing" a problem that shouldn't exist in the first place. When HTML is your base mental model to start with, this largely becomes a non-issue. And yes, export has been overridden. So now you've listed two bits of syntax that you equate to a whole distinct dialect while completely ignoring the cognitive overhead of createSignal(…) with [foo, setFoo], props object access, onCleanup(…) handlers, createEffect(…) to track reactivity, a render(…) function just to show some HTML, string template literals to use the framework, worrying about when to use createMemo(…) or not, explicitly subscribing and unsubscribing to stores, etc. But sure... Svelte redefined $: and export. 🙄 I reiterate: any framework that relies on JSX and other React-like library nonsense is fundamentally flawed. It's like Subversion's early motto "CVS done right" where CVS was a fundamentally broken model to start with.
@@mileselam641 you make it sound like Svelte is somehow different in its approach, does not have onDestroy or $:console.log(...). If you are using it, you already don't have HTML mental model. Compared to SolidJS, Svelte uses the same mental model, but with more magic and less well thought out synyax.
Wipe your greasy camera, my man
Still no where near how good reactjs is. Organisation way to messy.
people only still use react because it's popular. It's actually the worst at this point.
@@flogginga_dead_horse4022 people switched fromjQuery fast once other more organised frameworks came out, people are not switching from react because no other framework is AS organised. You missing the point of enterprise apps.
@@kivylius What exactly do you mean by organized? React is just a library. How is it organized? Now if you said Next or something that would make sense. Even Angular and Vue are more organized. I've been writing enterprise apps for 20 years. you? Also there is a whole lot of JQuery use still out there...
Because of these small minds that people still uses react.. (And other crappy stuff for that matter)