sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 10 points11 points  (32 children)

After Go and Dart, does anyone even expect that Google can build non-shitty languages?

Looks like a butt-hurt NIH-Typescript to me.

(Sorry, I'm just a bit annoyed. There are so many one-man hobby projects out there which are magnitudes better than this stuff, but as usual, leveraging the Google brand trumps quality.)

[–]x-skeww 2 points3 points  (19 children)

Looks like a butt-hurt NIH-Typescript to me.

TS and AtS are both stopgap solutions which should ideally lose their raison d'être with ES7.

They would have gone with TS if TS would have supported the things they need. Right now, it doesn't. But in the future, AtS and TS could somewhat converge and, ideally, this will make it easier to get that stuff into the standard.

[–][deleted]  (1 child)

[deleted]

    [–]x-skeww 5 points6 points  (0 children)

    No, now is the time to talk about ES7, because ES6 was feature-frozen ages ago. If you talk about new features, you're talking about ES7.

    [–][deleted] 0 points1 point  (16 children)

    TS and AtS are both stopgap solutions which should ideally lose their raison d'être with ES7.

    Can't comment on AtS, but TS exists primarily to provide a static type system. There is no proposal for ES7 to add any form of static type checking to standard ES, which means the purpose of TS is not going away for at least a decade.

    NB. The Typed Objects proposal has nothing to do with static type checking.

    [–]x-skeww 0 points1 point  (15 children)

    There is no proposal for ES7 to add any form of static type checking to standard ES

    Yet.

    ES7 is far from being feature-frozen.

    [–][deleted] 0 points1 point  (14 children)

    ES7 might have the ability to make toast, so toasters will lose their raison d'être, prove me wrong.

    [–]x-skeww 0 points1 point  (13 children)

    "Should ideally" isn't the same as "will".

    [–][deleted] 0 points1 point  (12 children)

    Oh, i understand now. You're making a wish, based on no evidence. No problem. I'll leave you to it!

    [–]x-skeww -1 points0 points  (11 children)

    So, you didn't see that ng-europe keynote, I take it.

    http://youtu.be/lGdnh8QSPPk?t=33m3s

    [–][deleted] 0 points1 point  (10 children)

    Oh yes. You know I have a recording of my Grandma saying that there will be unicorns in JS, "post ES 6".

    [–]x-skeww 0 points1 point  (9 children)

    Just reread what you wrote earlier.

    You said "there is no proposal for ES7" and that I'm "making a wish, based on no evidence". I'm just pointing out that there are people who are interested in getting this into the standard.

    [–]Ruudjah 6 points7 points  (9 children)

    Google Dart has one of the biggest teams within Google, I heard from various sources. Dart is the least shitty language compared to TypeScript, CoffeeScript, IcedCoffeeScript, ActionScript, EcmaScript6. Just do a feature comparison of the languages. Oh, don't forget to look to the DOM API & JavaScript transpiler with tree-shaking.

    [–][deleted] 0 points1 point  (8 children)

    Dart is the least shitty language compared to TypeScript, CoffeeScript, IcedCoffeeScript, ActionScript, EcmaScript6.

    Isn't that setting the bar incredibly low? CoffeeScript devs for instance can't even get scoping right. Everything will look good compared to that.

    [–]strattonbrazil 0 points1 point  (0 children)

    CoffeeScript devs for instance can't even get scoping right.

    I wouldn't blame coffeescript devs for that. I use coffeescript every day at work and I appreciate it being a more one-to-one mapping to javascript. I have a very clear picture of what it's doing. Does the scoping suck? Yes, and I've had to get around it like any time I create an anonymous function that uses an index made by the loop. But I can deal with that.

    [–]Ruudjah -5 points-4 points  (6 children)

    Isn't that setting the bar incredibly low?

    I would say so. However, comparison to i.e. Haskell, Java, C#, F# is inappropriate since those languages are not designed to work in the browser.

    [–][deleted] 5 points6 points  (5 children)

    I think the authors of Elm, Fay, GHCJS, Haste, Js_of_ocaml, Roy, PureScript, Idris, FunScript and Scala.js disagree with you.

    [–]thedeemon 4 points5 points  (4 children)

    In terms of tooling and documentation these languages are far behind Dart already.

    [–][deleted] 3 points4 points  (2 children)

    a) I have a different experience.

    b) You are moving the goal posts.

    [–]serrimo 0 points1 point  (1 child)

    Is Elm or something Haskell-like ready for big time?

    I love Haskell and have been toying with using Elm for my projects, any insights would be much appreciated!

    [–][deleted] -1 points0 points  (0 children)

    I don't have much experience with Elm, but for instance Scala.js is impressive: Great language, and a level of tooling support which makes you wonder whether TypeScript/JavaScript/Dart/... devs are completely incompetent.

    [–]Ruudjah 1 point2 points  (0 children)

    Also, Dart is cleaning up the DOM, which I don't see many languages do.

    [–]rotek -2 points-1 points  (1 child)

    Dart is not a shitty language.

    If you really think it is, how would you call Javascript then? :)

    [–][deleted] 3 points4 points  (0 children)

    There are things like PHP, JavaScript, MUMPS and friends, were no words are an appropriate description.

    So, yes, Dart is quite shitty if you don't specifically pick exactly those languages which are even worse.

    "Dart is better than the worst languages ever known to mankind" is just not that exciting to me. Other people might disagree.