[hnzix]

Rails provides a sensible and productive pattern for MVP but doesn't provide much guidance past a certain complexity level (Service Objects etc). Once the app grows past a certain size, more bespoke architecture needs to be applied and this will live or die on the competence of the team. Spaghetti code is not inevitable but can result from devs who are used to the hand-holding of less complex Rails apps.

Dunno where you are pulling docker from, that is completely orthogonal to Rails development.

[phendrenad2]

Yeah, dragging in docker is perhaps unfair, but Ruby apps suffer in a docker environment especially because of how much native code Ruby gems like to include (and how incredibly brittle they are under slightly different C++ compilers...)

[ravenstine]

I took the Docker comment as a sort of dig at Rails teams throwing tech at problems in an inappropriate way with the goal of overcoming poor decision making. Not sure how fair that is since the use of Docker et al is often an exercise in cargo cult tech.

[dieselgate]

At the very least a docker/containerized app is really nice for development envs especially if there is a variation on hardware/machines used