I also argue against the statement that Rails does not have a REST capability... the default routing for a given resource follows REST conventions, and in Rails 5, you can spin up a Rails app in API mode that slims down the gems installed (removing the templating and asset gems, e.g.), and optimizing the stack for restful API actions
I also argue against the statement that Rails does not have a REST capability... the default routing for a given resource follows REST conventions, and in Rails 5, you can spin up a Rails app in API mode that slims down the gems installed (removing the templating and asset gems, e.g.), and optimizing the stack for restful API actions
Maybe the author has never seen Rails used in the default way? I have seen apps that take make use of the defaults.
This is true. Our company has 12 Rails microservices, all running in API-only configuration.
The author obviously has mediocre experience with Rails and writes articles based on hearsays.