Yesterday I would have argued that with the rails framework Ruby is a great way to rapidly develop a scalable application. Today I started having an intermittent failure in one of my API instances and when searching about it the only thing I could find was one obscure blogpost that boiled down to “yeah sometimes Ruby Ave active record just screws up the character set off a string” exact same string, different results. Excuse me Ruby? How the fuck can you sometimes screw up a character set? There should be no sometimes to any thing here.
I like Ruby most of the time, but honestly, I’m not surprised at “sometimes” behavior from the language created by someone who, when asked for the formal definition of something in the language, said he’s “not really a formal kind of guy.”
I mean I’ve been using ActiveRecord for the last 20 ish years and I’ve never encountered or even heard of this bug. Sounds like you came across an especially obscure one.
I spent a few years with Ruby, and my experience is that Ruby and Rails couldn’t be more different in terms of programming approach, philosophy, and nature. I don’t trust Rails fully, but I do trust Ruby.
Yesterday I would have argued that with the rails framework Ruby is a great way to rapidly develop a scalable application. Today I started having an intermittent failure in one of my API instances and when searching about it the only thing I could find was one obscure blogpost that boiled down to “yeah sometimes Ruby Ave active record just screws up the character set off a string” exact same string, different results. Excuse me Ruby? How the fuck can you sometimes screw up a character set? There should be no sometimes to any thing here.
I like Ruby most of the time, but honestly, I’m not surprised at “sometimes” behavior from the language created by someone who, when asked for the formal definition of something in the language, said he’s “not really a formal kind of guy.”
Haven’t Spring Boot in Kotlin with jib and cloud integration caught upto this in terms of development speed?
I mean I’ve been using ActiveRecord for the last 20 ish years and I’ve never encountered or even heard of this bug. Sounds like you came across an especially obscure one.
I spent a few years with Ruby, and my experience is that Ruby and Rails couldn’t be more different in terms of programming approach, philosophy, and nature. I don’t trust Rails fully, but I do trust Ruby.