3 ms·
My team uses Dart for an internal application. We chose Dart because we wanted to be able to reuse the client code for both the web interface and for tools tha
by jrockway 13y ago
My team uses Dart for an internal application. We chose Dart because we wanted to be able to reuse the client code for both the web interface and for tools that call the same HTTP API as the web interface. (The server side is Python on App Engine.)
We didn't quite get this "for free" as I had originally hoped, as the libraries to make HTTP calls are different between the client and the server (complicating the API is something called "HTTP over RPC" that we use for authenticated requests to servers from workstations).
I also prefer class-based OO to prototype-based OO and wanted to be able to write thorough tests without requiring them to run in a browser, so Dart fit those requirements better than a Javascript-based framework.
After about a year of working on this project occasionally, I've found Dart code to be much easier to read and refactor than Javascript, but it also ends up being a lot more verbose. Dart lets you encode a lot more of your intent into the program text, which I generally see as a good thing when you plan to have more than one engineer work on your code.