I like Dart very much, but ther's one thing that makes me confused.
Is there any general obvious advantage over Coffeescript? Coffeescript
has «normal» class based OOP and it's  compiled JS is much more
readable and clear (+small).

The ultimate goal of Dart is to run directly on a VM, not compile into
anything.

Also Dart has features that are useful when creating IDE's for it,
also a better language in team environments.

On Oct 18, 8:53 am, 127 <mamyashev.ma...@gmail.com> wrote:

I'm just trying to find which way it is better for me as a front-end
Javascript developer )
But I don't get it because every new feature I hear about has an
analogue in Coffeescript.
IDE's dev is a very local usage and a <<better language>> is quiete
fuzzy answer (
By the way, Mozilla and Webkit are going to support Coffeescrpt
natively (it is a VM realization, I guess).

On 18 ÏËÔ, 14:15, Atro <mehdi.a...@gmail.com> wrote:

Hi,

On Oct 18, 4:53 am, 127 <mamyashev.ma...@gmail.com> wrote:

Coffeescript may be good but it's just one more way to program in
"Javascript", although it's translated. The many Javascript libraries
adopt different techniques, which doesn't help with standardizing
their components so they take advantage of one another's efforts. The
characteristics of Javascript of allowing direct execution of code
makes wrapping some of them harder, I guess.

Dart is more of a longer-term kind of project. Depending on the
commitment to it, it could become more popular than any single
Javascript library, including JQuery. Right now, Dart is a little of
Vaporware, but thanks to the early release it is more than just that.
As Dart provides things like Class from the beginning, the libraries
targeting it won't become inconsistent with one another. Dart code
isn't executable all the way which may help with wrapping third party
libraries targeting it.

Or so it goes.

Cheers,
Joao

CoffeeScript and Dart are going in different directions (neither of which is
bad, they just suit different uses and users). CoffeeScript starts with JS
and says, "Let's see if we can improve the syntax." I, like a lot of people,
find CoffeeScript generally more beautiful to read than vanilla JS, but it's
underlying semantic model is still 100% JS:

1. Everything is mutable.
2. CoffeeScript does add a declarative form for classes, but that doesn't
include fields, and it doesn't ensure that the class isn't later modified.
3. No type annotations.

Simplifying drastically, you can look at Dart as starting with JS and saying
"Let's see if we can improve the semantics." So Dart still looks a lot like
JS (or a hybrid of JS and Java), but its underlying semantics are quite
different:

1. Actual classes, no prototypes. No object literals.
2. Distinction between objects-as-instances-of-types and
objects-as-data-structures (maps).
3. Classes have a purely declarative form and cannot be changed after the
fact.
4. Optional type system and type annotations.

If you find yourself liking JS but wanting it to be more terse and
expressive, CoffeeScript is a good fit for you. If you like JS but want it
to be more structured and easier to tool, then Dart is a better fit, I
think.

That isn't to say the two are mutually exclusive. Dart's => functions are
inspired in part by CoffeeScript, for example.

- bob