Paul Bergstrom wrote in post #969903:
Marnen Laibow-Koser wrote in post #969891:
I didn't realize it was a blanket prohibition.
Why can't you respect that?
I can't respect the idea that you get to decide who answers you when you post on an unmoderated public list. If you don't want answers from the public, don't post here.
I only ask you to respect me as a fellow human being, asking you to behave and interact with other people in a kind, respectful and warm manner.
Is that too much to ask?
I believe I have always done that; to the extent I haven't, I certainly apologize.
Several times when I have asked a question you have given me a question back like "why do you want to do that?" instead of just answering my question. Once or twice is nothing but not all the time.
It's nothing personal. You have a tendency to ask questions on this list which betray a misunderstanding of how to get the most out of Rails. It is my usual procedure -- and, on the evidence, that of many others here -- to clarify why you're asking for advice on something that doesn't seem like a good idea in the first place.
I am not going to just stick my head in the sand and tell you or anyone else how to implement a bad idea without first saying "this is a bad idea and here's how to do it better".
If you don't want advice, don't ask for it. If you ask for advice, please listen to it. Doing otherwise is not respectful to the people taking time and effort to give you the best advice we know how to give.
I didn't ask for your opinion about bundler. I asked if there is a way to require a gem but keep the gems in one place, like before. I don't understand why that question would be so hard to understand. Why make it so complicated Marnen?
I'm not making things complicated; you are. Rails explicitly makes it easy to do things in the "Rails way", and less easy to do things that its designers consider bad. That means that it will actually be less complicated if you learn the Rails way before trying to ignore it.
The Rails 3 way involves Bundler. Since it's the Rails 3 way, you should learn it before deciding to do without it.
I'm sure bundler is wonderful, but I could do without it.
Then do without it -- after learning to use it.
Is that ok with you?
It's not up to me.
You seem like a person who get nervous when someone is not following the rules. Is that true? Is that the problem here?
No. I pity people who choose an opinionated framework such as Rails, and then make life hard for themselves by choosing to ignore that framework's conventions in the name of "simplicity". It's actually simpler in most cases to learn Rails' conventions than to fight them.
Now, Rails didn't get everything right. The core team made a wonderfully testable framework, but built terrible testing tools -- which I know because I learned Test::Unit, then discarded it.
But if I thought that (say) it would be simpler to do without an ORM like ActiveRecord, I'd probably stop using Rails.
Best,
