Can someone familiar with the Android ecosystem elaborate on what exactly this means? Does it mean you get rustc automatically when you download the Android SDK? Does it imply any particular level of support? How many other languages have this status?
> Can someone familiar with the Android ecosystem elaborate on what exactly this means?
It means that Google is experimenting with using Rust to build parts of Android. That could mean parts of the OS, tests, tools, SDK, etc...
As a simple example of why this isn't necessarily super interesting is Python has been in the Android tree for ages, but just for some build & test stuff.
But maybe it's interesting just in that the Google engineers working on Android have started playing with Rust enough to bother checking it in to the tree.
One reason I find this interesting however is that fuchsia, a potential replacement for Android being worked on at google (that's an aggressive oversimplification) is partially written in Rust. So this potentially opens up using parts of fuchsia.
Does anyone here have experience on using Rust for shared business logic between Android and iOS? It's something I'm considering but it seems there isn't a lot of documentation around it.
This happens a lot on hackernews, and frankly it's really annoying. People post a link to some random thing like this, and it gets upvoted because people don't click on the link, they just are excited about the title. A lot of times, the title doesn't even mean anything. Hackernews != Twitter.
HN could reduce (but not prevent) upvoting of unread articles by removing the upvote button from the HN home page (so you can only vote after having opened the HN thread page and seen some comments) and/or requiring the user to click the article link before the upvote button appears (so the user might have read the article before voting).
I've always taken it for granted that the voting system is essentially meaningless, especially for comments, so don't generally use it (I'll downvote egregiously rude or idiotic comments, but that's it).
It's been something like 3 years since I've worked in AOSP but IIRC mingw is for windows builds of adb. Someone else called out that AVR stuff is for ADK. The Android build tree is more than Android itself. It also builds includes a lot of the supporting tools and libraries for developers.
FWIW things may not actually be used anymore, doesn't mean the repo is ever taken down. Usually the manifests that sync these repo's simply "unhook" the repos when they're no longer in use. OP is excited that there's a bunch of links, but that's not the correct measure of "in use."
