Just so I am following... you converted from a dynamic language and opinionated framework designed for rapid feature execution and programmer happiness to a typed, compiled language that is 22-50x faster but considers uniq too frivolous to include in its standard lib.
Look, I'm happy for you and your team that you identified your bottlenecks and did the right thing to address them, but why did you have to write yet another clickbait "move from Ruby, save 5x on hosting!" blog post? Even though you take great pains to repeatedly say some nice things about the language and framework that got you this far (for free), you make it sound like Ruby was a problem that got solved with Go. It's nowhere near this simple, because designing your application and its API in Go from scratch would have been miserable for all of the reasons we champion in The Rails Doctrine.
Both Ruby and Rails call on libraries written in other languages because they are clearly more performant than Ruby ever will be. JSON parsing and sqlite3 come to mind immediately. How is what you're doing any different, except for the fact that you're recasting this architectural evolution as a "move" instead of optimizing the parts of your infrastracture that need to be compiled in something. Go is a great language, but you could have used Java, C++ or Rust, and achieved similar results. And you should!
But don't come on here and give the "Rails is dead" morons another piece of kindling. Rails is kicking ass right now.
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.
Just so I am following... you converted from a dynamic language and opinionated framework designed for rapid feature execution and programmer happiness to a typed, compiled language that is 22-50x faster but considers
uniqtoo frivolous to include in its standard lib.Look, I'm happy for you and your team that you identified your bottlenecks and did the right thing to address them, but why did you have to write yet another clickbait "move from Ruby, save 5x on hosting!" blog post? Even though you take great pains to repeatedly say some nice things about the language and framework that got you this far (for free), you make it sound like Ruby was a problem that got solved with Go. It's nowhere near this simple, because designing your application and its API in Go from scratch would have been miserable for all of the reasons we champion in The Rails Doctrine.
Both Ruby and Rails call on libraries written in other languages because they are clearly more performant than Ruby ever will be. JSON parsing and sqlite3 come to mind immediately. How is what you're doing any different, except for the fact that you're recasting this architectural evolution as a "move" instead of optimizing the parts of your infrastracture that need to be compiled in something. Go is a great language, but you could have used Java, C++ or Rust, and achieved similar results. And you should!
But don't come on here and give the "Rails is dead" morons another piece of kindling. Rails is kicking ass right now.