Wow. Few things guarantee success like starting off a project with a good old-fashioned language flamewar!
Wow. Few things guarantee success like starting off a project with a good old-fashioned language flamewar!
Of course, if they wrote it in Swift 1 they would have had pains migrating to 2 and 3, but if they wrote it in C++ then they wouldn't be able to refactor any of the code as Xcode doesn't support refactoring C++....
You'll need languages and operating systems that are battle-tested (literally) in hard-real-time fault tolerant systems.
Swift should never have been on the whiteboard for something like that. It's never been used in that scenario.
For example you might use C, but ban malloc, and recursion. There will be static analysis tools that look through your code and calculate exactly how much memory you are using using in the worst case of function call tree, that way they know they cannot run out of memory or stack.