4 ms·

Nonsense. Dart is open source, and it is designed to compile to efficient JavaScript that runs in all modern browsers. There is no walled-garden angle at all he

Nonsense. Dart is open source, and it is designed to compile to efficient JavaScript that runs in all modern browsers. There is no walled-garden angle at all here.

kevingadd 13y ago
Open source doesn't mean anything if all the early design decisions were made in secret and ongoing design decisions are made by a single stakeholder. That is not how open web standards are built. Yes, you have the source code, so you can fork Dart if you want, I guess. How are you going to get your Dart fork into a browser?
- parfe 13y ago
  You badly conflate open source and an open standards process.
  - kevingadd 13y ago
    I'm not conflating anything. You can't use 'Dart is open source' as a defense if people are complaining about walled gardens; it's entirely possible to have a walled garden around an open-source product.
- ahoge 13y ago
  >if all the early design decisions were made in secret Sounds like any other language or any other piece of technology. No one starts with standards. This always happens some time after 1.0. http://en.wikipedia.org/wiki/JavaScript#History http://en.wikipedia.org/wiki/JavaScript#History first shipped in beta releases of Netscape Navigator 2.0 in September 1995 In June 1997, Ecma International published the first edition of the ECMA-262 specification. > you can fork Dart if you want You don't have to. The tools and the VM will continue to work. In the late 90s, I used a compiler from 1989. It still worked fine and it still works fine today (e.g. via DOSBox). I really don't know why everyone here seems to think that these kind of tools will self-destruct if left alone. They really don't do that. > How are you going to get your Dart fork into a browser? You don't have to. You can still compile to JavaScript. You can still use the VM on the server, for command line stuff, or on Android devices (there will be an ARM VM soon). It would be only a problem if you wouldn't be able to use browser with native Dart support for client-side web development, because compilation takes a few seconds and because you wouldn't be able to debug from within the IDE.

Nonsense. Dart is open source, and it is designed to compile to efficient JavaScript that runs in all modern browsers. There is no walled-garden angle at all here.

kevingadd 13y ago

Open source doesn't mean anything if all the early design decisions were made in secret and ongoing design decisions are made by a single stakeholder. That is not how open web standards are built. Yes, you have the source code, so you can fork Dart if you want, I guess. How are you going to get your Dart fork into a browser?

parfe 13y ago
You badly conflate open source and an open standards process.
- kevingadd 13y ago
  I'm not conflating anything. You can't use 'Dart is open source' as a defense if people are complaining about walled gardens; it's entirely possible to have a walled garden around an open-source product.
ahoge 13y ago
>if all the early design decisions were made in secret Sounds like any other language or any other piece of technology. No one starts with standards. This always happens some time after 1.0. http://en.wikipedia.org/wiki/JavaScript#History http://en.wikipedia.org/wiki/JavaScript#History first shipped in beta releases of Netscape Navigator 2.0 in September 1995 In June 1997, Ecma International published the first edition of the ECMA-262 specification. > you can fork Dart if you want You don't have to. The tools and the VM will continue to work. In the late 90s, I used a compiler from 1989. It still worked fine and it still works fine today (e.g. via DOSBox). I really don't know why everyone here seems to think that these kind of tools will self-destruct if left alone. They really don't do that. > How are you going to get your Dart fork into a browser? You don't have to. You can still compile to JavaScript. You can still use the VM on the server, for command line stuff, or on Android devices (there will be an ARM VM soon). It would be only a problem if you wouldn't be able to use browser with native Dart support for client-side web development, because compilation takes a few seconds and because you wouldn't be able to debug from within the IDE.