
Here's an example where I launch vs code in one chat then switch to another chat and the window stays with the chat that launched it.

Software developer. Prev @deno_land. Working on ts-morph, dprint, and more.

Here's an example where I launch vs code in one chat then switch to another chat and the window stays with the chat that launched it.

My current setup is a sidebar where I can work on tasks within desktop tabs. I like that it surrounds and takes control of the desktop rather than living in a single window or terminal.

In all seriousness, I don't think this is a good reason to not have dependencies. There's huge value nowadays in many eyeballs and foundational libraries are only going to get more secure.

Can't have CVEs in your dependencies if you have zero dependencies.
What’s going to happen to open source? A prediction: Dependencies are over. The same Brotli vulnerability impacted .NET, Node, Bun, Envoy and more. Dependencies are too big of a target. When rewriting a dependency is one prompt away, why take the risk?

We put up a version of hunch that you can play Pictionary against in your browser (no server!). It's really good, even if your drawings are not. No Jev or OpenRouter calls here, nothing leaves your system! All powered by @GoogleGemma's EmbeddingGemma 2. tryhunch.dev/pictionary
Meet hunch! Jev-like decisions in ~20ms without even needing a GPU, learning live from a teacher model. Built on @GoogleGemma's EmbeddingGemma 2, it can works with any teacher model like @CloudFlare's Clef. Multimodal, w/a systemone endpoint, slots into your existing stack 🧵

Crunched the latest CVE/Pope numbers.
I'm tired boss

It's actually not faster when strictly looking at how long it takes to format text, but dprint traverses files really fast and the Wasm scales better on multiple threads (this chart is JS warmed up, which the Wasm doesn't need to do).

More progress compiling Prettier to Wasm then running it in dprint. 32 threads then 1 thread.
Current progress compiling Prettier to Wasm.

It's very hard to innovate on module resolution in JS because the TS user experience would be bad. TS needs something like content mappers, but for module resolution—you specify an npm package in a tsconfig and then TS sends it the raw specifier and referrer info to resolve.

Current progress compiling Prettier to Wasm.
I've been looking into getting prettier compiled as Wasm the past week with equivalent performance to v8... initially had some poor investigation into it (github.com/dprint/dprint-plu…), but I resurrected an idea I had in the past and it's looking more promising.

Nowadays this kind of stuff is trivial... super exciting, but also I feel bad for the TypeScript team because it's becoming easy for other people to come up with better solutions. You no longer need to spend millions of dollars to do this kind of work.

I had a similar idea when I became distraught after the TS team told me about their choice of Go... for several weekends I worked on a subset TypeScript to C# compiler that exposed things like Parallel.For Unfortunately, at the time, it was a ton of work so I gave up.

A huge benefit is this allows distribution of the TypeScript compiler as JavaScript so it can keep working well in JS until JS can catch up.
New from Vercel Labs: tsc-ts TypeScript was written in TypeScript Then rewritten in Go We ported it back to TypeScript Compiled it with scriptc And it's 2-4x faster than tsgo

You can use bun's formatter in dprint now with `dprint add bun` (dprint.dev - code formatter for all your code formatters) It's also available to try in the playground here: dprint.dev/playground/#code/… Of if you want to use it in JavaScript: npmjs.com/package/@dprint/bu…
👀 `bun lint` and `bun format` just landed - 600k+ lines added in one PR - 1,000+ built-in lint rules - Fast (of course) github.com/oven-sh/bun/pull/…

I've been looking into getting prettier compiled as Wasm the past week with equivalent performance to v8... initially had some poor investigation into it (github.com/dprint/dprint-plu…), but I resurrected an idea I had in the past and it's looking more promising.

Try it out in the playground here: dprint.dev/playground/#code/…