sdk VS dart_eval

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.

...which is what xml_layout and dart_eval are there for. However, at that point I wouldn't call it "writing Flutter applications in Rust" any more (which of course is just a subjective interpretation).

I also want to note that dart_eval now has over 100 tests running in CI! If you're interested in contributing to the project, writing even more tests might be one of the easier places to start - head on over to the GitHub repo and don't be shy to ask any questions.

Check out dart_eval

I learned about this because I wrote dart_eval lol. I'm sure there is a less time-consuming way, maybe some intro to programming tutorials would teach it. But tbh I don't think it's critical to know to be a good programmer.

I've been working for a few years now on dart_eval, the pure-Dart interpreter for Dart with a focus on interop (that's also now super fast :D). While dart_eval has technically been usable in Flutter apps for a while, actually doing so was pretty painful and definitely didn't meet the ultimate goal of enabling simple, automatic code push.

Maintaining this support was of course a high priority and it's also received a full rewrite, making it both easier to use than ever and also with a significantly reduced performance cost. Of course interop performance will still be better using wrappers if you don't need to extend the class, and code push support continues to evolve with the addition of runtime overrides (see previous link).

If you want to understand how it works, I think a good place to start learning would be to learn about how programming languages work in general - like what is a 'declaration' vs 'expression' vs 'statement' and then maybe see if you can understand the contributing document?