For what little it's worth, Stadia is opening to play through Safari (on iOS) soon.

Until just this week, Chrome OS's Instant Tethering was exclusive to Google's Pixel and Nexus phones, and was clearly advertised as such. Even now, the feature is only available for a small selection of phones (relative to the vast number of Androids in the wild).

Just use your phone's hotspot feature. The amount of time saving between using your native tethering vs Instant Tethering is negligible.

The instant tethering function actually doesn't use Bluetooth, except to set things up. If you pay attention, you'll notice the phone disconnecting from any WiFi network it might be connected to.

You can write software for Fuchsia without using Flutter, but Flutter is the most friendly way at present.

In a basic sense, Flutter is based in Dart, but if you want to call into another language like Swift, there is a way to do so, called FIDL. I'm not sure if Swift has FIDL bindings yet, but I'm sure that it and many other languages will, in time.

Even today Flutter has support for Swift code on iOS the same way it supports ObjC, via MethodChannels. (This is also true for Java and Kotlin code on Android.)

Have you encountered Julia, and if so, what did you think of it?

Can't say as I have. My expertise centers around Flutter and Fuchsia, for now.

Thanks for your support.

I'll trust code over an anonymous comment any day. But maybe I'm biased. If you see speculation in a Fuchsia Friday article that you disagree with, I'm always open to intelligent discussion.

Fuschia Friday is no doubt the most comprehensive Fuschia coverage on planet right now.

I started on this path recently with email by using the Astro app, and only getting notifications for "Priority Emails" which are intelligently chosen.

Inbox by Gmail does this, too. It's fantastic.

My understanding is that Fuchsia will have a stable ABI to avoid the driver issues of Android/Linux. That's not an answer to open source drivers of course. That falls on the OEMs.

I'm not sure why Escher started in a separate repo (possibly to make testing on Linux easier), but it's been moved to its rightful place inside of the Garnet repo.

Great questions. Specifically for #2 it's hard to say at this point. At present (in it's very early state), I believe they just pick the first result. But the resolution process returns a "confidence" value. This is purely my speculation and I need evidence before I publish it in an article, but I believe that confidence here indicates the intent to use ML.

It can probably be assumed that you would be able to set a preference for one module over another, but I haven't found any proof of that yet.

Author here. Manual installation will certainly always be possible. The instant/cloud parts of this feature are designed so that things can "just work" under optimal network conditions. Suboptimal and offline conditions are always to be expected and planned for. This is shown by Ledger's offline-first design.