CoreFX VS source-build

https://github.com/dotnet/corefx/pull/28278

System.Buffers v4.0.3.0 / v4.6.28619.01 @BuiltBy: dlab14-DDVSOWINAGE069 @Branch: release/2.1 @SrcCode: https://github.com/dotnet/corefx/tree/7601f4f6225089ffb291dc7d58293c7bbf5c5d4f / v4.6.28619.01

You’re right. Thanks for correcting me. The logic of applying the predicate for the two are inversions of each other, and they are even implemented in the same file: AnyAll.cs.

- EF Core is not MSSQL first. EF Core is an abstraction layer and is in no way tied to Sql Server. In fact, Microsoft's own getting started tutorial uses Sqlite (1). I've personally used the Postgres drivers in production and they are as good/production-ready as Microsoft's SQL library for EF Core.

- "Many libraries ship with two implementations..." I've yet to come across these "many" libraries in the 5 years since I've been building services with .NET Core.

"The community is really culty" - I'm not sure where this is coming from. It's hard to refute such vague criticisms.

- "It's practically open source in name only" - Here is the base class library source: https://github.com/dotnet/corefx/releases

1. https://docs.microsoft.com/en-us/ef/core/get-started/overvie...

Dotnet foundation publishes their C# coding style along with an editorconfig and some tooling to support it.

I created the bug report on GitHub. After that, the .NET development team fixed some code fragments described in the article. Among them - the errors with interpolated strings. The corresponding pull request.

.NET applications are technically challenging for Linux distributions to package. https://github.com/dotnet/source-build/discussions/2960

Git Credential Manager indeed release a self-contained binary for Linux x86_64 (no arm64 yet), though the installation size is necessarily large (80 MB) to include the .NET runtime. git-credential-oauth Linux binaries (x86_64 and arm64) are much smaller at 5 MB. https://github.com/hickford/git-credential-oauth#comparison-...

It's recommended to build from source for Debian, at least. Here's the latest stable release of the SDK announcement: https://github.com/dotnet/source-build/discussions/3369

Unfortunately, packaging applications built on .NET is still a challenge for any OS that wants to build everything from source and doesn't allow network access. Like you say, duplicating nuget into os-app-package-manager is challenging. Even side from the duplication, we need to bootstrap the ecosystem, in particular dealing with cyclic dependencies and version explosion as a result of all the different versions of all the dependencies that an average dotnet application needs.

We are starting to work through it here: https://github.com/dotnet/source-build/discussions/2960. Any advice/tips/contributions would be welcome, I think.

If you want to build .NET Core yourself, Microsoft provides you with the steps necessary to do so here: https://github.com/dotnet/source-build

Maybe our definitions of open source are different, or maybe you're just shitting on Microsoft for your own reasons. Regardless of whatever your experiences have been with .NET in the past, they don't mirror the majority of the folks that use it everyday.

The C# compiler and parts of the supporting .NET runtime are written in C#, so yes there is a boot strapping issue. Other languages like Rust or even C compilers written in C have this problem.

For initial porting to a new system or processor architecture, the C++ part of CoreCLR (the main runtime for .NET) can be built with CMake and LLVM on the target system. The libraries can be cross-compiled on another system that already supports .NET and copied to the target system. Some Details are here:

https://github.com/dotnet/runtime/blob/main/docs/design/core...

For building from source to satisfy requirements Linux distributions, Microsoft has a system to build from source. My understanding from the last time I closely looked at it is some binary dependencies are de compiled to MSIL (the bytecode used by .NET). Since CoreCLR includes a MSIL assembler written in C++ (ilasm), it can bootstrap using these MSIL sources. But I have not looked at this project closely in a while and it evolved quite a lot while I was watching it. The system for the source build is here:

https://github.com/dotnet/source-build

Note that there's a bug with the version of dotnet from Fedora's repositories (basically any version built from source by distro maintainers) that breaks Omnisharp for a lot of projects. See https://github.com/dotnet/source-build/issues/2006

It's coming. Progress is being tracked here: https://github.com/dotnet/source-build/issues/1139