Live data from Hacker News

Ask HN: Could the back-end language influence the success of a Web startup?

news.ycombinator.com

31–32 of 32 posts

Re: Ask HN: Could the back-end language influence the success of a Web startup?

#31
post #21

This is one of pg's theses about startups -- one that he bet heavily on when he became an investor. And the first essay that had a significant audience. http://www.paulgraham.com/avg.html I'm surprised that conventional wisdom has flipped at HN. Is C++ now considered just as good a language for web startups as Python or Ruby? Really? This feels quite eerie. I've felt the "decline of HN" posts were a bit overblown but…

I don't think you can attribute it to a "decline in HN", I think it's better attributed to the rise of a whole stack of languages, frameworks and software heavily optimized for web development, and the decline in hosting costs for any platform.

Today you can spin up an EC2 box for pennies an hour, even with Windows, and push a new build live or publish a new site just minutes later - very different to 16 years ago.

Re: Ask HN: Could the back-end language influence the success of a Web startup?

#32
I dont think languages differ most in prospects for success after you've reached functionally-complete-and-relatively-bug-free stage. The biggest difference is how do you get to this stage.

For a medium-to-big sized web application it would take you years to implement it in asm ;)

A language with a good web 'community' and great framework can be quite a big boost in getting your 1st version out to the users.

Also, many times, the choice is not so much between the tech but rather between the teams (i.e. when looking for outside help with development) in which case the tech matters less the people's ability to predictably hit the target on time and budget (talk to prior customers).

When doing internal development, if your team knows any web language well then thats what they should be using. On the other hand if the one they know is something like cold fusion I'd say - switch ;)

If you do switch, keep to the open source stack, linux, apache/nginx, mysql. Again, there are quite a few people advising postgre over mysql, but I'd say it depends on how your team knows them both. if you are new to db, then you might as well start with postgre, but if you already know mysql, stay with what you know.

Bottom line, stay with what you know unless what you know reeeally suck for web dev, in which case switch. I'd recommend Ruby on Rails, or if you allergic to Ruby - Djungo ;)

Post reply on HN