|
|
|
|
|
by detst
4602 days ago
|
|
> reasoning behind it In all of your condescending[1] comments, you have forgotten to actually articulate what your reasoning is. These are as close as you got: Dart doesn't have the open, cheerful intentions
Google's overbearing intention is obvious
flawed language
this one is doomed to fail
forced down our throat
[1] I'll Identify these on request. They're unwarranted, counter-productive and rude. |
|
---
I think my reasoning throughout this page has been more or less articulated, but I suppose I might try for a compact representation.
What exactly do you think is going to happen with Dart?
Is Google going to add Dart to every Chrome install? Sure, maybe. Will so many developers cry out that Safari and IE will also be forced to implement Dart runtimes?
Is every single browser going to run Dart because Dart will have made such a compelling case that it and it alone is preferable to javascript?
Why not python? Why not C, Java, Scala? We could be running those languages in browsers just as easily as we might run Dart.
Do you think Dart is that amazing? Do you think Dart is just so wonderful that it'll unite the programming world as never before?
No.
Even Google's pet framework is divided and recoiling.
The problem isn't that Dart has to compete with javascript, it's that it has to compete with every other language out there, and it's just not that special. Why Dart? If we're going to be serious about ripping up browsers, why Dart?
Now, I maybe should make it more clear: I don't have any problem with Dart as an experiment, Dart as a transpiled language, or even Angular.dart.
But Google doesn't get to decide the future of the web just because it has a bunch of fancy language designers. Google is trying to shove Dart down our throats, and it's not working, and it's not going to work.
Dart will remain a transpiled-to-js language for a time, and then fall off the radar when it's clear that it doesn't transpile to js very well. The alternative is a fantasy.