Re:Ask HN: What (almost) company sinking engineering mistake...
by juanse on Friday March 25, 2022 @01:20PM
(#30804833)
Out of curiosity: What was the old language and what was its replacement?
[ Parent
| on HN ]
Re:Ask HN: What (almost) company sinking engineering mistake...
by irvingprime on Friday March 25, 2022 @01:48PM
(#30805166)
old = ruby (rails). New = Java.
Re:Ask HN: What (almost) company sinking engineering mistake...
by scruple on Saturday March 26, 2022 @02:32AM
(#30809758)
I've actually seen a (Sales) executive, without a seconds worth of technical experience, bad mouth Ruby / Rails in meetings. He would say that it was a competitive disadvantage to use it. He would say that if our customers found out we used Ruby on Rails that they'd leave us. He had a few other things he would repeatedly say about it. It was all so bizarre.
FWIW, he was fired after about 18 months on the job (for reasons unknown to me).
Re:Ask HN: What (almost) company sinking engineering mistake...
by engineerDave on Friday March 25, 2022 @08:03PM
(#30808127)
As a ruby dev this completely makes sense to me based on the Java developers I have worked with. I'm willing to bet he also never even considered jRuby as a happy compromise, also basing this on my experiences with the Java developers I have worked with
Re:Ask HN: What (almost) company sinking engineering mistake...
by irvingprime on Saturday March 26, 2022 @03:15PM
(#30814482)
I've also noticed that most Java devs dislike Ruby just as much as I (a ruby dev) dislike Java. But the guy who made this decision had never done development in Ruby, Java, or anything else. He was a former db administrator who went into management.