SvelteKit is my mistress 

LMAO

your prayers/pull_request have been heard/merged

the time is ticking, in 1 years it will be something else

hahahah fucking yes

Hopefully, many SvelteKit jobs popup

Angular

@@Tobias-mz7nm Angular has been in slow decline since 2018, I think it's unlikely to rise again but who knows

we'll all probably switch to web components or something completely new eventually

@@MeatCatCheesyBlaster yeah, svelte compiles to web components

@toast i can’t wait for this day

That's awesome! Been doing angular for 3 years but the ecosystem is so closed off from non-angulat-specific packages I am looking to learn svelte now.

@@jonnyd6087react is better if you’re looking for work otherwise up to you and yea I realise this is 10 months old

Yeah man, the interactive tutorial is incredible. Whenever I have any doubt I return to the tutorial and it feels amazing

I worked with react, Vue and Svelte (a bit). react is garbage

I think that of javascript cause I learned python first haha

As a long time react dev just picking up svelte I immediately thought the same

I tried sveltekit kit and I don't like it lol. there's some typescript stuff that need work around that makes me frustrated.

after learning c,cpp,java... js was a breeze... until i saw react and throwup... i stopped front end at that point until i discovered svelte....

Coming as a rookie Nuxt developer (with some medium-sized personal project experience) and after watching this introduction video, I myself don't find SvelteKit as simple as Nuxt. For simplicity, it comes to balancing convention vs configuration. (Like React is just too much configurations and choices and they trynna balance that with Next.js, and Angular's too much convention) And just from watching this video, I see a little too many conventions in SvelteKit compared to my experience of using Nuxt. Also, page configurations through `export const`, just curious would IntelliSense support this? Since you have some experience on large-scale projects, would you say that these design decisions are trade-offs out of concerns for the robustness of large apps (like a bunch of pages that start with `+`) so it would be "harder to break stuff and hurt performance"? If you have experience with Nuxt, how would you rate Nuxt from the robustness perspective?

@@leap8351 I’ve never worked with Nuxt so I can’t compare. The biggest feature in SvelteKit isn’t the metaframework itself but the fact that you write Svelte. To write stuff in Svelte is as productive as one can get for reactive frontend development. Really, try it in some project. Regarding the file system decisions, SvelteKit 1.0 just launched and all the projects I’ve worked on were made in older versions of the framework, so I still have no practical opinion wether it is a good change or not. But if you’re not amused by SvelteKit 1.0+ way of handling routes and files, you can always use alternatives like Astro, Routify, or even Svelte itself with Vite and a client-side router such as Tinro. I myself used Tinro for some of the projects who were SPAs when SvelteKit didn’t even existed yet.

agreed man! I messed around with Svelte for a couple hours when I first heard about it and loved it. it's simplicity was amazing and it truly seemed like a framework that was revolutionizing frontend development

Pienso lo mismo, ya ningun framework tiene sentido, vamos Svelte!. a seguir creciendo!.

I don't code, just researching how it works, but most of channels recommend vuejs but this one doesn't even mention it, so perhaps the opinion is not as objective

​@@martinkulik9466 He has recommended Vue (and related tools as Vite) in the past, and also you shouldn't take so serious this channel 😅

​@@martinkulik9466 vue is fantastic. I recommend using it

Yep, it moves so rapidly & so many “features” that get added & usually just cause more complexity. SvelteKit is the most sane framework of them IMO

Never stopped to think about it, but as a guy whose job is writing both, you're right.

Don't even start. As a kid I would write little homebrew PSP games in C++ and the haphazardly documented open source libs, then I picked up C#, built stuff in Unity for the hell of it even though the tooling wasn't anywhere near as sophisticated as it is now... but web development? It fucking broke me.

With Rust yea both web & system programming is much more sane using Rust compared to the wild west that is JS Frameworks, but to be fair because the JS World is changing and moving so rapidly we get all the nice things and innovations happening

