Celebrating Dart’s birthday with the first release of the Dart SDK(google-opensource.blogspot.com)
google-opensource.blogspot.com
Celebrating Dart’s birthday with the first release of the Dart SDK
http://google-opensource.blogspot.com/2012/10/celebrating-darts-birthday-with-first.html
20 comments
Has anyone built something that illustrates Dart's features or made a neat web app with it? Can it handle graceful degradation from running in a browser which natively supports Dart to a browser which requires JS compilation?
> Has anyone built something that illustrates Dart's features
Take a look at: http://synonym.dartlang.org/
> or made a neat web app with it?
We're getting there. People are starting to build frameworks and libraries, and there are a bunch of sample apps floating around. The language itself is still changing pretty quickly, so it's most amenable to early adopters. As things get more stable, I think we'll start to see more apps.
> Can it handle graceful degradation from running in a browser which natively supports Dart to a browser which requires JS compilation?
Yes. There's a canonical stub .js file that you add a script tag for on your page. That will detect whether or not the browser supports Dart and pull in either the native Dart code or the compiled-to-JS one as appropriate.
With this, you can write an app that any browser can hit and it will do the right thing.
Take a look at: http://synonym.dartlang.org/
> or made a neat web app with it?
We're getting there. People are starting to build frameworks and libraries, and there are a bunch of sample apps floating around. The language itself is still changing pretty quickly, so it's most amenable to early adopters. As things get more stable, I think we'll start to see more apps.
> Can it handle graceful degradation from running in a browser which natively supports Dart to a browser which requires JS compilation?
Yes. There's a canonical stub .js file that you add a script tag for on your page. That will detect whether or not the browser supports Dart and pull in either the native Dart code or the compiled-to-JS one as appropriate.
With this, you can write an app that any browser can hit and it will do the right thing.
AJAX commands are still shown as:
var xhr = new XMLHttpRequest.getTEMPNAME(
Dartisans (video) episode covering the release: https://developers.google.com/live/shows/7702017-1001/
We're using AngularJS on a large project, and although we haven't looked deeply at Dart yet, I still have a ton of questions in regard to their future compatibility, potential overlaps, roadmaps, etc. I've seen some message group posts about this, but there was nothing definitive and the core groups don't seem to collaborate at all (please correct me if I'm wrong).
You'll probably want to see Dart's Web Components[1] work. I suggest you direct any questions over to the mailing list[2].
[1] https://github.com/dart-lang/dart-web-components
[2] https://groups.google.com/a/dartlang.org/forum/#!forum/misc
[1] https://github.com/dart-lang/dart-web-components
[2] https://groups.google.com/a/dartlang.org/forum/#!forum/misc
Definitely check out Web Components. It's aiming to take many of the low-level features of the MV* frameworks, like templating and data binding, directly into the browser. Angular was created with a "what would HTML look like if we could extend it" idea, and Web Components is the "ok, let's add it to HTML now" response.
SDK looks cool to play with; tools are definitely where its at with this.
Dart (currently) doesn't seem to have any compelling use cases.
If people make tools with in build refactoring and other nice features that make productivity a compelling use case, maybe Dart has a chance to grow~
Still, given the tools that already exist for working on JS, there's still a long way to go before this will be enough to drag javascript developers over to dart...
Dart (currently) doesn't seem to have any compelling use cases.
If people make tools with in build refactoring and other nice features that make productivity a compelling use case, maybe Dart has a chance to grow~
Still, given the tools that already exist for working on JS, there's still a long way to go before this will be enough to drag javascript developers over to dart...
A more sensibly Lisp-y Javascript with a closer eye to performance. I like it!
[deleted]
Please save us from JavaScript, google.
I agree with the sentiment. However, I hesitate to embrace Dart, after Google killed off a huge number of APIs earlier this year. Go seems to have much more traction at Google so I think it is safe, but Dart still has an experimental feel to it. I'd like to hear a long-term commitment from Google to Dart before I really jump in.
From what I see, Go is not really meant for web development. I think Google's real bet on web and general app development will be Dart, as Go looks more like a C++ replacement. Also from the project page, I see like 80 people are committing to Dart so that sounds pretty promising ( https://code.google.com/p/dart/people/list ).
Go is certainly meant for the server-side of web development, but I guess the phrase web-dev is often intended to mean client-side only.
I don't get it why they make it so difficult to get the source code.
TypeScript:
They say it's so complicatd because Dart is part of Chromium, but Firefox has a direct hg link -plus- hg bundles (repository snapshot).
TypeScript:
typescript.org
click "Get the source code"
click "Download"
dartlang.org
click "Download now"
click "Check out" the source code
click PreparingYourMachine
wget http://src.chromium.org/svn/trunk/src/build/install-build-deps.sh
bash install-build-deps.sh
install 32-bit dev libraries
svn co http://src.chromium.org/svn/trunk/tools/depot_tools
export PATH=$PATH:`pwd`//depot_tools
install jdk 1.6
gclient config http://dart.googlecode.com/svn/branches/bleeding_edge/deps/all.deps
gclient sync
They say it's so complicatd because Dart is part of Chromium, but Firefox has a direct hg link -plus- hg bundles (repository snapshot).
That is to get a development environment setup to build and contribute to the project. What are you trying to do?
This will get you the source:
[1] https://github.com/dart-lang/bleeding_edge
This will get you the source:
svn checkout http://dart.googlecode.com/svn/trunk/ dart-read-only
[1] https://github.com/dart-lang/bleeding_edge
That's not how you get the source, that's how you prepare for building the whole project, including the VM, compiler, etc. If you just want the source code, just
svn checkout http://dart.googlecode.com/svn/trunk
That isn't terribly easy to find, though, it's true (you either have to have used google code before and know it's on the "checkout source" page or dig through those "get and build" instructions for just the "get" part).
The rest is just dependencies (and daunting at first, but pretty simple after you do any chromium work). You have to deal with the same thing if you check out Firefox and you want to build it (gclient here becomes bootstrap.py there).
svn checkout http://dart.googlecode.com/svn/trunk
That isn't terribly easy to find, though, it's true (you either have to have used google code before and know it's on the "checkout source" page or dig through those "get and build" instructions for just the "get" part).
The rest is just dependencies (and daunting at first, but pretty simple after you do any chromium work). You have to deal with the same thing if you check out Firefox and you want to build it (gclient here becomes bootstrap.py there).
Thanks for the help. I see now you can get the URL by using the source browser then clicking 'checkout' to get the svn checkout URL.
I just wanted to check out the source, but setting up an Ubuntu VM to isolate gclient and that other nonsense was way too much work.
I just wanted to check out the source, but setting up an Ubuntu VM to isolate gclient and that other nonsense was way too much work.
You meant typescriptlang.org ?
I guess they can make it easier. But,
- The procedure you wrote is not that hard for a developer who wants to build the whole thing.
- Dart has much much more stuff than typescript. (vm, browser, editor etc)
I guess they can make it easier. But,
- The procedure you wrote is not that hard for a developer who wants to build the whole thing.
- Dart has much much more stuff than typescript. (vm, browser, editor etc)
You can get the source code right from github:
https://github.com/dart-lang/bleeding_edge