But wouldn't those things be more of an ActiveRecord concern rather than a Rails issue? AR isn't the only ORM you can use within Rails. But again, as Mike said a simple :include would fix a very simple issue. N+1 issues aren't my priority when I have a very short amount of time to throw together a prototype for a client, that where Rails will, for me at least, always win. Once I have a signed SOW and a green light then N+1s will matter, but at that point either I'll be triple checking my code anyway or hell maybe we won't even be using Rails for the production app, although a vast majority of the time Rails is a great solution. For me it's about the right tools for the job and for rapid prototype development, Rails is by far the right tools for me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But wouldn't those things be more of an ActiveRecord concern rather than a Rails issue? AR isn't the only ORM you can use within Rails. But again, as Mike said a simple :include would fix a very simple issue. N+1 issues aren't my priority when I have a very short amount of time to throw together a prototype for a client, that where Rails will, for me at least, always win. Once I have a signed SOW and a green light then N+1s will matter, but at that point either I'll be triple checking my code anyway or hell maybe we won't even be using Rails for the production app, although a vast majority of the time Rails is a great solution. For me it's about the right tools for the job and for rapid prototype development, Rails is by far the right tools for me.