@@fifty6737 I wish I was smart enough for Rust life, hopefully one day I will get there & although I am on the JS/TS side, totally agree with you.

Ikr? Why even struggle with React when you can just use Svelte.

When choosing a framework to "marry" I looked at Solid, Svelte & React (in that order). Svelte was the only one that I really looked into, and was the only one I ended up using. Honestly, some may say that it has a limited community, but now (it's not React, mind you), it's got pretty decent. The only thing that I had to make myself was a Modal component, maybe I'll add that little thing to GitHub and NPM someday.

I don't think you know what hands down means.

@@rayaqin Perhaps the gentleman meant to say hats off. I for one tip my fedora hat and welcome our new framework overlords.

@@simplytom1213 because Svelte is less type safe. More likely to be buggy

Nuxt3 is very simmilar

+masterpiece.ts+quiwik+is+most+easy

What about Solid and Qwik? Have you tried these?

You choose the right starter-pokemon

of course it won't, its javascript

@@bagr4ever Why are you hurting us with the truth?

javascript ecosystem is a hot mess, I hate it. I hate react but have to use it for the job.

Everything is up to date in the official docs...

Likely with the lunch of 1.0, we'd see more and more great tutorials for Svelte and SvelteKit

Huntabyte has the best Sveltekit tutorial 😘

already using it in a company 😅 it's extremely cool and joy to work with

how about if you compare it to next 12 or 13? I have never tried those but I would love to hear an opinion first.

I have bulit the same app with Svelte/Sveltekit, React/Next/Remix, Vue/Nuxt, Astro and I end up building everything with Sveltekit, I am migrating apps made with old versions to version1.0, Sveltekit is the smartiest, advanced framework we could ever have, in order to have such experiences you gotta try them all to conclude with such comment 😅

I came here to say this is such a long way since sapper

Cool kid on the block😂😂

For me, Angular feels easiest and most intuitive. Maybe because I'm mostly a backend developer doing .NET and Java projects.

Channel called @Huntabyte - great tutorials

exactly...

Can you get me a job? Pretty please 🥺

Ahh, I can still dream.

I’m switching from next to sveltekit lol. It’s really easy to pick up, took me a day with their interactive tutorial.

@@minnow1337 Hey Could you please share any course or tutorial that teaches full svelte , I found many of tutorials are half assed .. would really be thankful

The official svelte documentation has an interactive REPL tutorial that you can go through pretty quick. For svelte-kit I would read the get started section in their official documentation. I would also look to the vite docs since svelte-kit is built on top of it. In my experience, reading documentation is always more concise, comprehensive and up to date than relying on video tutorials. Most of the time youtube tutorials are just programmers following the get started section in official documentation anyways.

@@kevinmitnick1301 Huntabyte has the best Sveltekit tutorial 🦾

"All frameworks are good for hello world project!!" I agree with that

If you have 50 UI devs working on a project you should look into the concept of Microfrontends since 50 people can’t work together in a team.

Svelte is great, closest thing to writing vanilla js / html / css, which means you spend less time dealing with weird framework-specific stuff, yet the framework itself gives you a great safety net to fall back on. Also it sounds like js has come a long way since you last used it, if anything just use typescript and you’ll be smooth sailing

If you want to keep as close to native HTML/JS/CSS as possible, without sacrificing performance, then you go with Svelte. If you don’t care about learning curve and shenanigans as long as you get a huge community and packages and tutorials, then go with React.

@@beners Thank you very much for the feedback! I will definitely give it a try!

@@isdeonf Thanks my friend! Svelte's proposal is precisely what I'm looking for at the moment! I will take your position into consideration and give it a try!

@@heldim92 Hey, how did your project go? was svelte a good candidate?

🥇 Gold!

@@Fireship can you atleast gimme silver 🥈 ? Pwease 🥺

What is tanstack

why switch at all but if you do? Svelte

except Phoenix isn't a UI library