So WebAssembly can't get here fast enough then, at least when it starts
Post by Danny Tuppeny Post by Alex Tatumizer
I can see advantages of DuoCode, but I'm afraid somebody with a
brainwashing power will hijack it to build something like Angular, and then
every corporate employer will require C#+Angular (this sum, for me, is less
This is no different to every corporate employer requiring AngularJS. But
I don't think it makes sense to say "we shouldn't have something good,
because they every employer will want it". If it's good, it's not a bad
thing that they'll want it. If it's not good, it's unlikely they'll want
it. The sort of companies that let non-technical managers demand particular
skills that you don't think are good are not the companies you want to work
But suppose the impossible happens (miracle), and we have clean and pure
Post by Alex Tatumizer
DuoCode UI component library.
Hesitating to ask: why do you (we?) need dart then? What is the advantage
of dart over DuoCode? The latter is much more mature, familiar to many
users, has quite decent IDE, no risk of sudden death, (+ all other things
you mentioned). ???
Even if C# is mature and here to stay, Duocode is still new and unknown;
so there are still similar risks of sudden death etc (though I hope neither
DuoCode or Dart disappear anytime soon!).
That aside, I just can't see any world in which case 100% (or even close)
would agree C# is better than Dart. The real question for Dart is how many
users does it need in order for Google to continue putting resources into
it (and that question is still valid, even without Duocode).
Nobody is complaining about too much choice in languages on the server. We
get to pick our language based on all sorts of factors (ease of
development, maintainability, suitability of job, familiarity, easy of
recruiting experienced devs, to name just a few). If we had some
language-agnostic VM in all browsers that meant we could write lots of
different languages, I would view this as a good (great!) thing. We should
have the freedome to pick our front-end languages just like we can pick the
A colleague today reminded me of a blog post
I'm a big fan of both Dart and DuoCode, I do still stand by that somewhat.
yet it's the only thing we can run in the browsers.
It was a terrible accident. I really believe we need a language-agnostic
runtime/vm in all major browsers. I really didn't ever expect it to happen
(the chances of browser vendors working together are slim) but I now have a
little hope after the announcement of WebAssembly
and if they're now open to working together to put the same thing into
their browsers to aid this; maybe one day we'll be able to cut our
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an
The meek shall inherit the Earth, for the brave will be among the stars.