Thanks for sharing this, Ben. I'm with you! I just love that dev.to is a Rails app (or to paraphrase you, an app that contains a lot of Rails). It's important to set an example and I'm glad to see you doing that.
I also sometimes share your reticence to admit the Rails affiliation - although I'll stand on the hill + defend Ruby as a beautiful language to anybody who would say otherwise.
I recently had to make a stack decision between Rails + Phoenix for a big project, one that I'll be spending the next year or so building. I've already got production apps written in both frameworks and find them both really beautiful in their own ways, but the decision came down to my team being faster with Rails. We can do more in the same time. But I'm still using Elixir to write various helper apps + 'bots ;) And for the gnarly front-end stuff, I'm staying functional with Elm all the way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for sharing this, Ben. I'm with you! I just love that dev.to is a Rails app (or to paraphrase you, an app that contains a lot of Rails). It's important to set an example and I'm glad to see you doing that.
I also sometimes share your reticence to admit the Rails affiliation - although I'll stand on the hill + defend Ruby as a beautiful language to anybody who would say otherwise.
I recently had to make a stack decision between Rails + Phoenix for a big project, one that I'll be spending the next year or so building. I've already got production apps written in both frameworks and find them both really beautiful in their own ways, but the decision came down to my team being faster with Rails. We can do more in the same time. But I'm still using Elixir to write various helper apps + 'bots ;) And for the gnarly front-end stuff, I'm staying functional with Elm all the way.