There's nothing professional about choosing the wrong platform for your application and then jumping into a new proprietary language in the hope of fixing things with a rewrite.
> Have you looked at the medical devices in a hospital, recently?
Are you trying to imply they are Apple devices and/or becoming Apple devices? Because that's entirely opposite of what's going on at the several local hospitals (admittedly all under the same organization) near me.
They are implying that medical devices are notoriously bad at being proprietary/closed. Hospitals would be much better off if the devices could talk to each other but it isn't feasible as-is because device manufacturers want lock-in. The current situation leads to issues like alarm fatigue where nurses effectively ignore problems due to too many devices. If they were centralized then there could be one management system that intelligently alerts the nurse of any issues.
Let's not forget that Apple announced back in June that Swift would be open sourced by the end of 2015; it might end up being a holiday present for developers.
What's irrational about disliking an environment hostile to developers? When you you do robotics, you want full control over the software, so the natural fit is some Linux variant, not OS X or iOS.
I could say that far more about FOSS developers. Many of them operate under the idea that they bear no responsibility for the software they write, and as such, have no impetus toward quality.
Maybe you don't realize that "software" includes the kernel. Is it even possible to do a real-time fork of it like people did with RTLinux, RTAI and Xenomai?
Of course it's not, because OS X gives you shit and you invested so much in it already that you have to convince yourself that it tastes good.
There's nothing professional about choosing the wrong platform for your application and then jumping into a new proprietary language in the hope of fixing things with a rewrite.