7 ms·

1) I swear only to convey emotion. I feel it helps my message, but I realize that other people do not feel that way. I respect your opinion. 2) The team working

1) I swear only to convey emotion. I feel it helps my message, but I realize that other people do not feel that way. I respect your opinion. 2) The team working on it is too closed. They need dedicated people to clean up the "mess" left behind, to act as a kind of a Gatekeeper between core and community. 3) If you're in the Rails community it should be you who is scratching "the itch". Contribute 15 minutes of time a week to doing something beneficial to the community. Personally, I've taken to keeping a list of all the people I've helped and I'm going to put them on my wall as sort of an "achievement tracker" in the form of sticky notes. These are the people who's development lives I have added to, and this is one way I can silently thank them for using Rails. 4) Rails community is still "exploding" and I think with the release and associated press (read: circlejerking) there will be a lot more newcomers to Rails. To your final, unnumbered point: I disagree. There are still quite a few large sites that are using Rails and if "the world" had moved on, wouldn't have these sites also? I will not deny there being decent competition with Rails. There definitely is "solutions" that do it as well or (and this is something you won't hear a Ruby guy saying often, so please enjoy it whilst it lasts) better than Rails. Django, for instance, I hear is getting more popular and some people are jumping ship from Rails to it. Rails will, for the (slightly biased) foreseeable future, will still be a "big player" in the web-application world.

jimmyjames 16y ago
Rails has been "exploding" for years now, but it's still absolutely nowhere to be found in most job boards, so for all intents and purposes, it is a niche. I'm glad to see it grow because it contains a lot of very interesting ideas, but at this point, it's pretty clear that it will never become as popular as other "web frameworks" (using the term loosely here) such as PHP, ASP.net or some of the many Java frameworks...
- DanielRibeiro 16y ago
  If you believe Hiring is Obsolete (http://www.paulgraham.com/hiring.html http://www.paulgraham.com/hiring.html), then the jobs argument is pointless. If you don't, then you can always remember the Python Paradox (http://www.paulgraham.com/pypar.html http://www.paulgraham.com/pypar.html) the language to learn, if you want to get a good job, is a language that people don't learn merely to get a job.
- danieldon 16y ago
  it's still absolutely nowhere to be found in most job boards Strange, considering there are always Rails jobs on craigslist in every major city and on all startup boards. Hell, I don't even actively seek out contract work and have offers on a weekly basis (in person, not even counting online) from people looking for Ruby/Python web development. PHP, ASP.net or some of the many Java frameworks... So? You put stock in argumentum ad populum? Hell, why not rip on Django while you're at it, considering there are far fewer Django jobs than Rails jobs? Nevermind the fact that despite Python and Ruby web frameworks being less widely used than PHP overall they are still very strongly represented among the most successful and innovative web projects of the past decade.
  - jimmyjames 16y ago
    <shrug> Feel free to use whatever metric makes you feel good, all I'm saying is that the number of jobs for Java, PHP, Javascript and ASP.net (yes, even Basic) absolutely dwarfs those for Ruby on Rails.
    - ahlatimer 16y ago
      So, by lumping together four (or five) different platforms, you manage to come up with a number that is larger than those using Rails? That's not entirely surprising. You're also counting Javascript, which I find odd. Javascript is used in ALL of those platforms, so including it in an argument is extremely unfair. I do some Javascript programming from time to time, but I also spend a fair amount of time in Rails. When I was doing PHP and ASP.net programming, we were also using Javascript. So, yeah, there are going to be more jobs for front-end developers than those who program in some back-end platform, because all sites need some sort of a front-end (excluding some project that's purely an API). There's also a dilution of programming jobs for the aforementioned platforms, from my experience. Finding a job doing Rails seems to be fairly easy as, even though it was the "next big thing", the average programmer felt better sticking with Java, PHP, or ASP.net. There are way more Java programmers than there are Rails programmers, but it seems the ratio of programmers to programming jobs seems to be more in the favor of Rails.

jimmyjames 16y ago

Rails has been "exploding" for years now, but it's still absolutely nowhere to be found in most job boards, so for all intents and purposes, it is a niche. I'm glad to see it grow because it contains a lot of very interesting ideas, but at this point, it's pretty clear that it will never become as popular as other "web frameworks" (using the term loosely here) such as PHP, ASP.net or some of the many Java frameworks...

DanielRibeiro 16y ago
If you believe Hiring is Obsolete (http://www.paulgraham.com/hiring.html http://www.paulgraham.com/hiring.html), then the jobs argument is pointless. If you don't, then you can always remember the Python Paradox (http://www.paulgraham.com/pypar.html http://www.paulgraham.com/pypar.html) the language to learn, if you want to get a good job, is a language that people don't learn merely to get a job.
danieldon 16y ago
it's still absolutely nowhere to be found in most job boards Strange, considering there are always Rails jobs on craigslist in every major city and on all startup boards. Hell, I don't even actively seek out contract work and have offers on a weekly basis (in person, not even counting online) from people looking for Ruby/Python web development. PHP, ASP.net or some of the many Java frameworks... So? You put stock in argumentum ad populum? Hell, why not rip on Django while you're at it, considering there are far fewer Django jobs than Rails jobs? Nevermind the fact that despite Python and Ruby web frameworks being less widely used than PHP overall they are still very strongly represented among the most successful and innovative web projects of the past decade.
- jimmyjames 16y ago
  <shrug> Feel free to use whatever metric makes you feel good, all I'm saying is that the number of jobs for Java, PHP, Javascript and ASP.net (yes, even Basic) absolutely dwarfs those for Ruby on Rails.
  - ahlatimer 16y ago
    So, by lumping together four (or five) different platforms, you manage to come up with a number that is larger than those using Rails? That's not entirely surprising. You're also counting Javascript, which I find odd. Javascript is used in ALL of those platforms, so including it in an argument is extremely unfair. I do some Javascript programming from time to time, but I also spend a fair amount of time in Rails. When I was doing PHP and ASP.net programming, we were also using Javascript. So, yeah, there are going to be more jobs for front-end developers than those who program in some back-end platform, because all sites need some sort of a front-end (excluding some project that's purely an API). There's also a dilution of programming jobs for the aforementioned platforms, from my experience. Finding a job doing Rails seems to be fairly easy as, even though it was the "next big thing", the average programmer felt better sticking with Java, PHP, or ASP.net. There are way more Java programmers than there are Rails programmers, but it seems the ratio of programmers to programming jobs seems to be more in the favor of Rails.