Conversation

#fuchsia design principle: Bring Your Own Runtime. If your code can speak the protocols, it can be a first-class citizen regardless of language or runtime. Consequence: Fuchsia does not provide libc or other shared system libraries. Each package is #hermetic and has its own libc.

365

Adam Barth

@adambarth

Jun 9, 2021

The system protocols are defined in #FIDL, the Fuchsia Interface Definition Language. The FIDL compiler has a backend for each language, and an IR that makes adding new languages easier. Any language can add support for Fuchsia using FIDL without needing to ask for permission.

Dimiter "malkia" Stanev

@__malkia__

Jun 9, 2021

Replying to

@adambarth

Is there any hope to see FIDL used outside of Fuchsia, on other platforms?

Replying to

Possibly. However, FIDL is tuned specifically for Fuchsia. For example, there are types for each Zircon object. There are other similar tools that might be more useful for other applications (e.g., gRPC, FlatBuffers, Cap'n Proto).

Replying to

and

As a similar example, Android has developer.android.com/guide/componen (AIDL) and the legacy HIDL. Android 12 is significantly adopting Rust and part of that involves it having an AIDL backend in addition to the ones for C++, Java and C: security.googleblog.com/2021/06/rustc-

Replying to

and

There's also somewhat related tooling for generating ABI definitions for C and C++ code to enforce ABI compatibility. source.android.com/devices/archit That stuff is designed in a way that it could easily be used elsewhere. It's not particularly Android specific and has simple tooling.

source.android.com

ABI Stability | Android Open Source Project

6:01 PM · Jun 9, 2021Twitter Web App