Ask HN:Help for server side options. I know only .net

#1

Post by vaib » Sun, Jul 24, 2011, 8:40 PM UTC

Hi all,

Myself and my friend have been discussing an idea for some time now. It involves location based social networking not very different from Foursquare. My friend is a mobile developer and I am a .Net developer at work. These are exciting times with Node.js out. I am also pretty proficient with all client side technologies like html5, css and javascript.

Though I only know asp.net as server side technology but we both can really take up any technology.

We'd like to get suggestions on what to use on server side - Php, .net, java\scala, ROR, node.

What do you think we should be using on server side? Please suggest. We'd like to start soon.

Thanking in anticipation.

Re: Ask HN:Help for server side options. I know only .net

#2

Post by dbuthay » Sun, Jul 24, 2011, 9:24 PM UTC

I'd go for ROR, or maybe Sinatra + your favorite ORM.

If you don't want to host your own servers, you can grab an ec2 free micro instance, or just go with heroku or cloudfoundry.

Re: Ask HN:Help for server side options. I know only .net

#3

Post by trussi » Sun, Jul 24, 2011, 9:49 PM UTC

You want to build your MVP as fast as humanly possible.

If you already know .Net, so go with .Net. You don't have time to learn a new language.

Don't get swept away with the romance of a new language. .Net is a proven technology. It will be able to do whatever you need it to do.

And between DreamSpark and BizSpark, there's no licensing costs.

Re: Ask HN:Help for server side options. I know only .net

#4

Post by angryasian » Sun, Jul 24, 2011, 10:31 PM UTC

trussi wrote: post #3

You want to build your MVP as fast as humanly possible. If you already know .Net, so go with .Net. You don't have time to learn a new language. Don't get swept away with the romance of a new language. .Net is a proven technology. It will be able to do whatever you need it to do. And between DreamSpark and BizSpark, there's no licensing costs.

agree, just build something and get it out. The problem is you can spend months learning something or figuring out a new language and in the end it fails miserably. So what did you spend all that time for. Build it on .NET, and then when you have real usage figure out the details then.