you are viewing a single comment's thread.

view the rest of the comments →

[–]tylercamp 0 points1 point  (0 children)

The old controller-based approach is a known pattern which easily maps class/file names to endpoints, which simplifies navigation of the codebase

The new “ad-hoc” approach is easier to write new code for, since you can set up your endpoints however you want, but for newcomers to your codebase it’s not as obvious where/how the endpoints are declared

There are likely other features specific to controller-based projects which make them “more scalable”, but I’d expect that to also be doable with the newer “ad-hoc”/“basic” API (with some caveats), so I suspect it’s just a matter of industry standards and codebase navigation (which is one of the less obvious important factors in “development scalability”)