Flutter VS WPF

1) The open-source contributions are going well! - I was able to successfully make pull requests to flutter and to my-photohub - I am currently working on responding to the issues I worked on.

Flutter is also a good option. Dart is similar to C# so shouldn't be too much of a learning curve.

It's not really complete. You might consider learning Go if you want to get into developing microservices or other types of backend software. You might use Rust if you want to do operating systems or other types of system programming. If you want to do cross-platform application development with Flutter you'll learn Dart.

Vapor[0] based on Swift. Advantage of this is that you don't have to evaluate multiple frameworks for Swift and suffer paralysis by analysis. All the Swift community is behind one framework.

The next is Actix[1] based on Rust. There are many frameworks in Rust and most of them have not reached 1.0 And which framework will survive becomes a question.

Other not so well-known is Wt[2] based on C++. This actually is created for programmers who are not web developers. The development experience is similar to desktop app development like Qt.

If that is not acceptable then Django[3], based on Python, is the one that will be good for you.

For the front-end I would recommend Flutter[4]. As much as I dislike getting tied to a single company for whom the framework is not their bread-and-butter, I don't see any other viable options to Flutter that will cover all web, mobile and desktop out of the box.

For databases, I would recommend BedrockDB[5], if you are not averse to SQLite. Or FoundationDB[6], if you want NoSQL. But if you are not concerned about horizontal scalability or okay with self-managing database availability, then PostgreSQL[7] is a very good option.

For push notifications, PushPin[8] is a good option.

[0] https://vapor.codes

[1] https://actix.rs

[2] https://webtoolkit.eu

[3] https://www.djangoproject.com

[4] https://flutter.dev

[5] https://bedrockdb.com

[6] https://www.foundationdb.org

[7] https://postgresql.org

[8] https://pushpin.org

AngularJS (UI framework built in JavaScript): open (last commit: Apr 12 2022), unsupported Angular 2 to 12 (UI framework built in TypeScript): open, unsupported Angular 13 to 15 (UI framework built in TypeScript): open, supported until May 4 2023, Nov 11 2023 and May 18 2024 AngularDart (UI framework build in Dart): open (last commit: Oct 7 2021?, Today?), supported by community?, they say no Flutter 1: open (last commit: Mar 30 2022), unsupported Flutter 2: open (last commit: Apr 18 2022?), couldn't find if still supported, I assume unsupported Flutter 3: open (last commit: Today), supported

Look at this issue for example: https://github.com/flutter/flutter/issues/12920

Android & Windows based solution using Flutter and Dart.

Suggestion: decouple more widgets from Android/iOS design guidelines #53059

BLoC, which stands for Business Logic Component, is a pattern created by Paolo Soares and Cong Hui from Google that aims to separate the business logic from the view in a given application. One of its primary goals is to make the business logic reusable and independent from the corresponding view. Initially, this pattern was introduced within the Flutter community, but throughout this article, we will take the concepts of BLoC and implement them in a React application. To start with, BLoC has these main rules:

WPF (UI framework built on top of Direct3D): open (last commit: 2 days ago), still supported WinUI 1 (UI framework built on top of Direct3D): proprietary, supported until Jan 10 2023 WinUI 2 (UI framework built on top of Direct3D): open (last commit: 2 days ago), still supported WinUI 3 (UI framework build on top of Platform Uno): open (couldn't find v3 branch or repo), not yet released

C# is entirely cross-platform; there is nothing in the language that is Windows or VS specific. However, some .NET Framework libraries are not all cross-platform. One pain point in .NET (not Framework) is that WPF applications only run on Windows

https://github.com/dotnet/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/WindowsBase/System/Windows/Threading/DispatcherSynchronizationContext.cs may help

Also, the runtime that C# runs on, is also completely open source as well (https://github.com/dotnet/runtime); ASP.NET which is used to create web apps in C# is open as well (https://github.com/dotnet/aspnetcore). WinForms/WPF, used to make desktop apps in C# is also open source (https://github.com/dotnet/wpf, https://github.com/dotnet/winforms). All of the source code for these are on the dotnet Github page: https://github.com/dotnet and most are all MIT-licensed.

WPF is now open source (MIT licensed [1]), and its XAML control templates provide _as data_ a full declarative description of how a native Windows control is supposed to look like (in multiple Windows themes like Aero for Win7, Aero2 for Win10, Luna + Royale for WinXP, and Classic for Win95 look and feel [2]).

This includes everything like the exact colors and gradient stops and animation timing and vector shapes and accessibility behavior etc. of buttons and scrollbars and everything. Example: [3]

I wonder what one could learn / achieve trying to "port WPF to rust" / implement a XAML control template renderer in Rust. If you can "simply" parse and interpret those XAML files do you instantly get a native-like GUI that supports the exact look and feel of these different Windows themes? (on any OS!)

Somehow I think it is not realized how amazing that is!

[1] https://github.com/dotnet/wpf/blob/main/LICENSE.TXT

WPF is newer, prettier, more flexible, and open-source.

Their Roadmap disagrees.