41–47 of 47 posts
Please give us a proper VM like .NET(Mono is a good candidate), Java, Parrot or whatever instead of yet another crap language(both Dart and JS are shit). Provide a VM level binding layer to the DOM, and everyone will be happy. Really, I didn't expect that a company like Google will be so stupid to do so.
So. Adding stuff like the canvas tag (added to webkit to display dashboard widgets) and CSS transforms (ditto) is ok because they were going to submit them as standards anyways. But adding another language besides JS is not ok because that would be bad for the web. Now, personally I don't care about dart, but I know that I had the same bad feeling back in the day when Safari learned the then nonstandard canvas tag th…
By contrast, Dart is squarely aimed at competing with a feature that's both a defacto and a formalized standard for web browsers. Not an abandoned and aging feature, either: JavaScript's proven far more capable than most of the industry gave it credit for, it's been growing and changing over time, and there's currently very active development, discussion, and collaboration underway to improve the language and its performance -- and expand the features exposed to it by various APIs.
There's a world of difference between those two situations. In the former, you're introducing a new feature a platform doesn't have yet. In the later, you're splitting the industry on an existing feature.
Please give us a proper VM like .NET(Mono is a good candidate), Java, Parrot or whatever instead of yet another crap language(both Dart and JS are shit). Provide a VM level binding layer to the DOM, and everyone will be happy. Really, I didn't expect that a company like Google will be so stupid to do so.
ref: http://www.mozilla.org/grants/perl-foundation.html & http://www.parrotblog.org/2008/09/final-report-for-mozilla-f...
Earlier quoted context omitted.
You've forgotten your history. http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish And don't think it's not possible, a number of MSFT folks who employed this strategy are now in leadership roles at GOOG.
[citation needed]
Earlier quoted context omitted.
Just like canvas tag, right?
I remember canvas in 2004, I demo'ed it in a Firefox prototype at Web 2.0 that fall. The development of the API took place on the very early whatwg.org, mailing list and even in a few face-to-face meetings (recorded to the list). It was IIRC based on PostScript level 2, or really an Objective-C API based on the PostScript-2 model, from Apple. But a bunch of others had early say in the wide-open (to members, and in te…
Yes, I was a bit snarky in mine, but didn't intend to troll.
I was just an user, when the canvas tag appeared. I remember, that it was available for Safari and Dashboard on OSX, and then later in other browsers. I also remember, that at the time, Apple started to assert patents on it.
Dart's imlementation is harder, I also agree. However, what I see from Google at this stage is call for cooperation to shape the language, not something that is done and the others have to accept as-is. The call may be considered even more public than whatwg mailing list. And yes, I agree that the complexity of integrating another VM into existing engines may kill it in the end.
I actually do not like some design goals of Dart, but I understand, that there is demand for Java-like language in browser and that there is impedance mismatch between Java/GWT on one hand and JS in browsers on the other, that Dart intends to solve.
Earlier quoted context omitted.
I remember canvas in 2004, I demo'ed it in a Firefox prototype at Web 2.0 that fall. The development of the API took place on the very early whatwg.org, mailing list and even in a few face-to-face meetings (recorded to the list). It was IIRC based on PostScript level 2, or really an Objective-C API based on the PostScript-2 model, from Apple. But a bunch of others had early say in the wide-open (to members, and in te…
Hello, thanks for the reply. Yes, I was a bit snarky in mine, but didn't intend to troll. I was just an user, when the canvas tag appeared. I remember, that it was available for Safari and Dashboard on OSX, and then later in other browsers. I also remember, that at the time, Apple started to assert patents on it. Dart's imlementation is harder, I also agree. However, what I see from Google at this stage is call for c…
Apple's origination doesn't alter this distinction between the nature of the two things, and Apple played fair once they contributed the work.
Witholding patents when there was no WHATWG patent process or even a legal entity or membership structure was totally expected. The W3C has a patent protocol that Apple has used many times, and the w3c is where canvas has indeed landed as a Royalty-Free standard.