You might be insterested in quire.io [1] team's article [2] about using dart to build a large application
[1] http://quire.io [2] http://simonpai.github.io/2014/09/03/quire-building-with-dar...
What do you guys think about Dartlang?
21–24 of 24 posts
Re: What do you guys think about Dartlang?
#22We're not using Dart commercially currently; though we are prototyping in it as a candidate for vNext of some very large applications. To me, it seems incredibly promising. Every time I have to go back and write JS in our production apps; I seriously miss the static analysis Dart does; it's so clunky to find trivial errors at runtime in a browser that the editor should've been able to show you! However; there are som…
> No private pub server. If you want to host Dart packages internal to your company locally; you're out of luck.
You can store packages on a private git server, see the pubspec.yaml docs here:
https://www.dartlang.org/tools/pub/dependencies.html#git-pac...
It is also possible to run your own private pub server. But currently the only available implementation relies on AppEngine. According to the author it's possible to just implement the fetch protocol using static files served over HTTP. I.e. create some directories and put the json and tar.gz files in the correct places.
https://www.dartlang.org/tools/pub/dependencies.html#hosted-...
Re: What do you guys think about Dartlang?
#23Earlier quoted context omitted.
Would you like to see it replace JS? I think many would argue something should before we train an entire generation in the idiosyncrasies of JS.
I would love to see this happen; but I'm just not convinced it will. I just don't see MS/FF ever choosing to build/maintain a Dart VM for their browsers (even though I think it would be a massive step forward for web dev). (Google should've spec'd a generic VM together with MS+Mozilla and built Dart on top of it; but that ship has sailed!)
I don't think anyone's banking on Dart unseating JS, and it doesn't need to. It compiles to JS to work across modern web browsers while smoothing a fair deal for you in the way of optimizations and cross-browser issues. But that's saying nothing of the real reason folks choose Dart, or JS or any transcompiler or framework for that matter: the ways in which it may benefit you and your projects, relative to your other choices.
In Dart's case relative to JS, I think the language is more sane, debugging easier, the core libraries really powerful, the tooling more uniform, and the ecosystem more organized. I like the idea of one language on client and server, and yet the way it's done in JS-land with Node feels wilder and less approachable than I liked when I researched it some years back. That's just me, and admittedly I don't have all that much experience in the world of JS before I dove into Dart.
There are some tradeoffs of course, the biggest being that you sort of block yourself off from a world of JS libraries and even community to some extent. There's dart:js interop to wrap any JS library, and work being done to make that even easier with js:interop, but I think there'll always be some disconnect. Still, it's about costs versus benefits, and there are many benefits that I think ultimately outweigh the costs.
The point is there are a whole host of reasons to choose Dart, and I think it's foolish for any one of those reasons to be because you think it'll unseat JS. It won't, but there might be merit to it unseating JS in your own workflow.
Re: What do you guys think about Dartlang?
#24One thing that bothers me about Dart is that the Angular.js team decided to go with their own language AtScript, even though they were quite experienced with Dart in AngularDart. Do they know something about the health of Dart that we don't?
They're planning to use AtScript to transpile to ES6 and Dart by extending the ES6 transpiler called Traceur (source: https://docs.google.com/a/google.com/document/d/11YUzC-1d0V1... ). The basic issue for Angular is they'd like to support users of ES5, ES6, and Dart with the same code base. That's currently a bit hard to do with a Dart code base (although a lot of us want to see that get better!) disclaimer: I've wor…
John! And with the Dart team no longer? Where are you now?