371–380 of 509 posts
I worked on Mono a lot back in the early 2000s (back in the SVN days before it moved to Git, even). This move makes a lot of sense. Things evolved a lot over the years. Mono's legacy goals, which are to be a portable CLR (.NET) runtime for platforms that Microsoft didn't care about, don't make much sense today. Mono made a lot of sense for running places where full .NET didn't, like in full AOT environments like on t…
Earlier quoted context omitted.
Okay, this helps a lot! So .NET Core is now out of date, and any version of .NET >= 5 is cross-platform and has no Core variant?
More or less. any version of .NET >= 5 is cross-platform and is a direct descendant of the "Core" side of the fork, and so has no "full framework, windows only" variant. It is "Core" in a lineage sense, but there's no need to make that distinction any more. The term "Core" is out of date, because the experimental "Core" fork succeeded, and became the mainstream.
Earlier quoted context omitted.
For historical context: this was before the conclusion of the antitrust case that led Microsoft to start softening its stance toward open source. https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor... . This was the same year Antitrust came out: https://en.wikipedia.org/wiki/Antitrust_(film) Any support for open source or cross-platform stuff was a bulwark against claims of monopoly abuse, but none of it wor…
> Nowadays it sounds like .NET Core + third-party GUI libraries is the way to go. For reference for those unfamiliar with the terms: .NET Core was the name given to the cross-platform fork of the .NET runtime. It was forked out of .NET 4.x and dropped support for a lot of things in the first versions. It ran on various distributions of Linux and MacOS. At the same time there were forks of other libraries/frameworks i…
The current release is .NET 8
.NET 9 is about 3 months away from the usual November release.
Earlier quoted context omitted.
I last touched LINQ in college in 2016 - isn't it basically an ORM for C#? Not super unique but I assume very relevant to use when working with C#.
EF ("entity framework") is the ORM. LINQ lets you write queries against any collection, such as a Dictionary or a List. So I write lots of "listOfFoo.Select(x => x.Name).ToArray()" style code with it, which compiles down efficiently.
Earlier quoted context omitted.
For historical context: this was before the conclusion of the antitrust case that led Microsoft to start softening its stance toward open source. https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor... . This was the same year Antitrust came out: https://en.wikipedia.org/wiki/Antitrust_(film) Any support for open source or cross-platform stuff was a bulwark against claims of monopoly abuse, but none of it wor…
I'd argue that the dominance of Linux on cloud and Azure growing business is what's causing Microsoft to have an ongoing interest in linux support. A factoid that's shared sometimes (no idea if true) is that Microsoft now employs more Linux kernel engineers than Windows kernel engineers due to Azure.
The Microsoft of the Halloween Documents[0] is a different Microsoft from the one we see today that understands open source as something good rather than as a threat, and it started with Microsoft being forced to play nice.
"The cloud" as we understand it didn't exist yet.
Also, I'm not sure how relevant Mono is in the context of Wine. .NET Core is no longer an OS component, but just a runtime that ships with software. Imo their focus should be on getting said runtime working, rather than maintaining a .NET fork.
Earlier quoted context omitted.
> It's fully-cross platform To a point. Making cross platform native desktop apps is still in the hands of 3rd party vendors such as Avalonia and Uno. MAUI was supposed to fix that oversight to a less than stellar results.
That is like saying C is not cross platform because there is not a library for making desktop apps that use native components on all those platforms.
So this "it's all for backend now" notion is surprising.
Earlier quoted context omitted.
I’m a Unix person and I know nothing about Windows Server. How has PowerShell made it less competitive?
It hasn't. Powershell is probably one of great things to come out of Windows Server. I still use it with *nix machines and it powers some sidecars at work. If you are stuck with Windows Server, it's only thing that gives you a fighting chance of being able to do anything NotClickOps (tm) Sure, it's got some unique characteristic that more traditional shell users dislike but that's just a matter of taste.
Someone wrote some automation code that handles json payloads using powershell. When we tried to migrate to azure functions which uses 7.x by default things broke because users never cared to check sensitivity of key names.
It’s also slow even for interpreted language standards.
I’ll seriously never use powershell for anything serious ever again even though I admit syntax and design feels kinda nice.
Earlier quoted context omitted.
> This is wild, apparently this stuff is in the Debian repos now? It's not. Microsoft provides its own apt repository you need to add first.
Huh, why isn't it in? Does it not meet the DFSG?
Earlier quoted context omitted.
I think Microsoft has finally realized that its animus toward projects like Wine and pre-acquisition Mono was ultimately unproductive, and a net negative for Microsoft itself. I still don't trust MS's motives in general, but I think they at least recognize that Wine/Proton helps make the Win32 and DirectX APIs a sort of de-facto cross-platform standard when it comes to things like desktop gaming, and that this is a g…
I disagree. MS was completely succesfull in their goals. They kept a ton of developers busy learing useless Xamarin, thus keeping them from developing products that can actually compete with Microsoft products. Next they killed of an open source competitor (Mono) of their product, stole the usefull bits to put it in .Net, and now they dump the leftover project (that's not competing with them anymore) back into the OS…
What kind of moustache-twirly stupidity is this? Yeah, Microsoft maintained a shitty cross-platform SDK so that developers would make worse software, because that's somehow helping any of their main product verticals. By the way, those are (broadly speaking) cloud, client software, and games.
Do you have any evidence to suggest that there was a Xamarin-based application that would have directly competed with Office? How about Fallout? Now, do you have any evidence that Microsoft tried to make Xamarin worse at doing the thing that application was trying to do?
> Next they killed of an open source competitor (Mono) of their product
Microsoft's implementation is also open source, and has been for almost a decade: https://github.com/dotnet/runtime
> that's not competing with them anymore
Sure. Mono is only useful for legacy purposes. Microsoft's own design was always the reference implementation of .NET, regardless of whether it was open-source. Mono existed for the sole purpose of being an open, cross-platform reimplementation. Now that the reference design is itself open-source and cross-platform, Mono is mostly redundant.