ruediger

They could add support for GCC (MinGW) and ship it.

No APL code? I'm disappointed!

Can you elaborate on that? Why does Unicode suck for Japanese text?

> Also UTF-8 string can't be cut at arbitrary position.

Neither can be any other kind of Unicode string because of Combining Characters. That's why the Unicode standard (or an Annex) recommends algorithms for text segmentation.

(And if you really need to cut at a certain length then you can easily backtrack and find the beginning of the sequence by looking for the first byte with the MSB = 0)

The problem with start ups is that engineering is fun but business and administration is no fun. Nobody is enthusiastic about filling out tax forms and yelling at people because they are missing deadlines. People with experience in administration are rarely looking for a chaotic start up that can't pay a good salary.

Linux and *BSD have a fixed ABI for C++.

What about lwn.net?

Did you report that? It seems you should rather discuss that on the gcc mailinglists with the gcc developers.

I guess the reason for Google to start contributing to Clang and using it for their tools is the availability of the frontend. As far as I know the GCC developers made it extra hard to separate the frontend from the compiler because they feared that people would use it on proprietary backends. But this really left us in a situation were for decades people couldn't work on creating amazing static analysis, autocompletion, refactoring tools for C and C++. In the end this decision probably did more damage to the free software movement. GCC now comes with a plugin interface and with the Clang frontend available I hope that this will change quickly.

Why is the competition not-so-friendly? I believe GCC has already improved due to Clang at least a lot of the error message improvements in the last releases seem to be inspired by Clang and GCC has finally added Plugin support.