We&#x27;re both right. Rails look the way it looks because of Ruby. What I am advocating is a compromise between the two of them. Rails-esque packaging, and API design on the entire stack e.g Active Record to Active Support. 
But using Swift strengths with protocol conformance, extensions, associated-types and etc.<p>I would never want to work on a larger Ruby code base again. It&#x27;s just too hard to iterate on as things break too much compared to a larger Swift code base. That&#x27;s just my take.<p>I actually like Ruby, but for scripts and smaller code. Not large applications. Same applies for ES6, where I think TypeScript would do a better job.