How things change: Google would be considering using Swift as the primary language of Android

Have you heard of "Telecatch", the old television show of brutal free fights that, in fact, was nothing more than staging? The world of technology is not very different. If on the surface everyone seems to be fighting with everyone, behind the scenes the very different thing: old rivals form partnerships, use parts of each other and come together for common goals since the world.

This time the Android, whose rivalry with iOS instigates countless unbearable flame wars on the internet every day and has already made Steve Jobs declare that it would cause "a thermonuclear war" to destroy him, which begins to show signs that he will move to a language created by Apple. Can you believe it?

Sources informed the The Next Web that, last December, executives from the Google met with representatives from Facebook and Uber to discuss the programming language Swift, from Apple. Coincidentally or not, December was the month that Ma announced that Swift was becoming open source, with the main aim of stimulating the mass adoption of language in the computer world.

https://www.youtube/watch?v=ghdTqnYnFyg

The informants say that Google would be considering making Swift the new primary (or “first-class” language, as they call it) for Android, because it considers its strengths stronger than those of Java, the current holder of the post. Furthermore, apparently the Mountain View giant would be concerned about the outcome of the current legal dispute with Oracle, owner of Java, and possibly looking for alternatives to replace it.

A change of this magnitude would bring a number of benefits to Android, the most obvious of which is a huge ease for developers to create cross-platform applications. General improvements in system performance would also be a likely consequence of this decision if it is real, of course.

Obviously, in the case of a system as complex as Android, the process of change would not be simple or fast, so it is speculated that this would be a slow, gradual and secure transition. To migrate the system to Swift, Google would first have to create a runtime for that, and then to make its APIs and SDKs compatible with the language which would involve the complete rewriting of some parts of the robot's core, hercule work even for a company the size of Google. Unfortunately, not everyone who creates their systems is already thinking about the problems of the future.