This changes everything. Again.
Predicting Mac OS XI and iOS X to be built from the ground up using Swift.
Predicting "Mac OS XI" at all means you're wrong.
This changes everything. Again.
Predicting Mac OS XI and iOS X to be built from the ground up using Swift.
Crap.
Bought an introduction to Objective-C a couple of weeks ago (aimed at peoples with no programming experience at all...like me)
Can I get a refund ?
How about the 600 page book free on the iBooks store.
.....but the visual part of me wishes that the white bird in the icon were flying upwards towards the top right corner instead downwards towards the bottom right corner. I guess I just have to deal with it!
I'd say that's a bit of a stretch, it's hardly a beginners guide to programming, but I doubt that was the intention.
I'm going to go against the flow, I think Swift seems utterly pointless.
Another new language only used on Apple is another barrier for people getting involved with Mac development. Apple also has a history of offering bridges and then giving up, remember Python?
The playgrounds/interactive programming is all well and good when you have an extremely simple example like they had in the keynote. I'd be interested in seeing how it works with a larger, complex project.
Even then, their example was a game. Anyone with half a brain will be using an engine to create their games. Frankly, Apple's efforts with SpriteKit and SceneKit (or whatever it was called) is far too little far too late. There's engines using a variety of languages that not only use more commonly used languages but are also easily portable to other architectures. You'd be an absolute fool to use the basic tools that Apple are offering.
I would be curious to see if there will be support in open source compilers for this language. I don't want to be a party pooper, but I prefer programming languages that are open and have support in more than one platform/compiler (let's say C, C++, Java, Basic, etc.). I think to really make it into university classes they would have to have a compiler that works in Linux or any other UNIX like OS.
Today's programmers have it easy.
We programmers from the 80s used to have to build linked lists from dirt and bits of string we found on the ground.
The programmers from the 70s had to punch their code out on cards and feed the cards into the machine.
Inferred variable types...pshaw.
Wait a minute now, smalltalk has something very similar to playground way back in the 80's.
As for swift, interesting, but I do not see it replacing objective-c anytime soon.
just another scripting like language. eg. rubymotiion
The iBook is okay.. but certainly not complete, Here's to hoping that the folks at "Big Nerd Ranch" and Stephen Kochan can get some helpful books out soon.
Also, I wish Apple's documentation (iBook) was printable, it is often easier for me to read and markup/make notes on a physical copy.
Predicting "Mac OS XI" at all means you're wrong.
Wait a minute now, smalltalk has something very similar to playground way back in the 80's.
As for swift, interesting, but I do not see it replacing objective-c anytime soon.
just another scripting like language. eg. rubymotiion
So what are the chances/possibilities this language makes it beyond apple products? It would be great if it could be cross platform.
How can I learn the language without having any other programming experience? Is there a class I can take in university?
Nahhh .... Here ya go:
Image
I disagree. I think people learn by doing. There are far to many terrible computer scientists who have all the theory and no practical knowledge.I've always felt that Ruby was a programmer's programming language, that is to say, it's really only fully appreciated by people who are already experienced coders. It's a fantastic language, but if I was going to suggest a very first language, I'd start with something like Java or C++. Both were languages taught in AP Computer Science classes, to give you an idea of how easy they are to learn and use as a medium for learning computer science. You can learn the basics on languages like those and start to understand the logic of computing before you worry about more "advanced" features like generics, closures, and so on. Go and learn object-oriented programming, get a feel for loops, switches, inheritance, data structures, and I/O. After that, go learn Ruby if you want, or dive right into Swift.
One of the reasons why Swift has gotten so many developers excited, while a lot of the tech media is a bit confused by it, is because it's really the sort of thing you need to understand the background of, and have experience in other languages first, before you can fully appreciate what Apple is trying to do.
Bottom line, I think Swift would be overwhelming to you right now. I think Ruby would leave you ill-prepared for other languages. At the very least, wait for Swift to get some good books out first. Apple's eBook is really not intended for beginners. Give it six months and you'll have a wide selection of "Swift for Beginners" books from great computer language educators.
Looks like a project started by Scott Forestall
How can I learn the language without having any other programming experience? Is there a class I can take in university?
There's a big book about it on iBooks. Plowing through it, and it seems straightforward enough. It's amusing to see how language design decisions map down to what/how clang/llvm does for optimization.
For those who care, it's worth watching the previous clang/llvm WWDC sessions (they're on iTunes U/dev.apple.com).
llvm and its ilk has come a long way from being a generally retargatable VM.
----------
Swift would be fine, especially if playgrounds actually work.
There's a lot more to programming than the language, though. There's how you hook everything together, which is totally different than actual programming.
What needs to happen, really, is someone needs to come out with a Hypercard/VB like structure/framework so you can just type swift code into stuff and it'll just work.
Crap.
Bought an introduction to Objective-C a couple of weeks ago (aimed at peoples with no programming experience at all...like me)
Can I get a refund ?
I've read quite a bit of it. There's a lot lacking. Since when was a languages sum total documentation a single static PDF?
I guess the books fine, but there's a lot of the syntax which appears to be largely undocumented. The books a start but the fact there isn't much more right now is a little disappointing.
I'm going to go against the flow, I think Swift seems utterly pointless.
Another new language only used on Apple is another barrier for people getting involved with Mac development. Apple also has a history of offering bridges and then giving up, remember Python?
The playgrounds/interactive programming is all well and good when you have an extremely simple example like they had in the keynote. I'd be interested in seeing how it works with a larger, complex project.
Even then, their example was a game. Anyone with half a brain will be using an engine to create their games. Frankly, Apple's efforts with SpriteKit and SceneKit (or whatever it was called) is far too little far too late. There's engines using a variety of languages that not only use more commonly used languages but are also easily portable to other architectures. You'd be an absolute fool to use the basic tools that Apple are offering.
It was announced, and it was ready. Doesn't sound like Forstall to me.