Earlier quoted context omitted.
back when .NET was first launched it was advertised as the new way of making desktop applications on Windows. Visual C# made it very easy to design GUI interfaces. So this "it's all for backend now" notion is surprising.
.Net is "Microsoft Java". Like Java it was designed to do everything, but as desktop development died (and mobile development was locked down by Apple and Google, limiting it to their corporate languages), it pivoted towards networked applications.
Microsoft donates the Mono Project to the Wine team
481–490 of 509 posts
Re: Microsoft donates the Mono Project to the Wine team
#482Earlier quoted context omitted.
Debian developers can do it right because they're not affiliated with the vendor, so they can disable user-hostile features and settings that the vendor enables by default.
i don't think debian developers are actually prohibited from becoming employees of the vendor, but i think that if they get caught pushing malware, their dd status is likely to be revoked, and the process that allowed them to become dds is likely to be reviewed. any dd can generally push a change to any debian package to the archive; it's a major level of trust. that's why it's generally not realistic to try to get o…
Perhaps the Debian project would force a .NET package to come with telemetry disabled by default, but for as long as said employee can abide by the rules of Debian, I don't really see any reason it can't be done.
Re: Microsoft donates the Mono Project to the Wine team
#483Earlier quoted context omitted.
Well, let's say they wanted to use Linux, but run their windows software on it.
Why would they want to use Linux though?
Re: Microsoft donates the Mono Project to the Wine team
#484Fun fact: Second Life, the virtual world, has an in-world scripting language called LSL, and it gets compiled to bytecode that gets run on a virtual machine. Initially, it got compiled to bytecode that ran on an in-house virtual machine, but in 2008, they switched over to compiling LSL to Mono bytecode to run on the Mono virtual machine. I wonder if that's still how it works. (I haven't been involved with SL for a lo…
It does indeed still work that way! We even still support the old, in-house VM, known as LSO2: https://wiki.secondlife.com/wiki/LSO We're hard at work adding Luau ( https://luau.org ) as a supported language for both in-world scripting as well as client/viewer-side scripting. As a handy byproduct of that, LSL will also gain the ability to be compiled to Luau bytecode, allowing us to eventually (someday, at least) she…
Re: Microsoft donates the Mono Project to the Wine team
#485Earlier quoted context omitted.
When using Microsoft repositories you need to explicitly opt out on telemetry collection. I think telemetry collection alone should be a good reason for Debian to consider repackaging it. I don’t want telemetry to be collected on my GNU/Linux machine, thanks Microsoft, but you already have so much telemetry from my Windows machine, please leave my other machines alone.
I hate to defend telemetry of all things but in this particular case the criticism is unfounded and lacks context: https://dotnet.microsoft.com/en-us/platform/telemetry https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telem... In any case, Debian would use https://github.com/dotnet/source-build and dotnet/dotnet, and could easily include the argume…
Re: Microsoft donates the Mono Project to the Wine team
#486Earlier quoted context omitted.
Yes, .net is for azure cloud webapps, that's how modern software is made. Then wrap them in electron to make them native.
WebView2 would probably be the way to go, now... at least for Windows as the target. https://www.electronjs.org/blog/webview2/
When Microsoft teams behave as such, why should we keep paying attention?
For native Windows, Forms, WPF, and even MFC is way better in VS tooling than WinUI C++.
Re: Microsoft donates the Mono Project to the Wine team
#487Earlier quoted context omitted.
The shift is slow, but it has been ongoing for years, and is pretty much wrapping up now. .NET 5 was released in November, 2020 and that was the "beginning of the end" of the shift over. For what I do, it's not really "Windows development" in any meaningful way. It is business functionality with HTTP, message queues etc, developed on mostly Windows laptops, and deployed to mostly Linux instances on the cloud. Not tha…
It sounds like .NET is on the way toward becoming the Java competitor it set out to be.
I am told that the C# language has evolved faster and better than Java. Despite its origins in .NET 1.0 being basically a "Microsoft Java".
But paradoxically there is now more diversity of actively used languages that target the JVM. e.g. Kotlin, Scala, Clojure.
Re: Microsoft donates the Mono Project to the Wine team
#488Earlier quoted context omitted.
No it's way better than Flutter. Avalonia really works on desktop.. :). Also the model is WPF so whoever know a little bit of legacy .NET framework will be able to write Avalonia apps in no-time
I don't know any .net, and have never heard of this until now. Only stories with comments on HN are from eight years ago. Although I liked the screenshots on the linked site, it doesn't seem to have much buzz around it. And unfortunately, the only stench I can't stand more than Google's is Microsoft's.
Following buzz I started to do a prototype with Flutter and stopped after a few days as I found out that most of the open source controls I was using had bugs on Windows Desktop. Then I moved to MAUI and discovered that in order to have some decent Rich Text support my only option was Blazor Hybdrid. Nedless to say I found bugs that prevented my prototype to work correctly. Then I moved to UNO and found that it doesn't have full Rich text format support. I was able to find some .NET open source libraries for doing text layout on Skia and with that I was able to find a partial solution that was however pretty complicated. Out of curiosity I investigated Avalonia and found that everything that I needed had full support. Being fluent in WFP I built the prototype in 3 days and I never looked back.
Your experience might vary depending on your fluency of WFP but I found that, considering Windows Desktop as a target platform, Flutter and MAUI are absolutely the worst options. In my opinion Uno is better than Avalonia when considering web application support but Avalonia has more coverage of the WPF api with respect to what Uno does for WinUi. And for sure marketing is the worst part of Avalonia while it is the BEST for MAUI and Flutter.
Re: Microsoft donates the Mono Project to the Wine team
#489Earlier quoted context omitted.
Is there somewhere where someone new to the ecosystem can get a simple introduction to all of these different terms and which ones are still relevant today? I looked into .NET somewhat recently and came away with the apparently mistaken impression that Mono was how .NET did cross-platform. I guess I must have been reading old docs, but I'm pretty sure they were at least semi-official. Is there good documentation some…
For modern .NET, you don't need to know anything about the legacy terms of Mono, .NET Core, .NET Framework, .NET Standard, etc. All you need is .NET 8 SDK. It's fully-cross platform and installs support for both C# and F#. For example, just download .NET 8 SDK on whatever platform, which is usually very easy on most platforms, and then run `dotnet fsi` to get into an F# REPL.
Do not under any circumstance trust Microsoft for anything at all.
They have a decades-long history of treating their best customers with contempt.
They will break or deprecate whatever you rely on, and they will do it without warning.
Re: Microsoft donates the Mono Project to the Wine team
#490Earlier quoted context omitted.
.Net is "Microsoft Java". Like Java it was designed to do everything, but as desktop development died (and mobile development was locked down by Apple and Google, limiting it to their corporate languages), it pivoted towards networked applications.
Visual J++ was Microsoft’s Java