Spyros

Some talks from yesterday have not yet been uploaded as separate videos, but they will probably be added in the playlist soon.

Not the Stephen Toub blog post I was waiting for, but I have no complaints.

(Stephen Toub writes the yearly "Performance improvements in .NET x" post, always before the GA release in November)

I have started using Avalonia, and even though I am still learning, I am very satisfied with it. There are growing pains obviously, but as you said, I have no confidence in Microsoft UI frameworks.

It's a great text editor, yes. An IDE though, it is not. It gets close with various addons, but it's still not the same experience.

MonoDevelop died for this.

(Disclaimer: I haven't used MonoDevelop to know its quality, I'm just tempted by the idea of a free cross-platform .NET IDE. Microsoft took MonoDevelop, forked it into VS for Mac, left the former stagnate, and now is killing its closed-source descendant.)

Oh boy, now I need to find a new excuse to procrastinate on the project I want to start using Avalonia.

Well, for starters, WinUI 3 is Windows only (correct me if I'm wrong), while Avalonia supports Windows, MacOS, Linux, Android, iOS and WebAssembly.

The cross-platform solution that Microsoft advocates for is MAUI, which doesn't support Linux. And it uses native controls, meaning you may encounter platform-specific bugs, while Avalonia renders the controls the same way everywhere using Skia (same approach with Flutter).

Please be civil towards other users. Language on the internet can be misrepresented resulting in hostility in an otherwise technical discussion. This goes to everyone involved, I'm just replying in this specific comment.

Related: check out this thread (at /c/dotnet) for opinions on Avalonia: https://programming.dev/post/38851

There doesn't seem to be consensus for this move, things stay as they are.

Correct me if I 'm wrong, but I think it's still the same situation since January 2020: the long-term-supported (LTS) Qt releases are available to commercial licensees only and KDE supports collections of patches for them. Which is a hassle for sure. But nothing has changed because a fork of Qt (worst case scenario) would demand massive manpower from KDE.

And the KDE Free Qt Foundation exists, so the Qt Company can't close down the framework.

The Foundation has license agreements with The Qt Company, Digia and Nokia. The agreements ensure that the Qt will continue to be available as Free Software. Should The Qt Company discontinue the development of the Qt Free Edition under the required licenses, then the Foundation has the right to release Qt under a BSD-style license or under other open source licenses. The agreements stay valid in case of a buy-out, a merger or bankruptcy.

I have no experience with it, but I noticed there is no community for Julia (both url and display name). The locked down subreddit had almost 23,000 subscribers (if you build it, they will come ;) ).