Announcing Dart 2 Stable and the Dart Web Platform
1–10 of 259 posts
Re: Announcing Dart 2 Stable and the Dart Web Platform
#2I wouldn't be interested in Dart at all if it wasn't for Flutter. I can't help but wonder if there will be Flutter bindings implemented for other languages sometime.
Re: Announcing Dart 2 Stable and the Dart Web Platform
#3> The Dart language, libraries, build system, and web development tools have changed.
https://www.dartlang.org/dart-2
> ...announcing Dart 2, a reboot of the language to embrace our vision of Dart: as a language uniquely optimized for client-side development for web and mobile.
Re: Announcing Dart 2 Stable and the Dart Web Platform
#4I wouldn't be interested in Dart at all if it wasn't for Flutter. I can't help but wonder if there will be Flutter bindings implemented for other languages sometime.
> will be Flutter bindings implemented for other languages sometime
I hope so
Re: Announcing Dart 2 Stable and the Dart Web Platform
#5I wouldn't be interested in Dart at all if it wasn't for Flutter. I can't help but wonder if there will be Flutter bindings implemented for other languages sometime.
Anybody looked at flutter for Haxe?
Re: Announcing Dart 2 Stable and the Dart Web Platform
#6I wouldn't be interested in Dart at all if it wasn't for Flutter. I can't help but wonder if there will be Flutter bindings implemented for other languages sometime.
With Dart2 going through LLVM to make ARM binary code for iOS and Android (and Fuchsia), I imagine it would be trivial to emit WebAssembly as well. Writing Dart to make WebAssembly code is far more direct than writing C# and running MSIL on top of a micro .NET runtime (which is what the Blazor project is doing).
Re: Announcing Dart 2 Stable and the Dart Web Platform
#7Now that Dart 2 is final, I'm guessing we're a couple weeks out from Flutter going 1.0 -- which will mean a ramping up of the Fuchsia rumors.
Re: Announcing Dart 2 Stable and the Dart Web Platform
#8> The other is an interesting quality-of-life change for Flutter developers, which allows creating an instance of a class without the “new” keyword. The goal of this change is to make Flutter code more readable, less clunky, and easier to type, but the principle applies to all Dart code. There have been plenty of other improvements happening under the hood, as can be seen in the official changelog.
To me it seems kind of odd to design the language towards a framework. Then again, that framework is probably the only thing increasing the number of people using Dart so it does make sense to make using the framework as clean and easy as possible.
Re: Announcing Dart 2 Stable and the Dart Web Platform
#9Anybody using only dart for their mobile apps, how has been your experience with it? Where does it triumph & fail over RN??
Re: Announcing Dart 2 Stable and the Dart Web Platform
#10> The other is an interesting quality-of-life change for Flutter developers, which allows creating an instance of a class without the “new” keyword. The goal of this change is to make Flutter code more readable, less clunky, and easier to type, but the principle applies to all Dart code. There have been plenty of other improvements happening under the hood, as can be seen in the official changelog. To me it seems kin…
Server-side Dart is still there, but not getting a lot of support from Google, as it's not their primary focus. The renewed effort going into Dart because of flutter has also allowed AngularDart[0] to gain some of the benefits (better tooling and IDE integration). AngularDart 5 will actually be a huge quality-of-life improvement as they are killing the Dartium browser fork, and instead doing incremental-compiling to javascript with dartdevc.