3 ms·

IMHO, this is not a "break away" approach as originally indicated in the leaked memo. One of the biggest pain point in web dev is the inconsistent DOM implemen

by chintan 15y ago

IMHO, this is not a "break away" approach as originally indicated in the leaked memo. One of the biggest pain point in web dev is the inconsistent DOM implementations. I was imagining some sort of DOM-less, HTML5 Canvas-based UI controls. And something about the "Web", Semantic Web/URIs or a new approach to programming on Web. This is NOT a break away language in any sense - its more re-packaging.

deleted 15y ago
[deleted]
MatthewPhillips 15y ago
Canvas is stateless. The entire canvas has to be redrawn after every refresh. It will never make a good UI.
cletus 15y ago
I'll stress that it's early days for Dart. Go was announced in 2007 and only this year is going to a version 1.0. I don't know what the timeline is for Dart but I will say this: 1. If anyone is capable of the long sort of time frame that something like this can benefit from--event requires--it's Google; 2. If there is anyone who's qualified as a domain expert in Javascript generation it is, by virtue of GWT, Google; and 3. If there is anyone who's qualified to speak to the limits of what you can do with Javascript it is, by virtue of Chrome and V8, Google. If anything, I believe the error here (if you can call it that) is failing to properly set expectations and communicate the goals of the language (as witnessed by all the comments on this thread from people who were expecting something more and/or different).
- edsrzf 15y ago
  Small correction: Go was announced in November 2009.
  - dasil003 15y ago
    Thank god. I was starting to think I'm getting old if 4 years goes by that quick.
Lewisham 15y ago
The original leaked memo that everyone was freaking out about was incredibly overblown as it was entirely decontextualized. The engineer that wrote the memo needed people for his team. To get people to join a team from any of the others at Google, you need to convince them that your team is awesome to work with. At Google, you can't offer more money/benefits, so it has to be a "join us and you'll change the world!" message. That's going to lead to a lot of overblown statements that may or may not end up being true, and may or may not even be believed by the author. Google is not in the business of doing things that are bad for the web (and when they have done, there's been an about-face, see: Google Video shutdown), even if internal machinations might make it seem that way.
munificent 15y ago
We are definitely trying to improve the DOM API with Dart, but, for performance reasons, ditching the DOM and starting over from scratch in Canvas doesn't really fly, at least not in the short term.

by chintan 15y ago

deleted 15y ago

[deleted]

MatthewPhillips 15y ago

Canvas is stateless. The entire canvas has to be redrawn after every refresh. It will never make a good UI.

cletus 15y ago

I'll stress that it's early days for Dart. Go was announced in 2007 and only this year is going to a version 1.0. I don't know what the timeline is for Dart but I will say this: 1. If anyone is capable of the long sort of time frame that something like this can benefit from--event requires--it's Google; 2. If there is anyone who's qualified as a domain expert in Javascript generation it is, by virtue of GWT, Google; and 3. If there is anyone who's qualified to speak to the limits of what you can do with Javascript it is, by virtue of Chrome and V8, Google. If anything, I believe the error here (if you can call it that) is failing to properly set expectations and communicate the goals of the language (as witnessed by all the comments on this thread from people who were expecting something more and/or different).

edsrzf 15y ago
Small correction: Go was announced in November 2009.
- dasil003 15y ago
  Thank god. I was starting to think I'm getting old if 4 years goes by that quick.

Lewisham 15y ago

The original leaked memo that everyone was freaking out about was incredibly overblown as it was entirely decontextualized. The engineer that wrote the memo needed people for his team. To get people to join a team from any of the others at Google, you need to convince them that your team is awesome to work with. At Google, you can't offer more money/benefits, so it has to be a "join us and you'll change the world!" message. That's going to lead to a lot of overblown statements that may or may not end up being true, and may or may not even be believed by the author. Google is not in the business of doing things that are bad for the web (and when they have done, there's been an about-face, see: Google Video shutdown), even if internal machinations might make it seem that way.

munificent 15y ago

We are definitely trying to improve the DOM API with Dart, but, for performance reasons, ditching the DOM and starting over from scratch in Canvas doesn't really fly, at least not in the short term.