11–20 of 28 posts
Django is also a fine choice but Django lacks learning resources. I mean seriously, why aren't you Django guys writing books and recording screencasts?
On the other hand, I recently learned that Perl is making a comeback with a couple of popular web frameworks. I haven't programmed in Perl since the last century, but I remember it being a fun language!
Basecamp and Harvest were both written in Rails. For standing up simple SaaS, Rails is a great choice. However, for a complex SaaS (any SaaS can get here really), you will need to make some sane choices around modularity and building separate, loosely coupled services before things get out of hand. Node.js (or any of its lightweight frameworks on top) is probably a little stronger than Rails in this regard. This serv…
Huh? This is a load of crap. Frameworks, and even languages, have nothing to do with modularity and building services. You can do this in any language and any framework. Modularity and loose coupling are decided by the developer(s) writing the code and if you think a particular tool will solve this for you then you have a grave future.
JavaScript is most future-proof. Given that it runs in browsers, servers (Node.js) and mobiles (PhoneGap) I strongly suggest learning the Node ways, as you may find yourself using Backbone/Angular/etc on the client and in-depth knowledge of JS will help. In this day and age you're probably building a single page web app, in which case 99% of your code will run in the browser.
What does "future-proof" even mean in this context?
> In this day and age you're probably building a single page web app
Uh.. no. A tiny percentage of new web applications are single page applications and of those most of them don't need to be single page applications. The web would be a much better place if people thought in terms of "What functionality does this web application need?" instead of "Does this application need to be a single page application?"
Basecamp and Harvest were both written in Rails. For standing up simple SaaS, Rails is a great choice. However, for a complex SaaS (any SaaS can get here really), you will need to make some sane choices around modularity and building separate, loosely coupled services before things get out of hand. Node.js (or any of its lightweight frameworks on top) is probably a little stronger than Rails in this regard. This serv…
> However, for a complex SaaS (any SaaS can get here really), you will need to make some sane choices around modularity and building separate, loosely coupled services before things get out of hand. Node.js (or any of its lightweight frameworks on top) is probably a little stronger than Rails in this regard. Huh? This is a load of crap. Frameworks, and even languages, have nothing to do with modularity and building s…
Earlier quoted context omitted.
> However, for a complex SaaS (any SaaS can get here really), you will need to make some sane choices around modularity and building separate, loosely coupled services before things get out of hand. Node.js (or any of its lightweight frameworks on top) is probably a little stronger than Rails in this regard. Huh? This is a load of crap. Frameworks, and even languages, have nothing to do with modularity and building s…
I don't think it's right for you to call what he said crap without backing it up with any evidence. Node.js is essentially the modern poster child of modularity. JavaScript doesn't have inherent modularity--but the devs of Node have made some choices that make it possible to have an extensive module ecosystem for Node. npm is probably one of the best package managers for development right now, as it comes with one of…
Again, modularity has nothing to do with the quality of your package manager.
We see questions like this on HN quite often. When starting a new project that you would like to support yourself on, you must ask "Would I like to make a successful SaaS product?" or "Would I like to learn a new language/framework/ecosystem?". I am sure some would argue that the language/framework/ecosystem can really make or break a web application. However, there are successful business built on just about all of them:
Stackoverflow - .Net
Facebook - PHP
Amazon - Java
Bloomberg - Ruby (could have said Twitter until recently they are migrating to Java, interesting?)
Reddit - Python
DuckDuckGo - Perl
Orbitz - Lisp
OkCupid - C++
Of course many of these organizations use a number of languages and frameworks. The point is, when they started they used what they knew and went with it. My suggestion, start building! Then someday I can use your super successful application in a list like this!
[1] https://news.ycombinator.com/item?id=8677556 [2] http://www.teamten.com/lawrence/writings/java-for-everything...
And then invent your own because they're all crap.
Please, invent one that doesn't suck. I'm sick of web development sucking so hard.
And then invent your own because they're all crap.
Please, invent one that doesn't suck. I'm sick of web development sucking so hard.