Drop RobotLoader and let Composer Deal with Autoloading

Written by Tomáš Votruba / Original link on Jun. 8, 2020

Using 2 tools for one thing, in this case 2 packages to autoload classes, are sign of an architecture smell. Many applications I see contain RobotLoader for historical reasons. I will borrow this from psychology: pathological behavioral patterns tear us down in the present, but were useful in past. The best way to deal with them is acknowledge their purpose and then, let them go and enjoy the gift of present.


« How to add unlimited custom domains to Laravel Vapor - Microsoft Regional Director (Trifecta) »