I ported a JavaScript app to Dart
blog.sethladd.com
I ported a JavaScript app to Dart
1–10 of 83 posts
Re: I ported a JavaScript app to Dart
#2I really like Dart. I'm surprised its not getting traction faster. Its a language with few surprises, everything looks familiar and works as you'd expect without gotcha's. While it doesn't feel cutting edge like Haskell or retro on steroids like Clojure, it seems just right as a replacement for Javascript.
Re: I ported a JavaScript app to Dart
#3I really like Dart. I'm surprised its not getting traction faster. Its a language with few surprises, everything looks familiar and works as you'd expect without gotcha's. While it doesn't feel cutting edge like Haskell or retro on steroids like Clojure, it seems just right as a replacement for Javascript.
It just doesn't play well with JS, because it was designed as a JS replacement, with an own Runtime, which kinda sucks...
Re: I ported a JavaScript app to Dart
#4One of the early issues raised about Dart was that it's compiled nature would make it hard to debug and was against the open source (easy to hack) nature of JS on the web.
These days JS is more or less compiled, at least the file you get in your browser is very different that what the developer saw.
This seems to improve the case of Dart and I wouldn't be surprised if we saw more languages that compile down to JS in the near future.
We already have ES6 down to ES5 http://addyosmani.com/blog/author-in-es6-transpile-to-es5-as...
Re: I ported a JavaScript app to Dart
#5I really like Dart. I'm surprised its not getting traction faster. Its a language with few surprises, everything looks familiar and works as you'd expect without gotcha's. While it doesn't feel cutting edge like Haskell or retro on steroids like Clojure, it seems just right as a replacement for Javascript.
It just doesn't play well with JS, because it was designed as a JS replacement, with an own Runtime, which kinda sucks...
Care to be more specific? You can use JavaScript from Dart now, and we're working on improving interop support. Feedback is welcome.
Re: I ported a JavaScript app to Dart
#6I wonder how the size of the dart-generated js compares to the size of the original js.
Re: I ported a JavaScript app to Dart
#7I've been porting a larger application from JS to Dart, and I can repeat a lot of what Seth says in this article. The experience has been generally very good. While porting I also discovered a couple bugs that existed in the original code base for a very long time.
I do keep flip-flopping on whether I'm going to seriously commit to it though. I really like Dart, my code is safer, cleaner, and more maintainable. But it just doesn't feel like it has much momentum yet.
Re: I ported a JavaScript app to Dart
#8One of the early issues raised about Dart was that it's compiled nature would make it hard to debug and was against the open source (easy to hack) nature of JS on the web. These days JS is more or less compiled, at least the file you get in your browser is very different that what the developer saw. This seems to improve the case of Dart and I wouldn't be surprised if we saw more languages that compile down to JS in…
In addition to source maps, which have largely eased the pain of this issue, there's also the Dartium[0] build of Chrome, which has a proper Dart VM.
Re: I ported a JavaScript app to Dart
#9[deleted]
Re: I ported a JavaScript app to Dart
#10"Here’s what I learned"
This is a bit deceptive given that he's a Chrome Developer Advocate paid for pushing Dart. Surely he "knew" about that beforehand? I'll take his experience with a few bags of sand.