So I guess the (currently third place) "Other" is mostly PHP? I know it's not cool but it still seems strange to leave that popular and frequently used platform out of the poll.
If you were building a startup today, what would you use?
11–20 of 61 posts
Re: If you were building a startup today, what would you use?
#12If I were to start my career from scratch in 2014 I'd pick F#, and keep an eye out for Rust.
Re: If you were building a startup today, what would you use?
#13I'm surprised that iOS is winning out as much as it is on the first native side to build.
Re: If you were building a startup today, what would you use?
#14I'm surprised that iOS is winning out as much as it is on the first native side to build.
Objective-C is not a language option, but maybe because it's not a backend language? If iOS/Objective-C people voted for C++, they only have 3% now. So ~25% people want a fantasy iOS app but only 3% know native iOS = Objective-C?
16% of people think Javascript is a backend language? Hope those are votes for Node.js?
Re: If you were building a startup today, what would you use?
#15I'm surprised that iOS is winning out as much as it is on the first native side to build.
I'm surprised that it isn't winning by a larger margin.
Re: If you were building a startup today, what would you use?
#16I am most surprised by the number of people who want to use Go. It isn't that Go isn't a great piece of technology but I thought it would be really difficult to hire for and seems a bit overkill for an MVP.
That said, Rails, or any language developers are more familiar with, can be faster. At that point, I'd argue even static HTML pages might be one of the fastest MVPs to put together...
Re: If you were building a startup today, what would you use?
#17Seriously, I switched all of our development from Java/Tapestry/etc. to Groovy/Grails a few years ago, and really couldn't be happier with the decision. Grails isn't flawless, but it mostly "just works" and makes my life SO much easier than before.
No, it isn't the "flavor of the day" like node.js or what-have-you, but it works, it stays out of the way, and gets the job done. And it lets me leverage the decade plus of experience doing Java that I previously experienced. What more could you ask for?
Re: If you were building a startup today, what would you use?
#18Man, Grails / Groovy never get any love from these poll authors! C'mon, Grails rocks people... :-) Seriously, I switched all of our development from Java/Tapestry/etc. to Groovy/Grails a few years ago, and really couldn't be happier with the decision. Grails isn't flawless, but it mostly "just works" and makes my life SO much easier than before. No, it isn't the "flavor of the day" like node.js or what-have-you, but…
Re: If you were building a startup today, what would you use?
#19results: https://docs.google.com/forms/d/1fKVsAFT3nRVvlcJ74p0ZI2uqwDq...
tabulated results https://docs.google.com/spreadsheet/ccc?key=0ApqmTkgH6Ua_dEZ...
Re: If you were building a startup today, what would you use?
#20Earlier quoted context omitted.
I'm surprised that it isn't winning by a larger margin.
Why is that? My motivation for picking Android is the larger market share. Even if you have engineering preferences, to me what really matters is getting it out in front of a wider audience.
What device levels are you trying to get in front of?
Android seems like a "no brainer" until you start looking at the details... For example, if you cut out all "cheap shit 2.2 android devices" and focus on new(ish) Android 4.0> things get REALLY murky... In the US iOS still holds a lead over Android in those markets; in Europe Android is ahead, but then you have localization to deal with.
Additionally, Android might have an edge in some markets, but the fact that iOS users actually PAY for apps also makes a big difference.
The point is that Android is a sensible choice but it's not an automagic choice, nor is it as cut and dry as it appears.