Sometimes it is quicker to write the exact thing you need rather than struggling with something that wants you to think it is the solution to your problem.
Another case in point was the Aha! moment someone described when realized that the Lisp Postgress interface was not going against the library but against the wire protocol itself. Just as easy.
But I agree. It's a matter of deciding when it matters, and when it doesn't.
In these cases it's to your advantage to use the mainstream tools because there are so many resources available to you.
Libraries tend to be generic, so you can often do better for your specific problem if you are willing to pay the opportunity cost.
I thought GPL libs could be used n a web based project? PG's article says (emphasis mine)
"One of the reasons to use Lisp in writing Web-based applications .. "
(Also, what is with all the anti-GPL FUD on this site? Have any of you guys read the license, or do you just like to bash it because you don't like Free Software?)
"When you're writing software that is only going to run on your own servers, you can use whatever language you want."
If you're not distributing software then the GPL doesn't apply. A web-based start up can use as many GPL-based libraries as they want.
I'm not saying you should write everything yourself, just the bits that matter :)