5 ms·

It's been a (very) long time since I worked in Android OS land but at the time I could see effects of them actively moving projects from GCC to Clang. I always

It's been a (very) long time since I worked in Android OS land but at the time I could see effects of them actively moving projects from GCC to Clang. I always picked up the outsider impression that it was their preferred C++ toolchain. First I've heard of them abandoning it

moloch-hai 4y ago
There is a big push for their proprietary language "Carbon". Clang is way behind on implementing most C++20 features.
- smoldesu 4y ago
  Well, let this be a lesson to anyone who tries competing with a GPL product. Permissive licenses are cool up until the moment a FAANG company embraces your project, extends it and extinguishes it.
- stusmall 4y ago
  That's an early stage, pre-production, experimental language. They are still a couple years out from a 1.0. They aren't moving away from clang for that anytime soon and they sure haven't abandoned clang for it. Also it isn't even proprietary[1] 1. https://github.com/carbon-language/carbon-lang/blob/trunk/LICENSE https://github.com/carbon-language/carbon-lang/blob/trunk/LI...
  - cyber_kinetist 4y ago
    Well, but I’ve heard that many of the Clang people from Google have switched their gears to work on Carbon, so that might be quite an issue for future Clang development (even if Carbon is in the early stages). I think the possibility is that the Google engineers will do bugfixes for up to C++17 features but will minimize work on catching up to the latest standards (since it really takes up too much engineering effort, and Google seems to be conservative in using newer C++ features anyway and have opinions that differ from the standards.)
- menaerus 4y ago
  > Clang is way behind on implementing most C++20 features. https://en.cppreference.com/w/cpp/compiler_support#cpp20 https://en.cppreference.com/w/cpp/compiler_support#cpp20 begs to differ. The heck, even C++23 core language support is almost fully done.

moloch-hai 4y ago

There is a big push for their proprietary language "Carbon". Clang is way behind on implementing most C++20 features.

smoldesu 4y ago
Well, let this be a lesson to anyone who tries competing with a GPL product. Permissive licenses are cool up until the moment a FAANG company embraces your project, extends it and extinguishes it.
stusmall 4y ago
That's an early stage, pre-production, experimental language. They are still a couple years out from a 1.0. They aren't moving away from clang for that anytime soon and they sure haven't abandoned clang for it. Also it isn't even proprietary[1] 1. https://github.com/carbon-language/carbon-lang/blob/trunk/LICENSE https://github.com/carbon-language/carbon-lang/blob/trunk/LI...
- cyber_kinetist 4y ago
  Well, but I’ve heard that many of the Clang people from Google have switched their gears to work on Carbon, so that might be quite an issue for future Clang development (even if Carbon is in the early stages). I think the possibility is that the Google engineers will do bugfixes for up to C++17 features but will minimize work on catching up to the latest standards (since it really takes up too much engineering effort, and Google seems to be conservative in using newer C++ features anyway and have opinions that differ from the standards.)
menaerus 4y ago
> Clang is way behind on implementing most C++20 features. https://en.cppreference.com/w/cpp/compiler_support#cpp20 https://en.cppreference.com/w/cpp/compiler_support#cpp20 begs to differ. The heck, even C++23 core language support is almost fully done.