Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think at any point in time, the answer is the one that is a combination of the following (1) it makes the most sense to you, (2) it is maintainable/it is widely used (or has the potential to be, if you are willing to take the risk of something becoming quickly obsolete and impractical to maintain or impossible to find resources that will work on it), (3) it is simple, (4) it is flexible, and (5) it is potentially scalible.

There are a number of frameworks that meet those requirements now, including Rails. My point was that Rails has a real problem now in that it is a framework that fewer want to spend the time to learn, in my opinion and the opinion of others that make their living writing Rails apps. I see very smart people and people I work with (not necessarily, but sometimes mutually exclusive ;) ) promoting technology these days that doesn't fit the requirements I stated above for a framework/language/tool that will serve the test of time. That bothers me.

If you are really looking for a suggestion, I say go to the following URL and start comparing frameworks. This will at least help give some indication of usage. Then go to the forums, mailing lists, etc. and see whether things are getting more or less active over time: http://www.indeed.com/jobtrends



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: