> Everything is split more explicitly, and there is no system wide hybrid type > that has to be compatible with whatever the backend is.
So, one cstring for `char*`, one for `std::string`, one for `NSString` and one for JS' `string`? That looks like an awful lot of string types.
