This month, I’ve been looking into meta-frameworks like Astro and SvelteKit. Check out what I’ve learned recently.
In this article:
I tried Svelte 1.0 many years ago, and found that it lacked a few things that I consider needed for a production-grade library: support for types, developer tooling, a thriving community, and a SSR framework. Svelte now has all of those. SvelteKit lets you build server-rendered Svelte apps, going toe-to-toe with the likes of Next, Remix, Nuxt, and more.
Fireship on YouTube recently posted a 4-minute overview video. With SvelteKit, I feel like the concept of file-system based routing is further cemented as the new standard practice, and takes it further with a style similar to Next 13’s app directory convention.
When building software, “discovery” and “development” can be two separate tracks of work. I’ve found that some teams tend to line up their work with research and discovery planned along with development work in a linear fashion. They don’t have to. These two things can be done in parallel.
Interesting article from 2021 from the Netflix engineering team on how they deal with flaky tests.