I also desperately want deno to succeed cause it’s just the best way to work with typescript. I have a strong personal interest in working with deno instead of node in the future.

At my company a lot of internal stuff is built with deno. Nothing mission critical but lots of utilities and stuff. But new services are still node, which is basically fine cause all of the complex config is handled already. But all of that complexity still leaks through (whoops can’t use this package because jest can’t find it!)

> because jest

My life is much better for having switched to vitest