Yeah, but I will take a not great library that works everywhere the compiler does, than be at the whims of which platforms are supported by 3rd party libraries.
replyI can use most of the clunky Python, Java, .NET and if it must be, Go, standard libraries, than hunting down for dependencies with platform tier support and such.
Add more and more to a standard library, and you're going to start losing your "works everywhere".
replyPlatform support is a non-issue for every library being discussed. This is an array construction macro, it has nothing to do with what operating system you're running on.
replyJust because some trees have a specific trait, it doesn't mean the whole forest is the same.
replywhich, as painful as it may be, is ok. Better to have a safe functional stdlib library than a exposed external crate (which then asks the question; what's the replacement...)
replyThose aren't the only two choices.
replyWe also have the classic example of PHP with numerous not safe stdlib ways to use mysql.
To me the answer is still to vendor your dependencies and don't be on the bleeding edge of updates unless you're willing to invest the time into validating them.
> We also have the classic example of PHP with numerous not safe stdlib ways to use mysql.
replyI think it goes without saying that emulating PHP is rarely a good decision.
Which isn't actually a problem. You can ignore the bad standard library and use something different.
reply