Planning my migration away from Deno CLI to other, decisions to be made: - Runtime local - Runtime remote - Edge Runtime - Package manager - Local persistence - Formatter - Linter - Test harness - Code coverage - LSP - Typescript support - Scheduled jobs - OTEL I really forgot how good I had it.

Show Post

Fair. Since Node only erases types, nothing at runtime checks them, so a tsc --noEmit step in CI stays even in the best case. Deno bundles that check, which is the one thing I'd miss.

Show Post

It's also important to recognize that the "product" (deno) has not been "discontinued"... The people who have been working on it have decided to do something else. Other people can keep working on it if they want.

Show Post

I mean, Deno Deploy is the one being discontinued. Deno itself could live upon the community that would fork it and keep it alive no?

Show Post

I'd love to see a community fork that keeps pushing it forward, and keeps focusing on innovation. Or, just maybe entirely new runtime variations.

Show Post