7 ms·

Swift 5 will most likely include async/await

by guzik 8y ago

Apocryphon 8y ago
Whenever that is. It was originally slated for the last year.
- coldtea 8y ago
  We used to wait decades for any meaningful change in languages like C, C++, Java, JS, etc...
  - Dibes 8y ago
    I'm not sure how what we used to do or wait for is relevant now. Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time.
    - coldtea 8y ago
      >I'm not sure how what we used to do or wait for is relevant now. Because whether a language is slow to evolve only makes sense relatively to some baseline rate. >Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time. And yet still, today, popular languages take their time to get features like async/await. Python got it after 3.6 (so 20+ years on), JS only got it in 2017, C++ doesn't have it, Rust doesn't yet have it (it's coming), Java doesn't have it, C++ doesn't have it... Heck, Golang doesn't have generics and comfortable error checking still...
      - Dibes 8y ago
        It really is a language by language basis. Many languages adopt features insanely fast, many insanely slow. JS for example has as of late has a very fast rate of change[1]. Or you could look at how Java has changed from 8->10 and all the new features added there. There are other languages like C that haven't changed much at all (to my knowledge). It isn't relevant to take the rate of change of other languages and apply it to another as an expectation. You would get a better metric by taking the rate of change of the current language in the context of the last year or two.
  - matt2000 8y ago
    Sure, but these were languages that arrived with at least one huge improvement over the languages that existed at the time. Dart's async/await coupled with Flutter's proper support of it in their SDK is that huge improvement for me in mobile dev. In my experience, Swift is lacking any particular major improvement over ObjC. It seems like async/await could have been that big step, and Swift probably shouldn't have been adopted until it was in place. Just wasn't worth it. I realize that's a controversial topic and I know people who love Swift, just from my perspective it was such an enormous cost without enough upsides to justify it.
    - Apocryphon 8y ago
      I think type safety is Swift’s killer app. Other than that I don’t know what other major improvements over Objective-C other than the general conveniences of pithy modern languages.

Swift 5 will most likely include async/await

by guzik 8y ago

Swift 5 will most likely include async/await

Apocryphon 8y ago

Whenever that is. It was originally slated for the last year.

coldtea 8y ago
We used to wait decades for any meaningful change in languages like C, C++, Java, JS, etc...
- Dibes 8y ago
  I'm not sure how what we used to do or wait for is relevant now. Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time.
  - coldtea 8y ago
    >I'm not sure how what we used to do or wait for is relevant now. Because whether a language is slow to evolve only makes sense relatively to some baseline rate. >Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time. And yet still, today, popular languages take their time to get features like async/await. Python got it after 3.6 (so 20+ years on), JS only got it in 2017, C++ doesn't have it, Rust doesn't yet have it (it's coming), Java doesn't have it, C++ doesn't have it... Heck, Golang doesn't have generics and comfortable error checking still...
    - Dibes 8y ago
      It really is a language by language basis. Many languages adopt features insanely fast, many insanely slow. JS for example has as of late has a very fast rate of change[1]. Or you could look at how Java has changed from 8->10 and all the new features added there. There are other languages like C that haven't changed much at all (to my knowledge). It isn't relevant to take the rate of change of other languages and apply it to another as an expectation. You would get a better metric by taking the rate of change of the current language in the context of the last year or two.
- matt2000 8y ago
  Sure, but these were languages that arrived with at least one huge improvement over the languages that existed at the time. Dart's async/await coupled with Flutter's proper support of it in their SDK is that huge improvement for me in mobile dev. In my experience, Swift is lacking any particular major improvement over ObjC. It seems like async/await could have been that big step, and Swift probably shouldn't have been adopted until it was in place. Just wasn't worth it. I realize that's a controversial topic and I know people who love Swift, just from my perspective it was such an enormous cost without enough upsides to justify it.
  - Apocryphon 8y ago
    I think type safety is Swift’s killer app. Other than that I don’t know what other major improvements over Objective-C other than the general conveniences of pithy modern languages.