News for hackers. Stuff that matters.
Re:A man, a Plan. No canals (2011) by PaulHoule on Wednesday January 09, 2013 @11:01AM (#5032139)
A big reason why PHP was as successful as it was is that it came with a fairly complete and correct standard library for writing webapps.

This way you could spend zero time writing your own urlencode function (and screw up a corner case) or searching through maven to find functions to do very simple things and finding later other people on your team imported similar functions from four other projects.

Re:A man, a Plan. No canals (2011) by guard-of-terra on Wednesday January 09, 2013 @11:11AM (#5032178)
"with a fairly complete and correct library for writing webapps"

Some of which were dangerous and unwieldy actually. Then proven dangerous and unwieldy. And then most of things that made idiomatic PHP were removed from the language or discouraged and nobody writes that way anymore.

Re:A man, a Plan. No canals (2011) by graysnorf on Wednesday January 09, 2013 @11:22AM (#5032247)
Suggesting that, at least for language adoption, a standard library that is "good enough" is sufficient, and can be fixed later.
Re:A man, a Plan. No canals (2011) by dllthomas on Wednesday January 09, 2013 @02:04PM (#5032817)
This probably depends on the environment (including alternatives) at the time.
Re:A man, a Plan. No canals (2011) by agumonkey on Wednesday January 09, 2013 @02:00PM (#5032798)
It didn't matter, the reference frame was aligned with php for most things, it seems to me that it was more "valuable" to have bad glue between curl, mysql, foo, than have a good linguistic substrate and good stdlib.