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
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
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
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.
Specifically on Twitter and Reddit, this has led to a massive jump in federated social media. That seems like an advancement to me.
The argument for having tabs adjust depending on your ide sounds better than it is in practice. Someone formatting code to look nice with width 4 will look horrendous for someone who uses width 8.
Spaces makes it uniform and captures the exact style the original dev intended
They didn't say anything about "forced simplicity". Not everything is a slippery slope
Try deleting all obj and bin folders in the repo and restart VS. Sometimes it gets stuck on an old project reference and can't clear out the cached files
The second comment explains a lot. There is a build script that generated the binary, which they are using to reduce the overall build time. They mention this resulting from a limitation on cargo and this being a workaround
It seems like you could build it all from scratch if needed with a bit of effort
Why does the way you present the data change how the memory is managed? I think you are mixing data storage with display logic.
I'd imagine one of those killer features is using a language with a solid standard library. Npm dependencies are notoriously complex because js as a language is missing basic functionality that is standard in other languages. Just a few years ago the Internet broke because "pad left" was pulled by it's maintainer, that simply doesn't happen in other languages
From a maintenance perspective npm is a nightmare. From a security perspective it is worse. Being able to build your entire website using a language that eliminates most dependencies, and the ones you take on don't pull in a zillion dependencies either, is absolutely a killer feature
Of course that isn't the full story and using js still has it's advantages as people have already pointed out. If wasm closes the gap in those areas then it would absolutely be worth the switch
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