That page crashed MobileSafari on iPad and continues to after a reboot. Is it just me?
I honestly have no idea where the world is headed to these days...
21–30 of 70 posts
That page crashed MobileSafari on iPad and continues to after a reboot. Is it just me?
I honestly have no idea where the world is headed to these days...
No IDE support, no VM in Chrome yet, also no support for calling existing javascript libraries. These three things guarantee no quick adoption. I have no idea what Google is thinking.
Is the JavaScript that comes out of the Dart compiler/transpiler readable (like the JS CoffeScript generates) or is it mush like GWT?
CoffeeScript is pretty close. It just changes the syntax, but the type-system is the same.
The optionally static types in the Dart language seems like a good idea. You get both beautiful, simple code, like in Ruby, and the possibility to speed up execution by adding types later. On the other hand, you still don't have the great community like for instance ruby has. Charles Nutter has created a static typed ruby like language, called Mirah, which looks similar.
Full type inference also lets you write beautiful, simple code -- without even needing to add types later, you get them now. And speeding up execution is just a bonus, the main benefit is catching errors early, and refactoring safely.
the main benefit is catching errors early
Dynamic typing isn't about not specifying types. Dynamic typing is about creating types at runtime.This enables certain techniques that are very productive, and totally different from what you would do in a language like Haskell, which does have full-type inference.
I also do not think a static language would work as a client-side in-browser language, simply because of the nature of browsers and the web. Such a language needs runtime introspection and even types created at runtime like air. For in-browser stuff I also prefer eval() over static-typing any day of the week.
The web needs a standard Intermediate Language: a machine code. This is what Javascript is becoming and it isn't well designed for it.
No IDE support, no VM in Chrome yet, also no support for calling existing javascript libraries. These three things guarantee no quick adoption. I have no idea what Google is thinking.
[1] http://dartinside.com/2011/live-from-dart-launch/#liveblog-e...
While Google may need this for building large applications, this is something that the web could do without. The web needs a standard Intermediate Language: a machine code. This is what Javascript is becoming and it isn't well designed for it.
Definitely.
> This is what Javascript is becoming and it isn't well designed for it.
Maybe... but what does a bytecode layer provide?
I wonder if something useful couldn't be written in JS that provides a thin service layer. I agree it's not ideal, but it's what we've got.
Google already have a few to-javascript compilers, including one for Dart... I expect they're already all over this.
While Google may need this for building large applications, this is something that the web could do without. The web needs a standard Intermediate Language: a machine code. This is what Javascript is becoming and it isn't well designed for it.
> The web needs a standard Intermediate Language: a machine code. Definitely. > This is what Javascript is becoming and it isn't well designed for it. Maybe... but what does a bytecode layer provide? I wonder if something useful couldn't be written in JS that provides a thin service layer. I agree it's not ideal, but it's what we've got. Google already have a few to-javascript compilers, including one for Dart... I e…
If Javascript is good enough as an IL why does Dart bypass it in Chrome?
While Google may need this for building large applications, this is something that the web could do without. The web needs a standard Intermediate Language: a machine code. This is what Javascript is becoming and it isn't well designed for it.