Accéder au contenu principal

Google's Fuchsia OS-the successor to Android and Chrome


Google's Fuchsia OS can now run Apple's Swift code

Could it be preparing one OS to rule them all?

Fuchsia
Back to the Fuchsia
WHAT IS FUCHSIA OS? Noone truly knows what it's for yet, but it seems to be heading towards being the successor to Android and Chrome - one ring to bind them etc etc.
But Google's new operating system has a new trick up its sleeve. It will also run code made in Swift, Apple's programming language. If that's the case, although we won't necessarily be able to get iOS apps running on Android natively, it will be a heck of a lot easier to port them.
Google is planning to contribute its own code to the main swift fork, so its activity will benefit both sides of the mobile OS divide.
Fuchsia OS already supports C and C++, Dart, Go, Rust and Python. That makes us think it's going to be the next generation that will unify its existing efforts, and not before time.
Whether it'll be an all-out replacement or if it'll be a method of making it easy to develop across Android, Chrome and even iOS, remains to be seen. That was hinted at in the fabled Andromeda OS that Google was said to be working on but which never materialised (in fact Fuchsia and Andromeda may be one and the same).
Google is in an awkward situation. Both Android and Chrome have proved hugely successful but are growing apart rather than together. Although there is Android runtime on many Chromebooks now, many users have complained about how it has been integrated as ineffectual.
Meanwhile attempts to make Android desktop machines have had varying degrees of success, with Remix OS, seen by many as the big third-party hope for Android beyond tablet sizes opting to leave the consumer-facing market, while Google's own efforts have been greeted by mixed results.
Microsoft has suffered similar problems. It now is able to support Swift in its Universal Windows Platform, and indeed Candy Crush Saga for Windows is a port from iOS. But Android integration has defeated it and so hopes of running Android apps natively on Windows have been scuppered again. It's just possible that Fuschia might bring that possibility back from the dead too - and though it's too late for Windows Mobile, it could be a huge boon for the Windows-Android Chest Burster apps. µ

Commentaires

Posts les plus consultés de ce blog

easy drag-and-drop website builder

WINDOWS MAC LINUX WEB IPHONE ANDROID PRODUCTIVITY DEVELOPMENT GAMES SOCIAL BUSINESS Lists Sign up Login Crowdsourced software recommendations Which app do you want to replace? Find apps 32 Like Mobirise Create cutting-edge, beautiful websites that look amazing on any devices and browsers.  Created by Mobirise Website Builder Free   Open Source   Mac OS X   Windows   Android     Mobirise - is a super easy drag-and-drop website builder. Drop the blocks you like into your page, edit content inline and publish - no technical skills required. Develop bootstrap-based, fully responsive sites that look amazing on any devices and browsers. Preview how your website will appear on smartphones, tablets and desktops directly in the visual editor. Free for commercial and personal use. Download for Windows, Mac, Android. Boost your ranking - Sites made with Mobirise ar...

L’ARCHITECTURE REST EXPLIQUÉE EN 5 RÈGLES

L’ARCHITECTURE REST EXPLIQUÉE EN 5 RÈGLES par Nicolas Hachet     17 commentaires   Confirmé ,  PHP     architecture ,  REST     Permalink REST (Representational State Transfer) ou RESTful  est un style d’architecture permettant de construire des applications (Web, Intranet, Web Service). Il s’agit d’un ensemble de conventions et de bonnes pratiques à respecter et non d’une technologie à part entière. L’architecture REST utilise les spécifications originelles du protocole HTTP , plutôt que de réinventer une surcouche (comme le font SOAP ou XML-RPC par exemple). Règle n°1 : l’URI comme identifiant des ressources Règle n°2 : les verbes HTTP comme identifiant des opérations Règle n°3 : les réponses HTTP comme représentation des ressources Règle n°4 : les liens comme relation entre ressources Règle n°5 : un paramètre comme jeton d’authentification Les 5 règles à suivre pour implémenter REST Règle n°1 : l’URI comme iden...

Dîner des philosophes

Dîner des philosophes Le problème du «  dîner des philosophes  » est un cas d'école classique sur le partage de ressources en  informatique système . Il concerne l' ordonnancement  des  processus et l'allocation des ressources à ces derniers. Ce problème a été énoncé par  Edsger Dijkstra 1 . Sommaire    [ masquer ]  1 Le problème 2 Remarques 3 Solutions 3.1 La solution de Chandy/Misra 3.2 Solution dans le cas pair 3.2.1 Preuve de l'exactitude de cette solution 4 Notes et références 5 Voir aussi 5.1 Articles connexes 5.2 Lien externe Le problème [ modifier  |  modifier le code ] Illustration du problème La situation est la suivante : cinq philosophes (initialement mais il peut y en avoir beaucoup plus) se trouvent autour d'une table ; chacun des philosophes a devant lui un plat de spaghetti ; à gauche de chaque plat de spaghetti se trouve une fourchette. Un phi...