But having a programming language on a yearly schedule to announce updates is getting ridiculous.
While they keep compatibility and/or provide easy migration possibilities, and use the changes to improve the language and its environment (compiler, etc), I don't see how the updating could be seen as a negative.
Either that, or I have to stop buying printed books,
You are (1)BUYING (2)PRINTED books? In 2016?
Even in the 90s that felt to me like a bad idea.
and companies like Big Nerd Ranch have to start offering subscriptions to their ebooks so that the updates can be had for free for a certain yearly subscription. How about a 'lifetime update' ebook for Swift and Ojc-C for 'x' number of dollars...
I use a service similar to what you are asking for, and which actually covers all open-source languages, and lots of non-opensource too. They call it "internet".
How about a 'lifetime update' ebook for Swift and Ojc-C for 'x' number of dollars...
I wonder if doctors have some kind of "lifetime updates" for their books. I know that engineers don't have one, even software engineers. But yet again, this "internet" service comes pretty close.
I've got several iterations of their books sitting around here. A programming language shouldn't be a 'commodity item'.
Isn't that part of what killed Java?
I'd LOVE to know what definition of "killed" did you use there
[doublepost=1481539747][/doublepost]To those complaining about Swift changing too much: I really, really can't see what you are complaining about.
Look at this: https://github.com/apple/swift-evolution
There you have the fricking road map of Swift 4 for *next year*, with rationale, with possibility to participate on the development, and at the very least knowing where and why things are going. And not only that: you can see that in fact they are targetting goals of stability even at the ABI level, to avoid problems that have plagued the likes of C++ for decades!
And you are complaining that printed books get outdated??
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.
"Heavy things with a small amount of code"... in C, AKA the language without the concept of what a string is?
Please give me an example. PLEASE.
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,
Be thankful. Be very, very thankful. In C, your program might have looked like running, only to bomb later in any variety of exciting ways.
Or are you saying that you prefer languages which look easy while they merrily trash your memory because you forgot some hidden assumption in the code?
and perhaps COBOL. YUCK!!!
I'll still rather learn Obj-C, thanks...
At this point I'll be very, very surprised if you have any inkling of what COBOL even looked like.