Production ready means: people use it in production first -> no critical issue on GitHub -> yeah it’s production ready 😎
15.10.2025 13:29
👍 3
🔁 0
💬 0
📌 0
Production ready means: people use it in production first -> no critical issue on GitHub -> yeah it’s production ready 😎
I’ll also do my first half marathon in two months 🏃♂️
Congrats! Next: Svelte ambassador
Pure HTML! I send my blog post to Claude code and ask it to generate. You can check it in my repo.
It’s great to share our migration story at COSCUP!
I believe it can inspire and support the growth of the Svelte community in Asia!
Also, I met a new Svelte friend @henrylie.bsky.social!
I’ll be giving my first-ever public tech talk at COSCUP 2025—all about Svelte 5!
I hope more people give Svelte a try, make their lives easier, touch grass, and meet new friends.
Start your journey with a smooth, incremental migration 🪄
Star this. Now!
I can finally archive my repo and tell everyone to check sveltest
github.com/wd-David/sve...
My previous struggle: turn on my PS5, start playing dragon’s dogma 2 for 5 min to recall how to play, and then turn off my PS5 because I was too tired.
This happened three times a week lol. I spend one year to finish the first round.
Would love to work on the Svelte integration!
With AI, I think it will be easier to perform various related job functions. Let’s see how it goes!
I firmly believe that “better DX leads to better UX”.
A few years ago, Svelte enabled me to explore different aspects of a product.
That's why I always see myself as a product engineer.
The coolest part, we all agree that I’ll keep coding especially the Svelte part!
During a leadership meeting, our PM (was a senior tech lead) and I, the engineering lead, decided to switch roles. (The background story is too long, so I'll skip it.)
It's often not the case for startups. Even a CTO may not know when a pivot is necessary, and it’s challenging for a team to change the tech stack every time they pivot.
"Easier to recruit" depends on the recruiting process.
From a hiring manager's perspective, an exceptional engineer can quickly learn Svelte.
Imagine a seasoned React developer joining a new team. They need to learn patterns and libraries. The learning curve may be steeper than learning Svelte.
100% agree.
Some factors are complex to elaborate on in the article.
In React, the data model layer(which contains many classes) and render engine are separated.
I can’t tell how excited I was when I learned we can use runes in class.
Sometimes, comparing the technical differences between X & Y is not enough to make migration happen, so I also wrote about human factors and challenges we faced, and how to communicate with stakeholders as a Svelte evangelist.
(I am really bad at crafting engaging tweets.)
After many great conversations during the Svelte Summit, I realize we need to share more migration stories like ours and the one from "hackerman" @bertbengtson.bsky.social to help the community grow.
The guest blog post is finally out!
Huge thanks to Chris and Budi for accepting my proposal.
Hope you have a good read.
sveltejobs.com/blog/increme...
To have a more consistent result, we used cursor rules/ windsurf rules to force the AI to pick up.
The first and second options sometimes do not work well. The third option works way better.
It’s time to create new recipes for the new @sveltesociety.dev website!
Amsterdam Airport is clean and beautiful, but serves the worst flat white I have ever had. 🤦
When I found out that you would be talking about TanStack at the Svelte Summit.
🧡
Later 😏
I was thinking about writing a blog post about the summit, but this one is so good so I probably won’t post mine.
Svelte Asia is happening! @theosteiner.de and Tee Ming
Vibe chilling in Barcelona.