Today i released a big update to spark.
Lots of improvements in the framework.
see yourself : https://pub.dev/packages/spark_framework/changelog
and even more in the cli : https://pub.dev/packages/spark_cli/changelog
Today i released a big update to spark.
Lots of improvements in the framework.
see yourself : https://pub.dev/packages/spark_framework/changelog
and even more in the cli : https://pub.dev/packages/spark_cli/changelog
FOUND THE PROBLEM
My assumption was that the following code would generate a run-time exception if the types mismatch (as #Dart is supposed to have a sound type system):
final int value = mapping['member'];
This /does/ happen in regular #Flutter:
type 'String' is not a subtype of type 'int`
But, in #FlutterWeb / #DartWeb if mapping['member'] happens to be a String, then `value` is still seen as an integer, but it has as internal value a string literal, and not a numeric one.
A big part of the Dart Snake project was so that I could evaluate the experiences of using Dart for server side development. A year ago I looked at the REST server landscape with this post and how Dart compared to Go in that respect . The Dart Snake project instead let me look at how well Dart worked for the front end by doing three different implementations for the web: Flutter Web, Jaspr, and plain old Dart Web Standard Libraries. In this post I compare these technologies with respect to the development experience and performance. If you’d like to play any of these versions to compare directly you can find the links below: Dart Web Snake Jaspr Web Snake Flutter Web Snake