4 ms·
None of the things you mention really need to be in stdlib. There are plenty of awesome options, and the great thing is, they all have their own pros/cons and y
by ioquatix 8y ago
None of the things you mention really need to be in stdlib. There are plenty of awesome options, and the great thing is, they all have their own pros/cons and you can choose depending on your requirements.
The point of C++ is to avoid burdening you with costs you don't want to incur. Putting this stuff in stdlib is exactly that.
If you could focus on modules and package management that didn't suck, would you still argue that you need to have JSON and high level sockets in stdlib?
- Waterluvian 8y agoCan you help me understand your concern? I'm not a c++ person. Is it that there's more stuff that needs to be packaged in even if it's not being used?
- stochastic_monk 8y agoI don’t think C++’s “Pay for what you use” applies here. You don’t have to use something just because it’s in the standard library. The only practical difference for a user is a larger binary when statically linking. (The burden on compiler developers is a very real concern, however.)