I just realize Apple's strategy on compute and hpc, they Trojan Horse its Swift 3.0
Those familiar with python and c# and learning Swift should have noted very similar constructs and syntax differentiated mostly by trivial things.
Ok past week was finalized Swift 3.0 specification, guess that is not compatible with previous versions and most code will need a huge make up to migrate to swift 3, but still possible some automated tool will do, is that a bad thing you may think yes that is bad, unless you're familiar with python structures, the shinny new Swift 3.0 will allow migrate python code with mere trivial changes most can be done by common refactoring but certainly it's possible to write a python -> swift 3 migration tool fully automatic and 100% precise what you get on python its what you'll get on swift 3, you may think ok we now have tons of python code to migrate to OSX iOS apps , what it has to do with HPC? , you miss Swift since 2.0 its opensource? Yes you can run swift 3 code on a cheap raspberry pi zero as well as on the biggest cluster, with few solid advantages over python given swift its fully compiled its efficiency its superior to what you can get from python compilers as pypi and close or better than raw C, plus tons of new features plus an powerful ide (Xcode also Kdevelop), imagine you are on R&D at some hexascale compute project , you can code and test it on a Mac pro importing/translating whatever code you need from C/C++/Objective-C/Python and maybe later C# too, and later with simple script migrate it to production clusters running Linux or BSD or whatever where you have the open-source Swift 3 compiler.
[Insert Tim Cook voice in keynote mode]
That's Awwwnmaaaaaahhhzzinnnnng
[End of Tim Cook voice keynote mode]
