Your entire argument is invalid.

"I don't think this is a reasonable demand for startups or even medium sized businesses."

It was a recommendation. Go is a great investment, and while it may not have a "huge" market share, many of the most influential tech company's in silicon valley are starting to use Go.

https://code.google.com/p/go-wiki/wiki/GoUsers

And some of these companies are even writing/rewriting their spotlight core projects with Go.

https://code.google.com/p/go-wiki/wiki/SuccessStories

"Libraries cost time and money to produce"

Time yes, Money no. Developers may charge money to produce software, however there are lots of software projects out there that were written by developers who worked for free. Does a painter always paint with the intention to sell his/her work at a gallery showing? Maybe they just want to create something for other people to experience.

I view all software from this perspective, and I give alot of my time working on go boilerplate libraries and other opensource projects for free because I want to help empower developers to create real world solutions to real world problems without the nuance of having to "invent the wheel before being able to engineer a new automobile".

"and if you are relying on free volunteers, development will either be slow or buggy and likely both."

Pass.

"I remember when I tried to look into a MySQL library last month. The first one I tried wouldn't even compile. The 2nd one threw a connection error not when I issued the dial function, but when I tried a query on a fake IP."

Have you tried reading
https://code.google.com/p/go-wiki/wiki/SQLDrivers,
or...
perhaps considering using one of these,
http://godoc.org/?q=sql

Maybe consider this which looks considerably up to date. https://github.com/go-sql-driver/mysql

Your experience last month with Go may very well be irrelevant now. Ive been using Go for about a year now, and many things have changed within go's development ecosystem within that time period.

If you arent willing/capable of contributing to go by committing code, thats perfectly fine. However, atleast make sure that your issues with the language are actually still relevant before you discourage other developers from exploring the language themselves.

"If you want Go to succeed"

As if its likely to fail? Go has already successfully satisfied the language designer's desires that motivated the project's creation. They want to create a language that makes their programming environment more enjoyable and efficient when developing software at a scale Google operates at.

Unless some language comes along that is exceptionally better at solving the problems Go was design to solve, Go will remain a successful programming language for those who use it.

"get Google to start funding it more"

Are you kidding me? Google has some of the most well respected engineers in computational history working full time on Go. Google cant just walk into best buy and hire geek squad to work on Go. We are trying to reduce go's overall source code complexity so that we can not only maintain the code, but ensure we dont introduce bad language design mechanics as apart of the programming environment. We want to avoid the situation, years down the road., where we are faced with having to make a decision to either cope with a bad language mechanic or deal with it by introducing backwards incompatible changes that break gopher's code. Both options suck, and the only good option is to avoid the situation entirely by making sure we make the best design choices.

"or get used to having it grow organically like every other language."

Most languages dont grow organically. Most either grow all mutated and exponentially complex to adapt to changes in technology, or development either slows down or stops growing completely because the majority developers who used the language, moved on to something .
Go on the other hand does grow organically, atleast it has so far.
Everyday the project matures and issues we are frustrated with right now could be a faux problem because its already been fixed in go tip and you just need to rebuild the compiler.

http://swtch.com/~rsc/go11.html

I mean sure there are alot of bugs to fix and alot more than can be done to improve go's performance, but this is true for all software in general.

The reason go is a good investment because it has alot of good investors investing in it.