Explore >> Select a destination
|
You are here 
|
codepeer.com | ||
| | | | |
khromov.se
|
|
| | | | | Watch a video version of this blog post below! Svelte 5 brings a lot of changes, from the new Runes-based syntax to deep reactivity and performance improvements across the board. But one aspect that's flown under the radar is the massive reduction in bundle size. In my experiments, you can get about 50% decrease in code shipped to users, just by upgrading to Svelte 5 in your existing Svelte 4 applications! The New Compiler Architecture Svelte 5 introduces a small signals runtime (about 3-4 KB) alongside the compiler. While this adds a bit of code, it allows individual components to [...] | |
| | | | |
geoffrich.net
|
|
| | | | | ||
| | | | |
svelte.dev
|
|
| | | | | Taking the next-plus-one step | |
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
