sdk VS language

50. Dart - $55,862

Gerrit is optimized for in-house work lead by engineers who would rather be using Subversion. ("Subversion merge isn't worth using so I don't see why we need it.") It tends to be hostile to community contribution: outsiders get a second-class experience, so if community participation is your goal it's a bad choice.

First off, Flutter uses Dart for its codebase. This means that the Dart programming language is used to develop the UIs, logic, and functionalities of applications and software built with Flutter.

The methods and other important information are documented in detail here. I have been exploring it and received some advice from Norbert 🙌.

Programming Language: Dart

Official Dart website: dart.dev Dart Language Tour: dart.dev/guides/language/language-tour Dart API Reference: api.dart.dev

Flutter is written in Dart, and its C interop story isn't strong (all functions that have to be callable from C have to be specifically annotated, and it doesn't support named parameters, which are used all over the place in Flutter). Here is my ticket for that.

I noticed that I can enable inline-class as an experiment to play with Extension Types. You need to also add sdk: ^3.3.0-0 to your pubspec.yaml.

Current syntax is not all that bad if you are going to do OO and add various helper methods on `Message` and its subclasses, but if you just want to define your data and no behavior / helpers - then it is exceedingly verbose.

[1]: https://github.com/dart-lang/language/issues/3021

Reference

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.

Coming from a Dart context here where that team is also looking at adding Macros to the language. It was really interesting to compare and contrast some of the approaches https://github.com/dart-lang/language/blob/main/working/macr...

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 know that it would be nice not to use the generator at all, but we have to wait until static metaprogramming is implemented in dart. https://github.com/dart-lang/language/issues/1482

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.