Rails is pretty awesome for building monolithic, CMS systems and other CRUD type apps. It's not awesome for a lot of other things. I don't really get the poin

Rails is pretty awesome for building monolithic, CMS systems and other CRUD type apps. It's not awesome for a lot of other things. I don't really get the point of this article and the author seems to be contradicting himself all over the place. Like, how can you possibly talk about the pitfalls of dynamic typing and then a paragraph later tell people to use JavaScript or Python? WTF? Most problems at scale have to do with I/O, which Go isn't going to help you with. Your data stores are gonna be your pain points. And oh boy, talk about a mentality of premature optimization... seriously folks, worry more about making something that someone is gonna want to use than how many requests per second the thing can serve. Right now your product has zero requests per second so you could just fulfill them by hand if you had to.