When I started working on DynaBlogger (https://www.dynablogger.com https://www.dynablogger.com) I picked Rails because that's what I've been using for many year

When I started working on DynaBlogger (https://www.dynablogger.com https://www.dynablogger.com) I picked Rails because that's what I've been using for many years. After one month or so into the development I tried Elixir and Phoenix and I seriously considered switching since I was still at the beginning. I liked response times in microseconds while with Rails you have to implement aggressive caching to achieve good enough performance. I liked the language and Phoenix too was nice, but eventually I decided to stick with Rails. The main reasons were 1) it was easy to get started but it would have taken quite a while for me to become as fluent with Elixir/Phoenix as with Ruby/Rails, 2) I would have had to reinvent several wheels from scratch or make do with inferior alternatives to popular Ruby gems. I didn't want to spend too much time with this then but I will likely revisit Elixir/Phoenix later, if needed for performance or else. I think this is a good combination of language and framework but if you go that route you need to be sure you're ok with a smaller ecosystem, meaning that you may need to build things from scratch more often.