how to deprecate an interfacepic.twitter.com/0bJlCNkrcq
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
NDK used to offer a choice between gnustl, STLport and a stub C++ standard library only providing a basic runtime. NDK supports libc++ now and gnustl / STLport are deprecated. STLport still had releases until after December 2008.
AOSP itself switched to libc++ in Lollipop (2014). It took until 2016 for them to make that a default / stable choice for third party apps: https://android-developers.googleblog.com/2017/09/introducing-android-native-development.html … It's the same NDK release deprecating GCC. Using libc++ was likely the plan ever since it came into existence.
They happily use the OpenJDK standard libraries as the basis for their own Java standard libraries now, and that's GPL2 with the classpath exception. The license plays into these choices but so does lack of openness to contributions of GNU projects (copyright assignment), etc.
GNU C++ standard library has had a lot of issues with Clang, just like glibc, and they aren't particularly interested in avoiding them. They've wanted to use Clang everywhere for a long time and they weren't going to make any choices leading to that being any more difficult.
OpenJDK didn't exist when they started (even before Google). If it had, they might not have taken the route of forking Apache Harmony which was pretty much in the same situation as STLport.
LGPL3 and GPL3 aren't compatible with their usage so there's no way any GNU project would be used now. They're also going to be a lot more reluctant to use any GPL2 or later project than they were before, since it could move to GPL3 unless they get assurances that it won't.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.