HonkPerf.NET VS sdk

Good luck with that, I knew somebody's gonna make it lol. I also made a zero alloc Linq, but without SG (in the readme you can see comparative tables)

- Unfortunately LINQ is no match to Rust iterators which get easily vectorized. However, there are low-allocations and simd-ified implementations which might help with your goals. See https://github.com/asc-community/HonkPerf.NET

After all, DDD requires special care when describing its domain definitions in code but you really don't have to go OOP route nowadays for the core logic of your applications. Also records and record structs make it very easy to define contracts and state on the go without having to go with tons of boilerplate I keep seeing in a very much DDD-oriented project my team is responsible for.

I intentionally did not implement any API from Linq which would imply allocations - such as SkipLast (which needs to store a temporary buffer), ToArray, etc. Here's the list of all implemented methods.

[DllImport("libc")] private static extern uint geteuid(); public bool IsCurrentProcessElevated() { if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) { // https://github.com/dotnet/sdk/blob/v6.0.100/src/Cli/dotnet/Installer/Windows/WindowsUtils.cs#L38 using var identity = WindowsIdentity.GetCurrent(); var principal = new WindowsPrincipal(identity); return principal.IsInRole(WindowsBuiltInRole.Administrator); } // https://github.com/dotnet/maintenance-packages/blob/62823150914410d43a3fd9de246d882f2a21d5ef/src/Common/tests/TestUtilities/System/PlatformDetection.Unix.cs#L58 // 0 is the ID of the root user return geteuid() == 0; }

> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.

The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752

The assembly redirection hell has also been greatly reduced there.

I do the same.

I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...

You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).

With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.

[0] https://github.com/dotnet/sdk/issues/36918

Noticed an open issue just now.

You're thinking of https://github.com/dotnet/sdk/issues/22247

That's a twisted and wrong narrative

Unity like refers to a Editor driven approach

Unity became popular with its moonscript language (javascript like), they then ditched it to focus on C#, but what propelled unity to what it is today is the Editor driven approach, not c#, not DOTS

They are forced to transpile C# to C++ via IL2CPP as a result to target consoles/mobiles

C# is a disease when it comes to console/mobile support

It's a substantial dependency, quite heavy

And you are not free of unity like fuck ups, it's a microsoft language after all:

https://github.com/dotnet/sdk/issues/22247

And let's not forget when they changed the license of their debugger overnight to prevent people from using it in their products (jetbrains for example)

And them deprecating open source tooling to a proprietary/closed one for vscode (c# devkit)

Let's be careful when we recommend evil as an alternative to evil ;)

The script can be found at the end of the thread here https://github.com/dotnet/sdk/issues/8742

Another difference you might be surprised by is that the .NET tooling by default collects various data from your system and sends it to Microsoft [1]. If you want to avoid this (and still want to use .NET) you'll have to make sure that the environment variable DOTNET_CLI_TELEMETRY_OPTOUT is set in all contexts before touching anything.

[1] https://github.com/dotnet/sdk/issues/6145

SDK Pull Request

Pretty sure the final file referenced here https://github.com/dotnet/sdk/issues/8742 is the one I am thinking of.