Kickstarter: rails.app

I don't know. There are many good observations about what happened to Rails the last years in the comments. Rails is complicated and to get fluent in Rails takes some time. But this complexity came with a great flexibility. And that's a sign that we are facing a phenomenal ecosystem. I admit starting rails is frustrating, so many new concepts but everything like rvm has a reason why and even beginners will realize this quickly.

Yehuda's approach reminds me of the early days of webdevelopment where you could install a WAMP stack with one click on your windows systems. I never liked those one-click-installers—you don't know what happens to your system and deinstalling was a nightmare with still running db servers somewhere for years.

You can't wipe away Rails complicated entry with such an one click-installer. After you installed Rails with one click things aren't getting easier your still have to figure out next steps and which frameworks to choose (i.e. ERB or HAML, SCSS or LESS, MySQL or Postgre, etc.). Or something breaks within rvm: with an yehuda's approach you are completely clueless because you don't know anything about rvm, gemsets because the installer did all the work for you.

Sometimes there is even too much magic in Rails. I am still wondering if ActiveRecord is too much abstraction and if there are better more direct ORMs like DataMapper, I am used to ActiveRecord but still I can not fluently create data models, there's always something I forget, using the plural or singular, saving the updated migration, rolling back the migration, etc. Otherwise it's far beyond any ORM from other Frameworks I have ever seen in terms of speed. And its usage in Ruby is very consistent. Also Rails shell commands are very consistent, once you understand the rails syntax (like rails generate or destroy something you can quickly build anything in minutes), I tried several times to find something similar with python/django but there the entries seemed to me even more complicated, don't follow any system and felt restricted, i.e. Django's automatic Backend (no offense, i know not enough about django and python to say anything serious but that was just my first impression).

Another last great example of Rails: once you managed to install Rails, just put haml, less, less-bootstrap-rails and simple_form in your gemfile and run bundle. with this setup you can build web apps in minutes with perfect design and they are fully customizable. some years ago you needed hours or days to get to similar results. It takes time to get there but once you are there you have the power.

this pace and variety in the rails ecosystem comes from so many talented people who contribute. trying to set one standard for how things are done would slow down this pace.

finally, I think that Yehuda doesn't want to raise money, he just wants to get attention and the approval that he had the right idea.

OSS development has to be funded somewhere and to date it has been the benevolence of bigger organisations that have awarded grants or developer time. This gives the opportunity for a developer to offer to solve a problem and for the community to vote with their pockets. It empowers developers and the community to get behind a problem space and if people don't want it it won't happen.

Im all for opening doors to newbies, and I think udacity and coursera are leading the way in that regard.

But if people desire to become programmers is it really that bad to have them come in contact with a little bit of configuration and head scratching.

A lot of programmers have hangups about money. Consider whether you do as well, and if so whether this is something you've purposefully chosen because you really like what it does for your life or whether it is just accidental. If it is accidental, you may want to consider stopping.

a) $25k is not a lot of money for very well-known programmers. There are fairly straightforward methods to get that much in a month (a salaried job), a week (contracting+), or a day (training event, $500 a head).

+ Stipulate that in addition to Rails he has at least one talent which makes money and this is not unreasonable at all.

b) There was no time at which OSS was not predominantly the work product of the global rich employed at corporations. This is observably true for Rails, since the list of contributors since DHH extracted it is both public and short. The Rails core team works on Rails like it is their job because...

c) ... Rails was designed to, and succeeds at, making companies great piles of money by increasing the efficiency at which they can churn out CRUD apps. Please note that is in no way a criticism. Apps running on Rails go from BCC (five figures a year) to Basecamp (eight figures a year and will probably hit nine eventually unless they already did).

d) OSS developers making money by it - I.e. The traditional accepted way to write it - does not make you personally worse off, because it increases software available to you. You may perceive that people will listen to you less because monied interests will drown out your voice. This is irrational: since the $100 you think is a lot of money only buys maybe 30 minutes of programmer time anyhow, the opinions that mattered in OSS were already those of companies which coul actually pay salaries, and someone freer with their last $100 than you are will only have epsilon more impact on "the community" than you when compared to IBM (a consulting company which staffed most Linux development) or Google (an advertising company which directly or indirectly pays the salaries of the majority of programmers working on either of the two big OSS browsers.) apache's Kickstarter was IBM realizing that they'd happily pay a billion dollars to have IIS not become the dominant server platform so they proceeded to do so.

I'm assuming this is a (weak) joke, but in case you're genuinely wondering:

    git config --global alias.statsu status