Binder is just C++ with a thin IPC compiler, more or less similar to any IPC idl. Could be sunrpc, but Google wanted a c++ wrapper.

But in any case this is completely irrelevant, because there is no such thing as a "userspace driver" (unless you're speaking about hurd or plan9). Drivers are by definition kernel-space code (which on Linux is either built into the kernel, or is a loadable kernel module). Those binder wrappers are just a convenience layer, underneath it's all still Linux, /dev/video0, v4l2, and so on.

All smartphone drivers would have to be rewritten for a different kernel.

In 99.9% of the cases it's completely enough.

When I discovered it, I was amazed, astonished, stunned, thrilled, and in disbelief.

It turns out that it actually works.

Comments URL: https://news.ycombinator.com/item?id=49151146

Points: 67

# Comments: 6

DMCA and other anti-circumvention regulations.

Because those 11 features mentioned in the OP post need to be unlocked.

The core issue is not "Google not allowing a feature", it's that small businesses cannot buy phones, install a patched version of Android without a restriction and sell them to make money.

Until this problem is solved, everything else is palliative.

Just as being able to play an instrument or dance or actually reading literature from other cultures, even in English.

yeah, I speak 4 languages fluently, and can get through more with a dictionary

>Imho monoculture is toward death, not toward something golden

Same language does not mean same culture. Singapore and USA both speak English, yet the cultures are different.

The same culture can be represented in different languages, as translators prove by their existence.