5 ms·
> if you don't like Rails, go somewhere else Exactly. Makes perfect sense to me. If you're not going to lean on the framework, why even use the entire stack? Y
by k33n 15y ago
> if you don't like Rails, go somewhere else
Exactly. Makes perfect sense to me. If you're not going to lean on the framework, why even use the entire stack? You can pick and choose the parts of it you like, and want to use under the context of something like Sinatra which is meant for that sort of thing.
> but if you have a Customer model and a Card model, where do you put the checkout code? It could go in either place.
You can put it in either place. I'm not sure I understand why just because there's some flexibility on where you can put method X you should just work completely outside of the framework.
Edit: But this is a different point than the original debate though. I think the blog author goes way too far in avoiding using the framework.
- jshen 15y agoYou can pick and choose the parts of rails as well. I have a rails 3.1 app that doesn't use active_record at all, but it does use active model and encapsulates the service layer in model objects.
- minikomi 15y agoI'll use this space to point people towards http://www.padrinorb.com/ http://www.padrinorb.com/ Padrino. Seems apt!