Apple Details Swift 3.1 Ahead of Planned Spring 2017 Release

My opinion of Swift was that it is very regimented. You have to say the right thing, in the right way, or you get nothing.

It seems too hard, too 'fascist'. You have to do it their way. C was all about getting things done. If you really needed something done, you could lift heavy things with a small amount of code, and the language wasn't like a 'grammar Nazi', thumping you for every little thing. My first program in Swift wouldn't run because I did some little stupid thing wrong. I was surprised it cared. I was put off by it's attention to syntax details. It smacked of archaic languages like BASIC, and perhaps COBOL. YUCK!!!

If your reaction to a programming language is that it cares too much about getting details right, programming is not for you.

How about a 'lifetime update' ebook for Swift and Ojc-C for 'x' number of dollars...

I learned Swift with Apple's free iBook ('https://itunes.apple.com/us/book/swift-programming-language/id881256329'). They update it with every new release.

Apple is doing a lot of things right. But like all other news sites, MR just chooses to report more negative news bc it generates more activities then positive ones. It's a pretty sad strategy though.

I respect your opinion, but it is entirely false. We do not publish doom and gloom stories for clicks or to fulfill any other agenda. We truly try to report any news that is of any significance—good or bad. We really appreciate when our readers keep up informed by sending tips to tips@macrumors.com.

Finally; great to hear Apple is doing something right.

Objective-C used to be my favourite language but now I've switched to Swift, I would never go back. It's so much quicker to express an idea in Swift and so much easier to read it later. Not only that but my compiling code is much more likely to be correct.

There have been some mis-steps. Some of them are:

* The ABI is not defined yet so you can't make a pure Swift shared object library. This was one of the goals for Swift 3 but they blew it by spending too much time implementing WIBNI features suggested on Swift Evolution.
* An obsession with catching every error at compile time. This leads to nannying constructs in the language that are sometimes more trouble than they are worth. The prime example is access modifiers for object properties and methods. They are a complete mess in Swift 3.
* Old World snobbery leads to deprecating or perhaps just frowning on features that have been immensely useful in the past. The protocol oriented programming fascism - I mean fashion - is particularly annoying because it leads to people recommending highly convoluted opaque POP code to implement ideas that were quite naturally expressible with classes purely on the basis that Dave Abrahams gave a really cool talk at WWDC 2015 using one example cherry picked for the purpose. Also removal of ++ and -- on the grounds that "some people don't understand them" was pretty bad.
* The generics system is an overcomplicated clusterfsck.
* Frequent code breaking changes. At some point developers are going to get really pissed off at having to refactor all their code every time a new release of Swift comes out. This is in complete contrast to Objective-C where there's a good chance that a 64 bit program written for OS X 10.5 will still compile and run today. It doesn't help that each release of Xcode only targets one version of Swift (or exceptionally two, if you are lucky).

Fortunately, the first and last bullet points will go away at some point soon, in fact the last point is probably almost irrelevant already. The fourth point is being addressed slowly, but I think there will always be a problem with points 2 and 3. There's no shortage of people coming on Swift Evolution and saying "I keep making mistake x because of feature y, therefore feature y should be removed".

Anyway, despite all of the above, Swift is still a really nice language in which to write code. and the open sauce means it should get a bit more traction outside of the Apple ecosphere.

Contemplate this:

// begin the disaster

class MyClass
{
func stateFunction() -> () -> String
{
func internalFunction()-> String
{
return x
}
}
}

let myClass : MyClass = MyClass()

let r : String = myClass.stateFunction()() + + " Swift is a f##### disaster!"

/// end the horror

*any* language that so blithely allows such horrible code to be written and executed should never take hold.

A novice programmer (the type targeted by swift) will have no clue as to the dangers the above posses to pointer unwinding. The mind boggles when contemplating all the havoc embedded functions can cause. As for the logic itself - think of correlated sub queries 8 levels deep in PL-SQL....

Sounds fun right? Code you would feel comfortable taking ownership of and hiring other clever newbies to maintain???

Blocks in obj-c are a pain in the arse for a reason...