Swift > C / C++
This year’s WWDC was one of the better ones in recent memory for developers and app publishers interested in leveraging Apple’s platforms to create great products and services. After digesting the changes internally here at Buccaneer. In particular, we’ve been thinking about what the open-sourcing of Swift is going to mean for the wider development community. In short, we think it’s going to have a major impact.
If you don’t know, Swift is Apples new general purpose programing language that is the future of iOS and Mac OS X development. That alone is huge news and a major change for anyone interested in the app business, but that’s not the end of the story.
Swift is not intended just an app development language but a more general tool. In fact, Apple has stated that it can be used from everything as low level as systems programing. This could be a game changer. Don’t get me wrong, C and C++ have been doing a great job, but there’s showing their age and there’s just some nagging issues in those languages that are a little too reminiscent of the eighties to be something that we ought to be putting up with in 2015. Of course, the question is going to be performance. For Swift to really be a viable replacement for C / C++, it needs to either be on par or better than those languages from a performance point of view; after all, the main reason for using those languages is performance.
Some of you may be thinking that we’ve put down the rum and picked up the Apple Kool-Aide in thinking that Swift might actually be a replacement for C / C++ but consider that we and Apple are not the only ones looking to move on from those languages. Google is as well with their Go programming language, a topic we will cover at a later date.
Want to get your Swift project off the ground? Use the contact form on this page to send us details and we will get back to you!