4 ms·
which, 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 r
by rirze 1mo ago
which, 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...)
- lesuorac 1mo agoThose aren't the only two choices. We 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.
- kergonath 1mo ago> We also have the classic example of PHP with numerous not safe stdlib ways to use mysql. I think it goes without saying that emulating PHP is rarely a good decision.
- VorpalWay 1mo agoDon't forget C++ where large parts of the standard library are unusable (regex is slow and unfixable) or soft deprecated (dont use iostreams for formatting, use std::format, etc). No, I prefer what rust is doing. It suits a system programming language. Which is what Rust is.
- pjmlp 1mo agoRegex does the job for most business software, iostreams is alright, using them since 1993, std::format is cool provided one has control over their compiler version,...
- VorpalWay 1mo agoRegex is absolutely not suitable for most use cases that I have come across. Iostreams formatting is awful, especially if you care about internationalization (which is very common). Not sure what the issue with std::format would be here, you would have to elaborate. Obviously you need to specify a minimum version to have support for it at all.
- pjmlp 1mo agoIt works good enough for stuff I would be using Java or .NET for. Not every application requires internationalisation, especially server code or internal company tools.