anon01

Version numbers are pretty useless these days. I would certainly put a lot more stock in a 1.0 from the Go team than, say, my company. We use version numbers more for marketing than anything else.

Personally, I'm not as worried about reliability as I am roadblocks. Say, for instance, we spend a month moving our framework over to Go. Then we find a problem that is yet unsolved. Either we solve it ourselves at an unknown cost or we have to just ... wait.. until another group solves it while we make payroll in other ways.

I'm lacking any real evidence here, maybe Go doesn't have a library for our Message Queue (not true, just an example). Now we aren't just porting, we're writing a pooling message queue interface that is beyond our pay grade in the language.

We've just started using Go as well. It smokes our Python app in terms of speed, and is fun to use (maybe just because it's new?).

I have always wondered, however, that if moving to a new language seems great because of the language, or because you have such a better understanding of the implementation of the problem you are trying to solve.

Yes, because PHP monoglots have their homepage set to codinghorror.com and browse right over to Hackernews afterwards. It is not a public service, it is a waste of screen space.

The startup scene's dirty little secret is that (anecdotal from several local companies I've worked for and/or collaborated with) PHP development is fast and cheap. Once you have proven you can solve a business problem and get funding, then you can decide if you really need to do a re-write.

There are just too many small companies focusing on real problems(instead of what language their webapp is built in) to make me think PHP is evil or that Rasmus Lerdorf is a bad person.

We have made our first two customers extremely happy with our late hours and endless customer support. We also spent so much time customizing our product for them, we've had to invest 6 man months(so far) trying to get back to a stable product, on one codebase, that works for them AND new customers without direct engineer involvement in each turn up... it has been a mess.

I think its interesting to see what kind of passwords were in there. "password" was of course in there, "password1" was not, "password2" was....

This is literally the most motivating thing that has happened to me in almost a year. Short, sweet, and describes my exact situation. I'm glad to hear it's not just me.

I get motivated when I am able to accomplish goals.

I get demotivated when the owners sell me on a pitch that they asked my advice on creating. When I tell the truth about our product's technical status, I am being difficult and not a team player. When I sugar coat things, I am yelled at when the product isn't what they hype it to be.

That is demotivation. Instead, just let smart people build your product.

What about the entrepreneurs who pay themselves ridiculous salaries once they get even a little funding? It seems like a great way to make money. Our founder is the highest paid person in the company and we live one month at a time because of it. Is this common during the bubble, or is my situation unique?

Highest paid is fact, one month at a time is opinion.

Agree. When I go out to start a company (I've started 3 failed companies) I went to my lawyer and accountant, a marketing person from the local business chamber, I asked their advice, and followed it.

For some reason the people on the business/finance end seem to think they can just delegate everything and know how everything works based on whatever they heard in the news. They already decided on using the cloud, thats the hard part! Actually using it is just implementation right?