@_jayphelps it's "standard - something that everybody can use" vs. "standard - something everybody has to use" @wycats
-
-
Replying to @mraleph
@mraleph@_jayphelps Sounds like you're bitter about Dart? http://www.ecma-international.org/publications/standards/Ecma-408.htm … I think you're confusing "can use" with "wants to use"5 replies 0 retweets 3 likes -
Replying to @wycats
@wycats@_jayphelps e.g. I can use Dart and I do use Dart instead of JS. but it could be easier to use it, if web was less JS-tyranic2 replies 1 retweet 0 likes -
Replying to @mraleph
@mraleph@_jayphelps Who do you think is "JS-tyranic". The JS people I know are working hard to evolve towards safe, native code.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@_jayphelps ... e.g. all this work you are referring to does not help to run dynamic languages in the browser with low overhead2 replies 2 retweets 2 likes -
Replying to @mraleph
@mraleph@wycats sounds like you want a true bytecode VM, am I following? https://www.dartlang.org/articles/why-not-bytecode/ …4 replies 0 retweets 0 likes -
Replying to @_jayphelps
@_jayphelps@mraleph If your solution is "big bang release" of a totally new thing, you should work on iOS, not the web.1 reply 1 retweet 2 likes -
Replying to @wycats
@wycats@_jayphelps don't you think that telling me where I should work is again illustrating my point about fake "openness" of the web?3 replies 0 retweets 2 likes -
Replying to @mraleph
@mraleph@_jayphelps But I'm not longer surprised when people touting "openness" openly deride the opinions of their open collaborators.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@_jayphelps well, how would you be surprised if that's what you do?3 replies 0 retweets 0 likes
@mraleph @_jayphelps Most people share your concerns about enabling more languages, but not the big-bang tactics.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.