language VS Flutter

A future version of Dart will probably support macros which should make this all a bit easier to use, similar to how Swift 5.9 works which makes already fantastic use of its new macro capabilities by integrating mobx (or solidjs) like reactivity into SwiftUI by a harmlessly looking @Obervable annotation.

Yes, that needs a bit of boilerplate for the constructor declaration and the extra build method, but I personally don't mind and with implicit constructors this will become much easier. Also, you get a performant UI as Flutter knows to not redraw widgets that didn't change.

I implemented a prototype version of the algorithm in that paper when exploring exhaustiveness checking for pattern matching in Dart.

I found it pretty easy to understand, but also really easy to get it to generate huge combinatorially large spaces. Some careful memoization and deduplication helped, but even so I never got the performance to a state I considered acceptable.

Instead, I went with Luc Maranget's classic approach and figured out a way to adapt it to a language with subtyping (with a ton of work from Johnni Winther to figure out all of the hard complex cases around generics):

https://github.com/dart-lang/language/blob/main/accepted/fut...

The performance (in the prototype!) was dramatically better. You can always make pattern matching go combinatorial, but I haven't seen any real-world switches get particularly slow with our approach yet, and we have some fairly large tests of matching on tuples of enums.

We are working on a proposal to add macros to the language for sophisticated compile-time metaprogramming. But the goal is more for larger-scale uses of metaprogramming—synthesizing entire new declarations—and not really about extending the syntax.

Looked at, never gonna happen (says https://github.com/dart-lang/language/issues/69). The language would have to have been designed for that from the beginning, and now there are too many constructs that would require too much "guessing" to get proper syntax right.

However, I'm super stoked to see the community pushing forward. I think when/if metaprogramming becomes available (https://github.com/dart-lang/language/issues/1482), similar magical experience would be possible in Dart everywhere. Consider following that issue and providing feedback. IIRC the champion of that feature (https://github.com/jakemac53) would like to make DI frameworks one of the key use-cases for the language feature, and will appreciate your thoughts on what primitives you'd need.

Dart is openly developed. If you want to know what Dart 4.0 will bring browse the Github (https://github.com/dart-lang/language).

Macros: https://github.com/dart-lang/language/issues/1482

Not sharing memory between threads was a deliberate choice and I think it saves us from a lot of bugs. Especially race conditions in multi threaded code can be a pain to debug. But more you read a long discussion here: https://github.com/dart-lang/language/issues/333

Specifically, see column 3 "being implemented" at https://github.com/dart-lang/language/projects/1 which links to specifications of in-progress new Dart features.

Flutter - Build apps for any screen

By utlizing powerful cross-platform app development frameworks such as Flutter, you are able to build your app once and deploy it across both iOS and Android. Integrating In-app purchasing across app stores can be challenging when having to manage multiple SDKs.

Yes! That's something that belongs in the core framework and frankly, "currently being worked on" is not enough for something that is wanted for 4 years now. At least I lost my patience.

I could go into more detail about our setup but it was this issue: https://github.com/flutter/flutter/issues/123120

That sounds awfully close to this issue we are already tracking. It is on the dashboard I linked earlier. We discussed this in our weekly sync today and have a couple of leads. IIRC, we think that can happen when blits fail in certain situations (like when coming back from the background).

Other way around. Dart is a generic programming language. Flutter is the UI framework built with Dart.

https://dart.dev/

https://flutter.dev/

I reported this issue before (see the comment with screenshot), but they still taking no action about this.https://github.com/flutter/flutter/issues/63507

I check the Wonderous app to learn some best practices, the app is recommended by flutter.dev.