Announcing Dart 2 Stable and the Dart Web Platform

Post by nailer » Tue, Aug 07, 2018, 9:00 PM UTC

sbjs wrote: post #99

pcwalton wrote: post #92

Earlier quoted context omitted.

> I think mostly because they were bit too hard by IE doing the exact same thing just a few years before. It's pretty simple, in my view: JS developers were happy with the language and didn't want a browser vendor trying to replace it. Remember that it was announced around the time that the new ES6 ("Harmony") features were generating a lot of excitement about the future of JS.

I think Dart started internal development around the same time CoffeeScript gained major popularity and brought attention to JS's desperate need to evolve, but they released at a bad time: when JS finally did start to evolve (as Harmony) which was a reaction to CoffeeScript in the first place. So CoffeeScript served its purpose of pushing JS forward, and most other compile-to-JS languages had no more purpose. I say m…

Post by wmfiv » Tue, Aug 07, 2018, 9:20 PM UTC

munificent wrote: post #139

kbd wrote: post #124

Earlier quoted context omitted.

I think a lot of what people found off-putting about Dart is that Google already recently came out with a new language that has become very successful. Announcing another one, which at first glance looks like yet another curly brace language not that far from Java, was a step too far for people to be interested. Nowadays, the only thing driving Dart seems to be Flutter, which again is head-scratching. Like, "Flutter…

I could be wrong, but I don't believe the existence of Go was much of a problem. Go and Dart are very different languages aimed for very different use cases. If anything, I think Go helped us because we could point to it as a successful language that Google hasn't cancelled. > not that far from Java This is something that hurt us, I think. You can write Dart code that looks a lot like Java, and many of our early publ…

Post by nailer » Tue, Aug 07, 2018, 9:25 PM UTC

munificent wrote: post #139

kbd wrote: post #124

Earlier quoted context omitted.

I think a lot of what people found off-putting about Dart is that Google already recently came out with a new language that has become very successful. Announcing another one, which at first glance looks like yet another curly brace language not that far from Java, was a step too far for people to be interested. Nowadays, the only thing driving Dart seems to be Flutter, which again is head-scratching. Like, "Flutter…

I could be wrong, but I don't believe the existence of Go was much of a problem. Go and Dart are very different languages aimed for very different use cases. If anything, I think Go helped us because we could point to it as a successful language that Google hasn't cancelled. > not that far from Java This is something that hurt us, I think. You can write Dart code that looks a lot like Java, and many of our early publ…

    import 'package:hauberk/src/engine.dart'
    import 'package:hauberk/src/content.dart'

    content = createContent()
    save = content.createHero("blah")

    while (true) 
    watch = Stopwatch()
    watch.start()

    # Generate a dungeon at each level.
    count = 0
    for (i = 1; i = -1) count++      

    watch.stop()
    print("Generated $count dungeons in ${watch.elapsedMilliseconds}ms")

Post by andrewbinstock » Tue, Aug 07, 2018, 9:29 PM UTC

munificent wrote: post #139

kbd wrote: post #124

Earlier quoted context omitted.

I think a lot of what people found off-putting about Dart is that Google already recently came out with a new language that has become very successful. Announcing another one, which at first glance looks like yet another curly brace language not that far from Java, was a step too far for people to be interested. Nowadays, the only thing driving Dart seems to be Flutter, which again is head-scratching. Like, "Flutter…

I could be wrong, but I don't believe the existence of Go was much of a problem. Go and Dart are very different languages aimed for very different use cases. If anything, I think Go helped us because we could point to it as a successful language that Google hasn't cancelled. > not that far from Java This is something that hurt us, I think. You can write Dart code that looks a lot like Java, and many of our early publ…

Post by coldtea » Tue, Aug 07, 2018, 9:31 PM UTC

sbjs wrote: post #137

hota_mazi wrote: post #134

Earlier quoted context omitted.

> A language by itself is almost never useful, every language needs a killer app, I don't understand why this myth is still around. C++ never had a killer app to start its momentum. Neither did Javascript. Nor Java really (or maybe applets, back in the days?). Languages can succeed on technical merits alone if they come out at the right time and fix real problems that programmers experience on current mainstream lang…

These days it's mostly about apps, because apps are the main thing that facilitate the transfer of $$$. In the 80s and 90s, enterprises were full of $$$ and needed fast and safe languages for writing all their software. C++ came out to solve this need, and Java came out saying it could do it better. Today enterprises are moving many of their internal tools to the web. Enterprises don't need apps per se, but they do n…