This one particular guy had a passive agreesivd streak a mile wide. He did a lot of things counter to management. It was a final straw.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Announces Swift 2, Open Source for iOS, OS X and Linux
- Thread starter MacRumors
- Start date
- Sort by reaction score
This one particular guy had a passive agreesivd streak a mile wide. He did a lot of things counter to management. It was a final straw.
Pretty much agree. However, I do not see Swift going anywhere of worth for at least five years. I do not consider it a safe bet. My predict is we will see a merge of Obj-C syntax and the worthy parts of Swift into an "Objective Swift" type of hybrid.
Now the question is... do I continue to learn Python, or go full dive on Swift and hope that in the next couple years they release it on Windows?
Finish learning Python. Swift is a great language but it'll be a while before it catches up in terms of 3rd party learning materials. Python is one of the easiest languages you can learn right now because it has a massive community of coders around it, providing endless tutorials and other resources. If you have a question, even a fairly complicated and very niche question, chances are an answer is just a quick web search away. If not, you can always ask in one of the eleventy million places where people talk about Python and get a quick answer.
If you have a good understanding of object oriented programming (depending o how deep your knowledge of php is you may have this covered) the best place to learn is using Stanford's introduction to iOS programming on iTunes U. It is free and the course material is pretty good.
The Platforms State of the Union is being streamed now. Theres probably going to be a decent chunk of time spent on Swift 2 and of course the new Xcode.
I really enjoyed using Swift, playgrounds to test code etc. I started my next project using it and the amount of code I saved compared to Objective-C was considerable, and this was an audio sampling and conversion application using audio taps. But things got tougher and tougher with certain features relating to latency that were long winded using Core Audio via C turned into a hair pulling nightmare in Swift and I had to abandon it 3 weeks in. I restarted in Objective-C and managed to finish the project 2 weeks late. So, a lesson learnt. I hope that version 2.0 has improved vastly from my first experience.
It seems more and more people are adopting it based on the number of native Swift apps on the store.
It seems more and more people are adopting it based on the number of native Swift apps on the store.
Its great that Swift is going open source and hopefully that will attract more developers.
Though, its going to be an up hill struggle to meet the kind of adoption that Apple want. Existing languages such as Java, Ruby, Python, C# et al have a rich set of third party libraries to build backend server apps. Companies are not going to junk their existing code base for Swift. Its going to be a long slow process.
Though, its going to be an up hill struggle to meet the kind of adoption that Apple want. Existing languages such as Java, Ruby, Python, C# et al have a rich set of third party libraries to build backend server apps. Companies are not going to junk their existing code base for Swift. Its going to be a long slow process.
My advise is to wait and see on Swift. So far, there are no Swift only API on iOS 9 so you can work with it in Objective-C.
Also, the Open Source anarchists are going to play merry hell on the Swift compiler as the are in college or cashing their welfare checks. A lot of change from come from that.
Python has a good adopted market and you can make money at that. I have seen resumes passed over when "Swift expert" is mentioned and they did not work at Apple.
Swift Open Source ... Good move. But without the Cocoa integration/framework it remain a script language for background jobs and data processing. Which is still a good think. But a unified basic UI would be nice, too. Hopefully some 3rd party jumps in.
Oh, and VS 2015 community edition is something I also will look into.
Oh, and VS 2015 community edition is something I also will look into.
Yes, this should be on the front page. Massive news.
Swift was designed by academic high horses right out of the PARC culture with not enough practical experience in compiler and language design. Yes, I have met them and IMO, Steve would have given these guys a new ******* for how they wrote Swift. From that, there has been a huge push back on all fronts about the language, even inside Apple. Going open source is saying "Ok, we give up! Let's see what you can do with it." as the high horses review the public compiler builds for the new few years.
For me and others, the biggest syntax criticism is the arrow '->' mark to denoting function return variables on the right side of the function definition. Typically that is used for structure pointer member reference. If you know anything about compiler design, the reason why return variables are on the left of a function in source code is to build stack assignments during compiles in a single pass without a syntax backtrack. Swift breaks that convention and makes the compiler pass more complex.
I am not sure why you keep mentioning Microsoft, that are not really relevant anymore! Ballmer dug a hole so deep for Microsoft it will be a miracle if they can get out of it! Right now Microsoft is like a old company trying to stay relevant, they remind me of Kodak!
Just to bake your noodle Microsoft announced at Build 2015 that they will be adding Objective-C and Swift to Visual Studio! C# may die a slow death!
Microsoft also working on a Swift compiler for iOS developers to come to Windows 10
http://www.windowscentral.com/micro...swift-compiler-ios-developers-come-windows-10
Last edited:
So first thing that happens when I open my project in Xcode 7 is it tells me my code needs to be converted in Swift 2.0
Does anyone know if I can convert my code to Swift 2.0 and still run it on iOS 8? I've had so many errors I wouldn't know how to fix, that I haven't been able to try.
Does anyone know if I can convert my code to Swift 2.0 and still run it on iOS 8? I've had so many errors I wouldn't know how to fix, that I haven't been able to try.
If you need to submit to the App Store before iOS 9 comes out you should run both Xcode 6 & Xcode 7 at the same time. Keep a baseline of code for Xcode 6 and also create a separate copy or baseline to code and use it in Xcode 7!
Last edited:
I'll have to do this when iOS 9 has been released and generally adopted. I don't have enough time to branch my code (it's a hobby outside of my job unfortunately), the differences are too many. I was just wondering though - if I converted it say in September when Swift 2.0 is more stable and final, would it still work on iOS 8?
An immature language on a nearly obsolete OS model. This has greek tragedy written all over it.
If you want to play both sides of the street, avoid Swift like the plague. You will have enough issues with different library builds. Best is to have two separate projects in the same workspace. Build one project under Xcode 6 and the other under Xcode 7, share as much code as possible but keep seperate project settings. Any more advise and I start billing.
This is no surprise at all and shows how immature Swift is right now. They cannot even support backwards compatibility.
I am sure they totally redid the compile pass models following their hokey syntax. Looking forward to an object code analysis between Swift 1 and Swift 2 with the same source code. My prediction is that we'll see a revision in Swift syntax by the time the inevitable Swift 3 comes by next year.
This reminds me of the use and abuse of the JVM in the early Java days where old code would break under updated RTCs and force new syntax on the developers.
biggest news if you are a developer, Swift 2 is opensource, couldn't be more happier.
My linux box is ready
My linux box is ready
First, I would recommend joining the Apple Developer Program and download the beta for Xcode 7. Next, you can start by learning the Swift Language using Playgrounds. Next, I would recommend referencing the http://raywenderlich.com site for many Swift tutorials. Last but not least, the tutorials on the site are all relevant for OS X 10.11 and iOS 9.
One possible reason why Linux was chosen as an open source target because it's a Unix based operating system similar to Mac OS. Next, Apple doesn't want to implement Swift in the browser because EcmaScript committee is already working on delivering EcmaScript 6 which is the next version of Javascript. However, the week isn't over yet and there could be other announcements later in the week.
Now, I write professional iOS apps in Swift today and backends could be in many different languages these days. With this announcement, it would be possible to write both the client and backend applications in Swift. Very cool indeed!!!!!!