I've heard many times at all sorts of conferences that locales are
broken, that developers write their implementations without locales, and
that using std::locale now is an outdated practice. In this regard, I
have a few questions about it.

1. What exactly is wrong with locales? Can you just give me link to some article
or paper with explanation about it.

2. In that regard, is everything okay with all kinds of std::streambuf
and std::stream? Suppose I write a new library that supports c++11 and
later. Should I support streams interface (which implicitly uses locales
(or I can reimplement whis??)) or is it better to imlement any different
interface for I/O operations? I mean, doesn't SG16 do things that will
replace std::codecvt. Maybe there is more modern way to support I/O.

3. Is it ok for new code to have I/O classes derived from basic_ios?
More specifically, I want to make some wrap on C library with it's own
I/O, which is quite similar to linux api (read, write, getch, etc). Is
stream interface still common for that?

Thanks for the explanation, and sorry if this is off-topic.


Daniil Rozanov