Why Swift Will NEVER Replace RubyMotion
I’ve been seeing a lot of tweets from people saying that Swift has basically killed RubyMotion, which is extremely far from the truth, and I’m going to explain why quickly and without much fuss, because people seem to just be saying it without thinking.
Post a comment