knowgo-vehicle-simulator VS hydro-sdk

We published our vehicle simulator in the Microsoft store, using the msix package for package preparation. It took a little bit of trial and error to find the right combination for the configuration, but you can look at our pubspec.yaml if you're curious. Happy to answer any questions if you're running into problems.

KnowGo Vehicle Simulator - Connected Car simulator written in Flutter

Source

One of the more glaring limitations at the moment, besides the lack of web- and desktop-ready plugins, is the fact that isolate to web worker mapping was stripped out of dart2, so you're still forced to maintain separate isolate and web worker-based solutions for anything that needs to do background processing (e.g. most real applications that aren't just toy UI mockups). Having different dart:io and dart:html code co-exist in the same codebase is possible, but still quite ugly. The Dart<->JS interaction is also still incredibly clunky, particularly when you can't just push object serialization/deserialization to the JS side for dart:io code. You can see some of the tricks we had to come up with to work around this in our vehicle simulator: https://github.com/knowgoio/knowgo-vehicle-simulator

There is already a project trying to bring Typescript into Flutter, but its on early development: https://github.com/hydro-sdk/hydro-sdk This will also probably create many extra pains for developers since existing Dart packages would have to be wrapped.

It's probably vastly more trouble than it's worth, but you could technically write the package in Typescript and use Hydro SDK to compile it to Lua bytecode that can run on the Dart VM with Flutter bindings, then distribute that bytecode with a package that wraps the Hydro API.

As an open source author, I've been thinking about some general and domain specific optimizations https://github.com/hydro-sdk/hydro-sdk/issues/797 I'd love to chat if OP has time.

In terms of interoperability, the short answer is mostly-yes. Any Dart code can be made to interoperate with code written using Hydro. Taking an existing Dart package and making it useable from Hydro is automated. The tooling isn't quite ready for prime time (nor is the entire SDK) https://github.com/hydro-sdk/hydro-sdk/tree/master/lib/swid

Hydro-SDK has a small Dart-like language built into it to support binding generation (https://github.com/hydro-sdk/hydro-sdk/tree/master/lib/swid/frontend/swidi).

The analyzer API is enormous. I've had a lot of success using the analyzer API, but abstracting over it with my own ASTs that can be manipulated and transformed (https://github.com/hydro-sdk/hydro-sdk/tree/master/lib/swid) and using code builder (https://github.com/dart-lang/code_builder) to emit Dart code.

I've been having a lot of fun writing a compiler in Dart (in a pure functional style, with pattern matching and sum types!) over here https://github.com/hydro-sdk/hydro-sdk/tree/master/lib/swid