3 ms·
Having worked w/ rails/laravel, I'd say you could say the same thing and it may even be 'more' true about laravel (see: built in queues, authentication, etc), w
by gremlinsinc 6y ago
Having worked w/ rails/laravel, I'd say you could say the same thing and it may even be 'more' true about laravel (see: built in queues, authentication, etc), with rails you need devise, and 3rd party packages for a lot of the normal boilerplate.
However, lately I'm thinking more about performance so would love to work more with rust or golang, though I find rust harder to grok mentally. Golang is nice though, and easy to follow most code samples.
- catwind7 6y agoI've been meaning to checkout rust/golang for some time now - might pick up a book on it. I've worked primarily with rails the past few years and at times it feels like some of our biggest maintainability issues are the direct result of certain third party packages we reached for to solve boilerplate. Not to knock on using libraries or anything like that, but we've definitely felt the pain of putting tools / convenience ahead of architecture.