• 41 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


























  • SpyrosMto.NETAvalonia v11
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    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).


  • SpyrosMto.NET*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.





  • SpyrosOPtoLinuxOn the road to Plasma 6
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    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.




  • Does it effectively output a single binary?

    Yes, that’s one of the points of NativeAOT, a self-contained single binary, exactly as Go does it.

    Does it create some kind of clusterf*k and awkward packaging formats like other MS solutions such as UWP?

    No, you can create .exe files.

    Will it actually be deployable to a random fresh install of Debian 12 or Windows 10?

    Yes, NativeAOT supports Windows, Linux and MacOS, x64 and Arm64.

    What about compatibility with older systems?

    Not sure about that, I suppose it depends on the targets each .NET version support. For example, .NET 8 will drop RHEL 7 and only RHEL 8 and later.

    And to play devil’s advocate: this won’t work for all existing .NET applications. If you use reflection (which is AOT unfriendly), chances are that you will have to rework a ton of stuff in order to get to a point where NativeAOT works. There’s a middle solution though, called ReadyToRun, which has some advantages compared to running fully with the JIT compiler.