Google's upcoming 'Fuchsia' OS to support Apple's Swift language
Google's nebulous "Fuchsia" operating system -- still in development -- will apparently support apps written in Apple's open-source Swift programming language.

A Google employee recently created a pull request on Swift's GitHub repository, adding Fuchsia support to the compiler, Android Police noted this week. Fuchsia already supports a Google-created language called Dart, as well as standards like C and C++.
Swift support may make it easier for Apple developers to bring their apps over to Fuchsia. Google has yet to identify the goal of Fuchsia however, and indeed the company could conceivably abandon it as an experiment.
The platform is separate from Android and Chrome OS, and should be more easily scalable, which could let it run on everything from embedded devices through to full-fledged computers.
Swift is primarily intended for iOS, macOS, tvOS, and watchOS -- Apple is in fact heavily promoting the language at colleges and universities. It can also be compiled for Linux however, and as an open-source project it's not strictly under Apple's control.

A Google employee recently created a pull request on Swift's GitHub repository, adding Fuchsia support to the compiler, Android Police noted this week. Fuchsia already supports a Google-created language called Dart, as well as standards like C and C++.
Swift support may make it easier for Apple developers to bring their apps over to Fuchsia. Google has yet to identify the goal of Fuchsia however, and indeed the company could conceivably abandon it as an experiment.
The platform is separate from Android and Chrome OS, and should be more easily scalable, which could let it run on everything from embedded devices through to full-fledged computers.
Swift is primarily intended for iOS, macOS, tvOS, and watchOS -- Apple is in fact heavily promoting the language at colleges and universities. It can also be compiled for Linux however, and as an open-source project it's not strictly under Apple's control.
Comments
I watched a video on YouTube, and it’s not something anyone should bother looking into (at this point).
https://www.cnet.com/videos/first-look-at-googles-new-fuschia-os-in-action/
On Linux it is already displaying great potential and has seen adoption by the likes of IBM. That is pretty impressive as it is hard to get people to even consider other languages beyond Linux's core languages of C, C++, and Python.
What Linux needs now is a complete GUI environment built around Swift. This to address the buggy or behind the times solutions like GTK and QT. Linux is in the same position the Mac was before Apple bought the current operating system, they need a reboot and Swift could be the answer.
More iKnockoff garbage. I was hoping it was something new.
Why Apple still have not created a framework that use XHTML, JS, and CSS (like PhoneGap and Titanium) is a mystery. It would offer more stability, better protection, better compatibilty for the future and the past as well, and having the CSS would allow the apps to easily scale to resolutions without having to deal with bizarre constraints in Swift/Obj C++. In fact, I suspect if Apple just use pure XHTML, CSS, and JS, it would be a lot more efficient and more stable. Programming with Swift is hard... if you code that is missing out something important but it seems to compile fine and you run it, it literally crash hard. It takes only one simple error to make it go all wrong. It's no wonder that apps keep getting updates.
The combination of XHTML/JS/CSS cannot provide anything approaching the protection of any compiled, type-safe language. The only time that any error is caught in JavaScript is when the runtime trips over it. I remember a day spent tracking down a bug in an AngularJS app because someone had mistakenly dumped the wrong object into a list. Because the list wasn’t type-checked we had to figure observe usage for a few hours before we could narrow down the problem.
Oh, and your ‘suspicion’ that JS is more efficient than Swift is also wrong. Swift is compiled and optimised for the hardware it’s running on. JavaScript is optimised for running inside a browser, compiling as it goes. That browser is also running on top of an operating system, essentially doubling the layers of interaction between the user and the device.
I ‘suspect’ the problem is that you lack experience more than anything else.
My apologies. I just repeated your post.
Well, here’s something they didn’t copy from Apple:
https://qz.com/1131515/google-collects-android-users-locations-even-when-location-services-are-disabled/
the notion that they have a right to your data, even when you’ve asked them not to record it.