ignorethat

This is wrong. It is only one reason for burnout. I have another.

I burned out because I can no longer care enough about what I'm doing at work to motivate my mind to work on the task at hand. It seems fruitless. People can try to convince me there is some good it is doing, but I see only waste and politics. That resentment is not because my workplace doesn't care about my family. They treat me better than any place I could ever hope to work for. The only sacrifice I've had to make for work is my sanity. I cannot stand development anymore, nor technology, nor I.T., but I'm incapable of doing anything else. I've read the books that say I must love what I do, but I don't, and there is no option to love what I do. I have chosen an occupation and career that no longer suits me, and I have no alternative. I am the only one with a job in my family. I cannot fail. I have to trudge on. This is burnout. I have no where to go.

Therefore, I would state instead that burnout is caused by lack of hope.

I want it, but only if Home Depot sells it for under $30.

I tried the locomotive solution back in the day and there was a reason it died. It sucked. Installing Rails was not the problem. Learning it was.

And again, the problem with Rails 3 today isn't the install. Instead it's that:

1. There is a shit-ton of old Ruby/Rails documentation out there that confuses the living shit out of people, and this is a duck-typed language, which is fine, but it means that people are even less likely to know what the fuck is going on when the code they are trying to use from someone's blog doesn't work.

2. Most of those using Ruby on Rails are not new as they once were, so since the majority know a little more about what the fuck they are doing, they are less likely to write things for those that don't know what the fuck they are doing.

But, writing an .app won't solve that. Instead, spend that time trying to take bundler, Gemfiles, rvm, the more complex Rails directory structure, asset pipeline, etc. and simplify the whole damn thing to create Rails 4, and chalk 3 up to an oops. A lot of the changes in Rails 3 were warranted, but the additional complexity will drive people away, and that is against the soul and original intent of Rails.

Want something that people would be really interested in? A framework that makes both development and scaling EASY. Development was easy with Rails years ago, but scaling was nearly impossible because that wasn't the intent. Now people scale Rails, but it is still hard, and development has gotten much harder. That's bad, because there are already ways to learn to develop quickly, and other solutions for scaling well. Being halfass at both is a sure way to fail miserably over the long-term, and Ruby and Rails is awesome; it shouldn't fail like this.