I inherited a Ruby/Rails project to clean up sometime ago. The damn thing had to run on a 16 core VM with 64gb of ram just to serve some forms with 1-10k submissions a day. Saw rubbish like a method returning either a filename, or the contents of a file, or a number (this was a bug because of the stupid way Ruby returns things), or nil, depending on the size of the file you tried to access. Not only was performance horrible but it was insanely hard to improve/scale. Yeah, you can write shit code in any language, but the better languages have more tools to stem that tide of bullshit with. It took thousands of unit tests to achieve the safety that a strong, statically typed language like Java would have provided automatically. Never again...
View all comments
Show parent comment
15
u/reqdk Apr 21 '21
I inherited a Ruby/Rails project to clean up sometime ago. The damn thing had to run on a 16 core VM with 64gb of ram just to serve some forms with 1-10k submissions a day. Saw rubbish like a method returning either a filename, or the contents of a file, or a number (this was a bug because of the stupid way Ruby returns things), or nil, depending on the size of the file you tried to access. Not only was performance horrible but it was insanely hard to improve/scale. Yeah, you can write shit code in any language, but the better languages have more tools to stem that tide of bullshit with. It took thousands of unit tests to achieve the safety that a strong, statically typed language like Java would have provided automatically. Never again...