Lucky

Dotnet core (now just dotnet) was a full rebuild of the framework specifically for cross platform support so they could get more enterprise cloud hosting on azure, running everything on Linux

Modern C# is built for first class Linux support for everything except UI

Even if you don't have a special setup, having a section telling you that is still a helpful thing to quickly assess a new project.

I appreciate knowing that a project should Just Work with minimal setup so I don't have to guess or make assumptions

There are far more factors determining wrist position than the size of the keyboard

Ergonomic keyboards are not a result of "the size of the keyboard", but the shape. The size could be identical, it is the shape that matters.

Without any real studies on it mentioned so far you're relying on gut feeling and logic here. Well, you mention sitting with proper posture actually helps, which is putting your body into proper alignment. That makes sense, if your neck is arched and your back is crunched all day it will eventually cause damage to your discs and cause nerve pain.

Why doesn't the same apply to your wrists? It seems logical that keeping your wrists cockeyed all day would put strain on them, and that keeping them in alignment would reduce strain.

At the very least it seems easy to see why some people would genuinely prefer keyboards like that just for comfort. I find it hard to label as "snake oil"

Wouldn't wrist position be considered part of your overall posture?

This is for custom collections, right? And you don't even have to use it, you can keep using existing ctors for your custom collections

Worse case scenario you keep doing what we've always had to do. But for the 99% of use cases we get a much more streamlined initializer, with extensions to use our own.

I don't see how that's a bad thing

The new list initializing syntax is less boilerplate, no?

Agreed. Their business model is transparent: we give them money, they give us good products

Vscode is beginning it's enshittification cycle. They got everyone using it, now they start locking it down. Much of the fear is what Microsoft could do, not so much what they have done so far

The C# extension going proprietary is the smoke to the coming fire though, and highlights what could happen to other languages. The new extension cannot be installed on open source redistributions like vscodium. What happens now if the typescript extension gets a similar update? Or Python? Etc.

They've made it so technically anyone can spin off their own extensions marketplace, and attempt to make their own C#/typescript/Python extensions, but can they truly compete with Microsoft? That is the fracture the author is talking about. They've effectively made a walled garden out of an open source platform, they've just been playing nice to hook devs and companies in before the slow enshittification

Rider on Linux has worked great in my experience

I've never had an issue with the dotnet CLI, including the commands you're talking about. Their documentation is a bit scattered at times but for the most part they have examples on everything and walk through most scenarios.

I'm not a Microsoft employee either, just a c# dev of 10 years.

They provide a link to the section where they elaborate on "commit first vs test first", here is the relevant text

Instead of jumping straight to the commit step, Fossil applies the proposed merge to the local working directory only, requiring a separate check-in step before the change is committed to the repository. This gives you a chance to test the change first, either manually or by running your software's automatic tests. (Ideally, both!) Thus, Fossil doesn't need rebase, squashing, reset --hard, or other Git commit mutating mechanisms