News for hackers. Stuff that matters.
Re:dotnet run app.cs by jbverschoor on Thursday May 29, 2025 @07:43AM (#44125034)
I run in a Debian arm64 container. I get 500ms consistently. It is using a cached binary, because when I add —no-build, it used the previous version. I’m not sure where it stores cached versions though.

I’ll try to compare with explicitly compiling to a binary later today.

But that’s the thing. It’s a JIT, running a VM. Swift emits native code. Big difference.

Maybe I’ll add AOT compilation for dotnet then.. Strange they didnt incorporate that though.

Re:dotnet run app.cs by Kuinox on Thursday May 29, 2025 @08:21AM (#44125295)
What command do you use ?

> But that’s the thing. It’s a JIT, running a VM. Swift emits native code. Big difference.

It's not only a JIT, you can preJIT with R2R if you need, or precompile with NativeAOT, or i think you can fully interpret with Mono.

Edit: it looks like the issue with the dotnet cli itself, which until now was not on a 'hot path'. `dotnet help` also take half a second to show up. When running a dll directly, I think it doesn't load the cli app and just run the code necessary to start the dll.

Re:dotnet run app.cs by jbverschoor on Thursday May 29, 2025 @08:39AM (#44125485)

  dotnet run