I had a coworker adopt Ruby for a major project about 20 years ago. He didn’t know it, nobody on his team knew it, and nobody else in the entire state had ever heard of it, so when the project failed after two years there was nobody around who could save it. I’m sure Ruby (on Rails) is a perfectly viable language/platform, but you wouldn’t know if from these guys.
Lots of stable stuff in Japan is (or until recently was as at least some omve to go or java) ruby. It’s not that it’s horrible per se, but it’s not going to be the most performant in some situations. I worked in grails in the past (the jvm version using groovy unsteady of ruby) and it’s not the worst.
As someone with his own preferences, I would never implement something in a language no one else knew, at least without leading courses on it first and confirming ability. Bus-factor 1 is no good.
TBF, my colleague also managed to produce complete disasters in a language (C#) that he knew, the entire company knew, and lots of other programmers in the area knew very well.
Yeah, when process and oversight fail, that can absolutely happen. As someone who’s been in the industry for 20 years, though, doing a thing that puts me as a single point of failure in production is just irresponsible. Maybe this is why I can’t find a job; too much sense (I work for a shitty japanese company and want out)
The guy who made ruby was japanese so lots of adoption and documentation. I spent years doing perl in the past and ruby was based on that, but I generally prefer compiled to interpreted. I would take ruby over php though
I’m trying to find a new job here in Japan. So much of it is PHP and Ruby. I’m already depressed enough as it is!
I had a coworker adopt Ruby for a major project about 20 years ago. He didn’t know it, nobody on his team knew it, and nobody else in the entire state had ever heard of it, so when the project failed after two years there was nobody around who could save it. I’m sure Ruby (on Rails) is a perfectly viable language/platform, but you wouldn’t know if from these guys.
Lots of stable stuff in Japan is (or until recently was as at least some omve to go or java) ruby. It’s not that it’s horrible per se, but it’s not going to be the most performant in some situations. I worked in grails in the past (the jvm version using groovy unsteady of ruby) and it’s not the worst.
As someone with his own preferences, I would never implement something in a language no one else knew, at least without leading courses on it first and confirming ability. Bus-factor 1 is no good.
TBF, my colleague also managed to produce complete disasters in a language (C#) that he knew, the entire company knew, and lots of other programmers in the area knew very well.
Yeah, when process and oversight fail, that can absolutely happen. As someone who’s been in the industry for 20 years, though, doing a thing that puts me as a single point of failure in production is just irresponsible. Maybe this is why I can’t find a job; too much sense (I work for a shitty japanese company and want out)
Ruby, for network stuff? How? Why?
The guy who made ruby was japanese so lots of adoption and documentation. I spent years doing perl in the past and ruby was based on that, but I generally prefer compiled to interpreted. I would take ruby over php though