Johnson Chu

Ch.2: Running ESLint rules at 16× speed in TSSLint gist.github.com/johnsoncodehk/…

I feel like we are on one of those pendulum swings right now where people undo a decades worth of work only to realize in 5 years they over swung because they missed the actual problem. We see this all the time. I'm not going to argue against imperative handles in all cases. But I want you think about the implications. If you unwind these things you remove guarentees. Like why do developers like Rust or TS? Its because through constraints certain classifications of issues aren't possible. The solution solves itself structurally. Structural constraints also have a nice property when composed. You keep benefitting from them as you layer on complexity. Build more constrained systems. Like if you aren't batching synchronous updates you probably have no foundation to managing async race conditions structurally. We shouldn't confuse incidental simplification(removing a problem) with structural simplification. Sometimes legitimately we don't need to solve certain things. The solution should fit the problem. But more often than not in a well established space we are just delaying the inevitable.

Volar now has first-class support in tsdown and rolldown-plugin-dts. It can generate `.d.ts` files for all file types supported by Volar, including Vue and Astro. github.com/sxzz/rolldown-…

@jitl 👀

may have gotten a 20%-30% speedup on alien-signals reactivity, prompting fable from the beach @johnsoncodehk

The wait is over – @AnthropicAI’s Claude Fable 5 is back! Try it in JetBrains AI Assistant, Junie, and Air today. What are you going to build?

@theozero 🤟

wow @johnsoncodehk can read my thoughts. Wanted a rust based parser emitted from github.com/johnsoncodehk/… and there is already an open PR! If you are doing anything with parsers - this is the future! 🚀

Goodbye Claude 👋 But thank you for letting me try.

Opinions along this line show a clear disconnect between those who use React only vs. those who don’t use React at all. It’s easy to assume what makes sense for you makes sense for everyone because who cares about those who don’t use the same framework as mine? But - Vite is framework agnostic, vendor agnostic, and we can’t go down that slippery slope. What if tomorrow we are going to add another 5mb for a Rust Vue compiler, and next week another for Svelte, Solid, and Astro? One can argue React is the most popular so it deserves special treatment, but where should that line be drawn? Why NOT other frameworks? Vite is downloaded 12 millions a week, every uncached download consumes bandwidth and CI time. 5mb might not mean much for an individual end user, but it can result in meaningful difference at scale. If there is a way to optimize it, we should try that. It’s ironic that people complain about node_modules size while at the same time dismissing size optimization efforts.

Happy to announce vue-tui@0.1! What you get: - Vue