2 ms·
> Documentation effort towards OSX would help vastly more people than similar efforts for any flavor of Linux, which nobody plus epsilon uses (except amongst de
by geofft 9y ago
> Documentation effort towards OSX would help vastly more people than similar efforts for any flavor of Linux, which nobody plus epsilon uses (except amongst devs).
Documentation effort towards Linux would help get that number up from nobody plus epsilon.
Also, at this point that's just not true because of Android. Most of the userspace is different from normal GNU/Linux distros, but not all: for instance, if your question is "how the heck am I supposed to connect to this WPA-Enterprise network," it's wpa_supplicant under the hood whether you're using Android's network dialog or GNOME's, and documenting wpa_supplicant's abilities and bugs helps Android users just as much as GNOME users.
- pjmlp 9y agoAndroid is only about Java. The NDK APIs are quite constrained and only meant to be used for Java native methods, real time audio and high performance graphics. Google can replace the kernel for anything else POSIX like, with the same set of NDK APIs. Since Android 7, they have been locking down access to anything else not part of the official NDK APIs.
- geofft 9y agoThat depends if you're talking about user docs or developer docs. I'm saying that we should document wpa_supplicant as user documentation: if there are caveats like, oh, "Android 5.1 and lower can't connect to TLSv1.2-only PEAP or EAP-TLS networks," that should be documented for end users but is irrelevant for devs since wpa_supplicant isn't accessible to the application at all. It's not a library/API, it's a system daemon. (But maybe I missed the point and we're specifically talking about developer documentation here?)
- pjmlp 9y agoI am speaking about developer documentation. As for user documentation, any OEM is free to do whatever they feel like, so you don't have any guarantee how much of it is actually like AOSP. Samsung is well known among Android devs for breaking AOSP compatibility.