No one said the strategy was working!

They did the calculations but unfortunately they were not good at math.

I can't tell if this is sarcasm. I really hope it is

She's kept her stuff off the Internet and any form of digital distribution since long before streaming services existed

You can create your own emitters, there's info in the docs on how to do so. My team built a custom TypeSpec emitter to output a SDK and set of libraries

I'm the TypeSpec PM at Microsoft and I'd like to learn more about your use case and experience building a custom emitter. Are you willing to chat about it? If so, what's the best way for me to reach you?

I wonder if they have plans to introduce any default emitters as part of the package? Nothing about that in the docs that I could find. [1]

[1] https://typespec.io/docs/extending-typespec/emitters

There are a few emitters in our standard library - OpenAPI 3.0, JSON Schema 2020-12, and Protobuf. REST client and service emitters for a few languages are coming online now and should be ready in the next couple months.

Been running Docker under WSL for a few years. Don't need systemd if you're either happy to start it manually with an alias or poke it into one of your profile/logon scripts.

The experience is light-years ahead of the monstrosity that is Docker Desktop

Trust me, nothing has been ported to .NET, nothing would be gained from such a move. That's not how Microsoft works. Source: I work at Microsoft

Yeah NH gives a warped lens on how ready these runtimes & frameworks are for real work. Threads about Deno and Bun pop up almost weekly, yet in my experience they remain a long, LONG way from the stable (and admittedly stale) experience we have with Node and NPM

> Yeah NH gives a warped lens on how ready these runtimes & frameworks are for real work

I think it's more that HN is warping reality on how ready they are for real work. We are shaping what is going to happen next in tech, and how quickly, by being eager and ready to give things a try and, in a mix of above average skill and curiosity, being able to make it work at a fairly sophisticated level, despite its current shortcomings.

I don't know that they are made to.

Npm packages already do too much, with package.json being used to run scripts that have permission to do nefarious tasks to relying on C libraries.

If I were to use Deno it would be with the understanding that I'd need to find dependencies that are generic and standard... Not expect everything from npm to work by default.

If I used either I'd specifically look for dependencies that are standard enough to not matter or

Hopefully it has changed, but when I was using Deno, there wasn’t a standard for TypeScript libraries that worked in both environments (due to Deno requiring file extensions on imports and tsc requiring no file extension on imports). There was a workaround using import maps, but it’s not tenable for large libraries.

Same. I've been doing a bunch of WebGL side project stuff and yet this site claims I can't run it. There's some broken detection code I think

As a 'drop in' replacement for Node, bun has a long way to go, there's many gaps and incompatibilities.

If need to change my existing code, I might as well switch over to a much more mature runtime like Deno

Sounds a lot like VS Code devcontainers https://code.visualstudio.com/docs/remote/containers

Not exactly, VS Code devcontainers work by directly interfacing with the container environment. If you don't trust the connecting party with direct access, you can use ContainerSSH. One use case would be a shared development environment.