I did my lonely venture in java. I think the main problem of java for startups is that it's uncool. They're trying to rationalize, but they are wrong, you avoi

I did my lonely venture in java. I think the main problem of java for startups is that it's uncool. They're trying to rationalize, but they are wrong, you avoid wearing a tie to express that you're not a number, I don't know why you wouldn't avoid java as a statement that you're not an IBM consultant. When I started my project, I tried ruby, but after 2 months of fighting, I just went back to java. But somehow I'm gifted, I never did java at bigco, I did it at another (desktop) startup before and have a critical eye on the java current trends. I don't use Spring and all the famous bigco frameworks, I use a simple setup (PicoStuff, jetty, Webworks). But in think most "objective arguments agains java in a startup" are plain wrong. The real problem of java is that all people know about it is eclipse and spring and the EJB2. edit: BTW, today I do PHP, and we're integrating with drupal, and what I see in drupal is far worse than the EJB spec. It's tangled and static so you can't test anything in isolation, and there is no spec. The core code is really difficult to read because everything is passing maps of string around.