4 ms·
Heh... I just realized I have no idea what any other Triangle area startups are building in. And more to the point, I don't really care. I mean, if I met anoth
by mindcrime 12y ago
Heh... I just realized I have no idea what any other Triangle area startups are building in. And more to the point, I don't really care. I mean, if I met another startup founder at an event or something, the question "what is your tech stack?" would be pretty near the bottom of the list of things I'd ask. I actually can't even think of a reason I'd want to know.
I'll go back to what Steve Blank and others have said: most startups that fail (and most do), fail because they build a product nobody wants, not because of technical problems with the product. If you believe that is true (and I do), the tech stack really just isn't a very important decision at all. And I think that's especially true if you stick to anything even remotely close to mainstream: Node, Rails, Grails, Django, Flask/Pyramid/Pylons/Whatever-it's-called-now, Scala+Play, Java+Spring MVC, Whatever-Clojure-uses, etc.
Now, if you said you were building using Algol-68, SNOBOL, RPG/400 or MUMPS, then there might be a legitimate question regarding your ability to find and hire good developers, etc. But I'd still almost be willing to bet that "building a product nobody wants" would be more likely to be the culprit if the company failed, than the tech choice.
That said, we use Groovy and Grails here. Node is on my list of "things to play around with when I have some free time" but nothing I've heard yet gives me any reason to think that it's a "game changer". Feel free to convince me otherwise though.
- notduncansmith 12y agoI've worked quite extensively with Node, and I'd hesitate to call it a "game changer". The game has not changed - there's nothing about Node.js that fundamentally alters the way people build web servers. I mean yes, there's the whole async thing (nothing new), but that's really only in pursuit of performance, and Go (way more performant) will catch up to Node's library selection within a few years. All that said, I quite enjoy working with it: I find Javascript pleasant, and it's easy to create elegant solutions to the problems I encounter day to day. Finally, Node powers some absolutely fantastic front-end tooling (Bower, LESS, Gulp). Even if it's not powering your sever, I recommend it as part of the front-end workflow.
- callmeed 12y agoThanks for the input. If there was a web framework for Ada, I'd be all over that ;)
- vorg 12y ago> anything even remotely close to mainstream: Node, Rails, Grails, Django, Flask/Pyramid/Pylons/Whatever-it's-called-now, Scala+Play, Java+Spring MVC, Whatever-Clojure-uses, etc The etc covers Go based servers nowadays. PHP backends are still fairly common, and maybe even Perl 5 is still used.
- deleted 12y ago[deleted]