141–150 of 351 posts
Earlier quoted context omitted.
Someone with strong negative opinions about Microsoft, but none about the FAANG companies, is usually struck in the past, maybe 20 years ago.
FWIW, I'd approach other FAANG with the same "get ready to be betrayed" attitude I have to MS as well. Try to entrust as little as possible into their hands, but still do what's necessary to your business (i.e. don't be fanatical about it).
Earlier quoted context omitted.
Millions of businesses run on Microsoft platforms and software developed on/for Microsoft platforms for decades. I think you are painting darker picture than it really is. Or please elaborate a little what you mean by "betraying".
You're right. They run on Microsoft platforms. For decades. Not Linux.
That hasn't been true for the last few years.
Had to fix a bug in a hobby app that uses .NET Core for its backend last evening. I miss working in this ecosystem daily (back to node and rails for work), it's such a pleasure. The best developer experience I've ever had. If anyone is hiring and you use .NET... :)
I don’t know where in the world you’re located, but there are way more .Net jobs available than than Node or Rails here in Denmark.
Earlier quoted context omitted.
The debugger is part of Visual Studio, which is a paid product. I don’t think it’s unreasonable to not publish the source for it.
Yeah, but the general standard is for open languages to either have an open debugger (e.g.: V8 JS) or else otherwise have support for an open debugger interface (e.g.: Rust via GDB). It's not strictly unreasonable for MS to offer a proprietary debugger, but it is bass-ackwards for the core .NET team to not offer an open source debugger or open standards compliant debugger interface to go with their open source langua…
But it should be possible to write independent .NET debuggers -- I believe Jetbrains has done so, Rider can debug C# code without the problematic Microsoft component.
I wonder if this opens the door for .NET applications to be included in Ubuntu? Neither this blog post nor Ubuntu’s [1] mention that as a possibility. Just thinking from a Ubuntu package level, where libraries live in packages separate from executables, it might be possible to create library packages using the result of ‘dotnet store’. Then executable packages could reference them when running ‘dotnet publish’. [2] T…
Earlier quoted context omitted.
Millions of businesses run on Microsoft platforms and software developed on/for Microsoft platforms for decades. I think you are painting darker picture than it really is. Or please elaborate a little what you mean by "betraying".
I believe, sooner or later, MS will put some arbitrary restrictions on .net or some part of its toolchain, forcing users to purchase a license to make it usable. It will probably involve "cloud" to sign/notarize your binaries to distribute them and give MS complete control of the ecosystem. Obviously, I have no idea what exactly will MS do, but after reaching some adoption target, MS will try to extract as much money…
- .NET Hot Reload is only implemented on Windows. It requires support in the .NET runtime, which is technically possible to implement, but the team has not gotten around to implementing it for years. This doesn't have to do with the issue around MS removing the "dotnet watch" command, it's for the "Edit and Continue" feature in IDEs.[1][2]
- MS was considering deprecating Omnisharp, the open-source language server that implements C# support for VS Code, and replacing it with a closed-source version. Since the announcement, commits to omnisharp-vscode have dropped off significantly. The lack of Omnisharp would mean there would be no real open-source C# development environment for Linux anymore, since MonoDevelop was abandoned a few years ago.[3]
[1] https://youtrack.jetbrains.com/issue/RIDER-31366/EditContinu...
[2] https://github.com/dotnet/coreclr/issues/23685
[3] https://github.com/omnisharp/omnisharp-vscode/issues/5276
The .NET ecosystem is giving me a lot of confidence these days. I've been on this rollercoaster since .NET Core 2.x and don't think I will be getting off any time soon. We recently upgraded from 3.1 to 6, which was a total non-event. The code base that was around for Core 2.x is still the same one we have today. Some substantial changes made to the web interfaces and hosting, but nothing in the business logic or data…
What kind of applications you build primarily with.net6?
For fun, a game engine complete with a pure software rasterization pipeline.
Earlier quoted context omitted.
> Old .net has become ".net framework". From my understanding, thats not quite right. AFAIK framework was adapted to differentiate it from standard, core and mono.
It's really too bad the naming/versioning has gotten so confused. I used to be a heavy .Net user, then stepped away for a while when I changed jobs. Every time I try and come back, I get so confused. Am I looking at the right docs? Is this API available for the platform I'm on? It's bad enough with .Net, itself, but what about GUI libs? What's even supported anymore? What's actually stable and not in pre-release? It'…
Earlier quoted context omitted.
> Old .net has become ".net framework". From my understanding, thats not quite right. AFAIK framework was adapted to differentiate it from standard, core and mono.
It's really too bad the naming/versioning has gotten so confused. I used to be a heavy .Net user, then stepped away for a while when I changed jobs. Every time I try and come back, I get so confused. Am I looking at the right docs? Is this API available for the platform I'm on? It's bad enough with .Net, itself, but what about GUI libs? What's even supported anymore? What's actually stable and not in pre-release? It'…
Anybody knows if this affects the ease of installing on Debian 11 in any way?