On Tue, 11 Oct 2011 16:31:13 +0200, Chris Koerner <[email protected]>
wrote:
Ouch..
http://blogs.perl.org/users/rafael_garcia-suarez/2011/10/why-dart-is-not-the-language-of-the-future.html
With "ouch" do you mean the poor quality of the blog post, right?
"The spec has even a chapter on factories (static constructors). (Oh my,
factories? it's like 1997 and design patterns all over again!) I should
note that the integration of popular design patterns at the syntax level
is disappointing: design patterns tend to emerge to work around a language
design's weaknesses. Embracing them is a bit like admitting a design
failure up front."
Please explain me this. For what I've understood, Dart factories are just
syntactic sugar to define a default implementation of an interface. I
don't understand the elaboration about design patterns and "design
patterns to work around a language weakness".
"Another example: Ovid pointed me at the NoMoreElementsException, and
added: "didn't Java programmers learn years ago that you throw exceptions
for exceptional things and not for expected things?"
To me this is bullshit, because exceptions are just part of the outcome of
the method execution. You can choose to use them only for exceptional
purposes, as well as going the opposite direction. A withdraw() method
throwing NotEnoughMoneyException is not exceptional (especially for me in
this period) but can make perfectly sense.
At this point I gave up reading. After all, it's so clear that the
language of the future is Perl.
BTW, up to that point I've read several assertions about the fact that
Dart would loose runtime information about types, which it's not how I
understood it, but I might be wrong (but: if Dart has got reified
generics, how can it loose type info at runtime?).
Generally speaking, I find that the picky review of such details of a
language is a really boring approach to comment about it. Given that Dart
is aimed at becoming a better JavaScript, I'd like to see people
discussing on whether the two claims by Dart guys (about JavaScript being
too flawed to scale) are reasonable or not. For instance, I've not read so
far which points for which JavaScript wouldn't scale for JIT performance
have been fixed by Dart.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
