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
The edition for this week covers some technical, development aspects of Fuschia with an emphasis on the Dart language, one of 3 used by Google for the development purposes of their creation. What I find interesting here is that so far, no mention of the Go Language. It sounds like a subject for another episode as I find it hard to believe Go won’t play a huge part in Fuschia, which IMO is designed to be Android without ties to Java, therefore Oracle [successor to Sun Microsystems].
With the significant news this week that the Fuchsia SDK and a Fuchsia “device” are being added to the Android Open Source Project, now seems like a good time to learn more about the Fuchsia SDK.
The curious can find a download at the bottom of this article, but I obviously don’t recommend its usage for any major projects as it will swiftly become outdated and/or outright wrong. The tools in the included version are designed for use with 64-bit Linux, so if you’re on OS X, you’re on your own.
Not mentioned in the article means you are also on your own regarding Windows.
via Fuschia Friday SDK edition.