https://www.tiobe.com/tiobe-index/

What’s missing is non-Apple adoption. I’m hoping Swift becomes an acceptable/competive option on other platforms.

What are the target environments like in non-Apple systems?

[0] https://github.com/swift-server/work-group

I think the reason you'd pick it for a server language is because the strengths of the language and ecosystem meet your server requirements.

”The goal of the Swift project is to create the best available language for uses ranging from systems programming, to mobile and desktop apps, scaling up to cloud services”

And if “doesn’t have rich libraries and vibrant communities” were a decisive argument to not start using a new language, there never would be a new language again. I can see that, for some, using Swift on the server could be the right choice (for example because it makes it easier to share code between server and iOS apps)

I'm programming in it daily and its uglier and has more syntax then it should. Its very much like my experience with Transact-SQL, I'll use it and gain as much proficiency as possible, but I really don't like programming in it.

Anything that makes code beautiful works for me. Swift somehow can't be per_line_efficient and aesthetically pleasing to me.

let x = “Hello world”

var isDone = false

Filtering an array in one line is much nicer than a for loop:

let newList = anArray.filter(...)

No header files reduces code significantly.

I am using a lot of different languages so 'what I am used to' means lots of different stuff. Ruby has some of C beauty. Python does not. Haskell is probably most beautiful of them all. All individual and from my point of view of course.

https://h4labs.wordpress.com/2016/02/09/should-i-use-objecti...

The ++ operator was removed from Swift. Haskell uses ++ for concatenation. The case where ++ to add 1 is desirable occurs much less often than a variable declaration, which is better in Swift.

  while (*d++ = *s++);

  qsort []     = []
  qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++ qsort (filter (>= x) xs)

  func strcpySwift(_ d:UnsafeMutablePointer<CChar>,
                   _ s:UnsafeMutablePointer<CChar>) {
    for i in 0... {
      d[i] = s[i]
      if s[i] == 0 {
        return
      }
    }
  }

  func qsort<T:Comparable>(_ arr:[T]) -> [T] {
    var xs = arr[...]
    guard let x = xs.popFirst() else {
      return []
    }
    return (qsort(xs.filter{$0 <= x})) + [x] +
           (qsort(xs.filter{$0 > x}))
  }

Back to the one idiomatic C example. The few places where it’s terse does not make up for the many other places where it’s not. You also have memory management with malloc for additional code. If you compare nontrivial code, Swift is a more modern, safer, less verbose, etc way to develop iOS apps vs Objective C.

https://stackoverflow.com/questions/9558335/filter-an-nsarra...

Food food1 = [Food alloc]initWithName:@"samsar" andId:@"1"];

Food food2 = [Food alloc] initWithName:@"rusaramar" andId:@"2"];

NSSarray array = [NSArray arrayWithObjects:food1, food2, nil];

[array filterUsingPredicate:[NSPredicate predicateWithBlock:^BOOL(id evaluatedObject, NSDictionary bindings) {

    return [evaluatedObject.foodName hasPrefix:searchBar.text];

Stabilizing source code doesn't have any meaning that I know of. But the updates to the language and library are good!

Looking forward to what they come up with regarding ownership semantics.

Programs written in Swift 4 will compile under the Swift 5 compiler, etc.

    if a..b ∩ ..<c: