Finally, some added guidance of the Fuschia project that may ultimately replace Android as Google’s mobile platform.
This document describes which programming languages the Fuchsia project uses and supports for production software on the target device, both within the Fuchsia Platform Source Tree and for end-developers building for Fuchsia outside the Fuchsia Source Platform Tree. The policy does not apply to (a) developer tooling, either on target or host devices, or (b) software on the target device that is not executed in normal, end-user operation of the device. For example, this policy does not apply to zxdb (a debugger) because zxdb is a developer tool; the policy does apply to pkgfs because pkgfs (a file system) executes in the normal, end-user operation of the device.Fuchsia Programming Language Policy
Source: Fuchsia – Fuchsia Programming Language Policy
Yesterday, on the 9to5Google Alphabet Scoop podcast, our Stephen Hall dropped a mini bombshell that a Fuchsia tablet is rumored to be in the works. We dug in a bit deeper and found that the truth may be more complicated than that.
Early this year, it was discovered that the first Chrome OS tablet with Qi wireless charging was being developed under the codename “Flapjack.” Fast forward to today, it appears Chrome OS won’t be the only operating system this device supports, as Google’s Fuchsia OS team is also looking to support the “Flapjack” tablet…
Source: Google’s Fuchsia to support Chrome OS tablet ‘Flapjack’ – 9to5Google
Not frequent enough for my tastes, but it looks like Fuchsia is near the point of being the official successor of Android. And more importantly from Google’s point of view is direct control, unlike Android which is open source. Here’s hoping for more consistent news on that front.
This may be related to this announcement and article on ZDNet.
Over the past two years, we’ve closely followed the development of Google’s Fuchsia OS and the various hardware products it supports. Thus far, these products have almost all been Made by Google devices like the Pixelbook and Nest Hub, used simply as testbeds for Fuchsia on various form factors. But if Fuchsia is to ever succeed, Google will need to partner with other companies on developing their own Fuchsia-based hardware and software projects.
This week in Fuchsia Friday, we take a look at the various Google partners that have looked into Fuchsia OS, including familiar names like Samsung and Sony.
Samsung and other Google partners show interest in Fuchsia – 9to5Google https://ift.tt/31dw877 via Tumblr and IFTTT
New evidence has come to light indicating that the Fuchsia team is working to support the Snapdragon 835 processor, found in phones like the Google Pixel 2.
Source: Fuchsia adds official Snapdragon 835 support – 9to5Google
I know, it’s been a while. However, Fuschia is still very much in the development cycle as it’s not directly derivative of any other OS currently out there that I am aware of.
Courtesy of Kyle Bradshaw, 9to5Google.com
I have always said that Fuschia is Android without Java and thus free from licensing issues associated with it from Oracle, the successor to Sun Microsystems. Also modern and updatable on Google’s cadence.
It’s no coincidence that Fuchsia & Chrome OS share features like Android apps. The Fuchsia team is using some Chrome OS developments for their own benefit.
Source: Fuchsia Friday: Fuchsia’s close relationship w/ Chrome OS – 9to5Google
Courtesy of Kyle Bradshaw, 9to5Google.com
Could it be that Google has a different way of presenting Alpha code as usable? This activity is analogous to what got Microsoft in trouble during their Computer World Domination period. I. E. use the public as unpaid Beta testers at best, and sometimes Alpha.
Fuschia continues to be an interesting product and will, I think, be Google’s answer to the One OS holy grail that all of the platform vendors want to get to, Microsoft being the closest or further along on that path.
Fuchsia, Google’s in-development OS for anything and everything, has marched on toward its latest milestone—the first “release candidate.”
Source: Why did the Fuchsia OS team build a ‘release candidate’? – 9to5Google
Granted, my ongoing interest is a mobile platform not tied to any legacy system, unlike Android (Java) or iOS (Objective-C); this proves how difficult to design a modern OS and make it all work. Sometimes it may be better not to re-invent the wheel here, but what do I know?
Earlier this week, we reported that just about everything we’ve seen about Fuchsia is now gone, as the “Armadillo” UI has been deleted. In its place, we only have references to what seems, in context, to be three other “shells” or user interfaces which are all kept closed-source by Google. However, one of these, “Dragonglass,” may offer more answers than we initially thought.
Source: Fuchsia Friday: The mystery of Dragonglass in Android, Chromium, and Fuchsia – 9to5Google