> Facebook levels of load would be a great problem to have. Until then, who cares? Good question, why did he bring it up? As others pointed out, it doesn't eve

> Facebook levels of load would be a great problem to have. Until then, who cares? Good question, why did he bring it up? As others pointed out, it doesn't even make sense: your data store is where you have to scale, not the language itself. > Doubtful, but this isn't even a good point. Working software is the important deliverable. Hmm. I thought the goal was working and maintainable software? > You missed the point. Writing a web app with a language that's basically tied to the web makes sense. It's not the most important point, but it isn't 'nonsense'. No, it makes sense to choose the most powerful language. A language that's "basically tied to the web" means that you can't use it to do other things when your business needs change. > He said as much in that point. No, he said that php makes it less easy to screw up, which is simply not true. What if, late at night, I call mysql_escape_string (because, hey, the name makes sense!) instead of mysql_real_escape_string? Type systems make it harder to screw up. Poorly named escape functions, ridiculous type coercion, and a gigantic global namespace do not. > Did you bother reading and thinking about the article, or just trip over your own drool racing to the comments section? I'm just going to stop here. They see me trollin', they hatin'.