4 ms·
idk. This was common knowledge/advice when I first worked with Rails professionally on a startup-size team over a decade ago. The writer says “That’s when peop
by bluepod4 3y ago
idk. This was common knowledge/advice when I first worked with Rails professionally on a startup-size team over a decade ago.
The writer says “That’s when people jump to googling ‘how to autoload lib/‘. Don’t do it! lib/ should not be autoloaded.”
But from experience, that’s not what was commonly queried. The search terms or the question asked to senior engineers went something like “my Rails lib dependency is not loading in production” which always lead to the “require” solution and the advice against autoloading.
Thinking about it more, I don’t recall ever googling the word “autoload”.
Have all of those old StackOverflow posts been removed?
Are newer devs not using linters that check for this?
Is the audience for this article solo devs inexperienced with working with Rails?