I've been using Svelte in production for over two and a half years. It's tough to go back to a fully-run-time framework after using Svelte. So obviously the t

I've been using Svelte in production for over two and a half years. It's tough to go back to a fully-run-time framework after using Svelte. So obviously the tiny amount of run-time code leads to better performance, but what surprised me was how much better the run-time debugging story is. If my code causes an error to be thrown inside the "framework" code, the stack is always very shallow, and it's easy to follow to figure out what's going on. Compared to my experience with e.g. trying to trace through AngularJS's digest cycle, following what's going on "under the hood" at run-time is pretty delightful.