corefx

According to this https://github.com/dotnet/corefx/pull/28278 SNI support has been added in 2018.

- 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/runtime/tree/main/src/libraries or https://github.com/dotnet/corefx/releases (depending on what version you're looking for) 1. https://docs.microsoft.co

For JS, cynical take would be that Javascript is just being consistent in making every wrong choice in language design. More serious (and more correct) answer is that, being single-threaded, adding any kind of threads would be pretty adventurous. Async/await as a sugar for promises is a decent improvement over using promises directly, so it's not so bad of a choice after all. As for C#, some kind of fibers appear to have been considered but deemed too hard or not worth the trade-offs. See here: https://github.com/dotnet/runtime/issues/11084 The acceptable alternative was, apparently, forcing to programmers to litter their code with words such as async/await/task in-between the words and symbols that actually describe the purpose of their program, should they want to take advantage of non-blocking IO. All the way throughout the call-stack,

It is still a 2nd class citizen, IMO – but I think that's improving rapidly. Some examples: -IDE support from MS is markedly better on Windows (real Visual Studio) and Mac (VS for Mac). VS Code+Omnisharp is still pretty rough around the edges for C#. -Many of the older .NET class libraries were just not designed with *nix in mind. System.IO still doesn't support symlinks https://github.com/dotnet/corefx/issues/26310

I believe they did port IQueryable: https://github.com/dotnet/corefx/blob/master/src/System.Linq...

>With .NET Core 3.0, we’re at the point where we’ve ported all technologies that are required for modern workloads .net HttpClient is based on outdated cookies RFC, RFC6265(that is 8 years old) is yet to be supported [1]. And what can you do today without good http library? [1] https://github.com/dotnet/corefx/issues/29651

Shouldn't this link to https://github.com/dotnet/corefx/issues/41769 instead since it's redirecting there for discussion?

Most benchmarks show either similar or better performance overall. https://stackoverflow.com/questions/44334125/net-core-on-win... https://robertoprevato.github.io/More-about-Linux-vs-Windows... But there are reported issues with sql: https://github.com/dotnet/corefx/issues/24480

.NET Core 3 (in preview, due out Sep 23) includes support for popcount as part of the BitOperations class: https://docs.microsoft.com/en-us/dotnet/api/system.numerics..... There's a recent post describing hardware intrinsics in .NET Core: https://devblogs.microsoft.com/dotnet/hardware-intrinsics-in... There are a lot of potential use cases, but one of the early discussions was around quickly scanning for known HTTP headers. You can see that in use here: https://github.com/aspnet/AspNetCore/blob/caa910ceeba5f2b2c0... If you really need help falling asleep, here's the discussion going back to 2015: https://github.com/dotnet/corefx/issues/2209 Disclaimers: Microsoft employee, Nazgûl

I was thinking Java and .NET yes. Here’s a discussion for .NET core not adding support for security reasons (eventually overruled for backwards compatibility reasons unfortunately). https://github.com/dotnet/corefx/issues/6564#issuecomment-21... Java: https://www.bleepingcomputer.com/news/security/oracle-plans-...

Waiting it to be ported to BSD systems[1][2][3]. [1] https://github.com/dotnet/coreclr/labels/os-freebsd [2] https://github.com/dotnet/corefx/labels/os-freebsd [3] https://github.com/dotnet/corefx/labels/os-netbsd

Perhaps, but also a huge number of public OSS projects. To take an example of a large OSS Project hosted on Github: The Microsoft .NET Core framework[1]. If I want to contribute a code change - their guidelines require me to submit a pull request on github. If I want to submit an issue - their guidelines also require me to log the issue on github. This is not unusual for most OSS projects which use Github as their central collaboration point. Today that's all A-OK for Chinese devs. The scenario discussed is if the trade-war extends, and either the US or Chinese governments block access to Github for Chinese users. Now, perhaps it's easy enough for someone to set up a mirror copy of everything in China - but that's going to limit or block collaboration. Bug fixes, changes, issues - they're not going to get across as easily. I can't email

I am hopeful .NET/C# will support[1][2][3] *BSD operating systems soon. [1] https://github.com/dotnet/coreclr/labels/os-freebsd [2] https://github.com/dotnet/corefx/labels/os-freebsd [3] https://github.com/dotnet/corefx/labels/os-netbsd

Yes: https://github.com/dotnet/corefx/blob/8750960d3fafa46a9b838c...

I was a bit confused about the talk about the maximum length of floating point constant that must be parsed, but a test case cleared it up... https://github.com/dotnet/corefx/blob/master/src/Common/test... The (760-character) string should parse as the smallest positive denormal number, but if even 1 of the trailing digits of the mantissa is deleted, the number should correctly parse to the double precision floating point value 0.0 instead. However, there are many much shorter string representations of this number possible, such as '5e-324'.