Because fat std is rigid, impractical, and annoying.
replyIn practice (e.g. Go) it’s actually pretty good and infinitely preferable to third party everything.
replyYeah, it's annoying to have good support for dates in Java since 2014, instead of only getting it now like in JS.
replyI think we found the constituency that led to the present sorry situation.
replyThat's rather rude.
replyIf you're referring to my packages on npm, I joined way late to that game. This was also ~15 years ago.
Works just fine in Go.
replyFat std library mistakes/warts would likely result in third party packages being used anyway.
replyNot necessarily, but let's agree that some design faults would happen: you still get the option to use the solid, boring and slightly rusty std instead of another 100 dependencies from the supply chain supermarket.
replyAt work, we're happy with Python's included batteries when we need to make scripts instead of large programs.
So it provides another option, and in worst case it doesn't make situation worse than it is right now?
replyYeah, pretty bad idea.