I stepped away from programming 13 years ago. Then, 10 months ago, I discovered Rust. Four months later, I found Svelte. Now I’m back, and I’m in love all over again!

Sehr schön erklärt vielen dank Fabian :)

Ich habe Python Image Preview über die Erweiterungen des VS Code Explorers installiert , leider funktioniert das Einbinden von PIL nicht beim Programmieren mit Python, ich bekomme immer eine Fehlermeldung, daß er PIL nicht kennt. Woran liegt das?

Wish I could have gone to this

Love Svelte, but the new font for the documentation is a downgrade for me, it just feels slower to read and slightly more ugly, it doesn't add anything of benefit.

One of my favorite talks

Das war wirklich einfach und schnell zusammengefasst was der useEffect macht und wo man ihn wie anwendet. Super geil, ich danke dir. <3

Currently porting a svelte4 app to svelte5. My app heavily relies on stores in /lib/stores/<filename.ts> Can someone kindly point me to an example of how I would migrate these global (writable) stores to svelte5? Clearly I’m missing something and having a hard time adopting the new mental model.

Fkin rick rolled again

Sehr gut erklärt und mir persönlich in 1.25 facher Geschwindigkeit am angenehmsten.

Can't wait to start building real stuff with Qwik. Just wondering if it will give us the Angular experience in the next major update. Just like angular with angular 2 (was not good for a lot of people).

41:11 Is it similar to the thing present in swift ui? The Binding thingy

Is there anything equivalent of tanstack query? New to it in reacr world but feels like it has lot of benefit in caching and auto api calls to keep the website updated and no need to think about when to revalidate the apis.

grüße von tjorre

Well its dead for me , time to go to HTMX for most cases.

Best library of the world 💖

welche enwicklungsumgebung und wie konfigurirtt ??? so kann ich das nicht nachvollziehen ???

I hate how $state handles (or rather doesn't) object reassignment.

Evan = engineer Rich = journalist This is why it took 4 years for Svelte to arrive at Vue’s design 😂

The 18:42 and 23:34 hits the nail! Fundamentals is required and it should not be forgotten.

Miško is working magic. I wish the idea of resumability would be picked up qiwker by the JS community. Just like signals or modularity, the benefits of this model are evident.

Honestly, I am very happy every time svelte improves! I am very happy for all that rich has achieved, and I hope this continues to grow to make more devs happy. Honestly... I don't give a shit about employability. From the beginning I always want to code in something that really made me enjoy the experience... the only framework that could do that was svelte... Nothing more to say! Long Life to svelte! & happy codding! :):):) ♥♥

bei mir zeigt es keine rechenwege an, eine falsche Zeile wird auch nicht rot, oder grün.... was muss ich dafür tun?

Dachte http wäre ne Krankheit

Hallllllooooooo danke

Maybe this is just me, but I find the new font a bit harder to read when either glancing at it or reading from a distance (i.e. when it is small).

Svelte was my first JS framework. The first time I received money with programming was with Svelte too. It was a competition in my school, I created a sort of 'secret diary' where you could write your thoughts and select some parts to publish anonymously. They gave me R$ 200 (35 american dolars in 10/2024) :) Thats how I got into the industry lol

44:10 Svelte magicians throwing spells to each other

Eternally greateful for Svelte

I really cannot wait for all the Millennials to get laid off so we can stop wasting time on all this bloated JavaScript horseshit.

come here to check Rich talk about svelte but i really like this talk

vercel teamleads and cucksecutives got involved and ruined svelte

Nice talk! It still amazes me how readable and powerful the `pipe` method turned out.

I like the change in font, it's good to have some change every now and then

Without svelte 5 I was unable to build my latest application EATView 2, I was experimenting with component based design system and svelte 4 had an unintentional reactivity limit of something like 5-10 deep. where Svelte 5 had no limit. Well done Rich & Team!

Great stuff. Congratulations

Svelte and especially sveltekit is so great! Hope it continues to grow

Svelte 5 is not Vue3. It is much simpler and better than Vue3. Thanks Rich for taking this upgrade in the Svelte life path.

Sry for the off topic, at first I thought the presenter was that French Pastry Chef, Amaury Guichon, from TikTok 😅 But these changes to Svelte looks cool tho!

Great talk despite not being prepared. I’m very excited to finally use Svelte 5 in our production apps. The new docs are a nice addition too! I like the look of the serif font on the home pages, but for the docs it’s too hard to browse for me. But great updates 🎉

Solid.js 5! Now with a new logo!

@rich_harris getting married and "Never Gonna Give You Up" play as his first dance is spot on. Mad props. 24:00

Imagine building Vue3 Composition API

Isn't just better to use Vue 3? Looks like Svelte.

Svelte is awesome i just hope to see more component libraries for faster development. Not a huge problem though, and sometimes it is worth writing a little more code to reap svelte's benefits

If "Svelte is a language", then what are the semantics? You can build signals fairly easy using getters and setters, you can build reactive objects using proxies. Accessors and proxies are standard javascript features with defined semantics. When I use "myRef.value" in Vue, I understand I am registering a reactive handler. Even when I reference it in a template, I understand that the template render function is calling .value on it so the render is getting registered to that. In short I have an actual way, as a programmer, to reason about how the application is going to work. And because I have a semantics, compilers can supplement this to eliminate unneeded signal operations when the compiler can prove it won't violate the semantics. The magic that Svelte does, where sometimes things are values, sometimes they tell the compiler to reactively track them, but everything is opaque to the programmer as to what is what, and the only semantics is "whatever the Svelte compiler decides to do at the moment", is not a good place to be. Especially just to avoid a function call or just plain simple property access. We've decided to throw away all good sense and lessons from decades of programming just because someone wants to write "count += 1" instead of "count.value += 1". Suppose you are handed a value in Svelte, e.g. pull it out of a *.svelte.ts file. It's a number. Do you know if it's reactive or not? No, you don't. The type signature doesn't show it. You have to go look and see if it was created via "$state". When you copy the variable, will it retain reactivity? Destructure it? Clone it? Will it just be the value? Should you write your own getter and export that from *.svelte.ts? Who knows, Svelte doesn't even have a published semantics! This is the exact opposite of good sense, and where we've been going e.g. with TypeScript. All of this because someone hates writing ".value"? This is really deeply and fundamentally not a good idea and it's why Vue abandoned the reactivity transform even after considering it and slating it into a release, shame Rich didn't learn from Evan.

good stuff 👏

I wish qwik manage to find his space, it is amazing framework

Bruh. I feel like I’m wasting time using react rn

You should do more videos on valibot. That will help us to lobyng in companies the move to your lib