InfoQ Interview: Rich Kilmer on the Power of Ruby

Re:InfoQ Interview: Rich Kilmer on the Power of Ruby by Gigachad on Thursday June 15, 2023 @07:11PM (#36348170)

Breaking changes are not an issue, it’s the fact you can’t spot them before deploying. TS would warn you when compiling, but Ruby gives you nothing until that specific code gets run.

I recently had an issue where updating ruby caused kernel#open to change its parameter list, but all of our tests has this call mocked out since it makes a web request. Then it blows up in production. Despite all my efforts I couldn’t even find the changelog or PR that caused this breakage.

[ Parent | on HN ]

Re:InfoQ Interview: Rich Kilmer on the Power of Ruby by realusername on Friday June 16, 2023 @02:20AM (#36352218)

Sure but what's the point of types if none of the packages you use are using it or are even tested in the first place?

I also have the same story on the JS side, we upgraded the package to open notifications, they broke the API and kept the types the same. Now we added a test that notifications are working (we're basically doing the package maintainer's job).

Ruby's update story isn't prefect, far from it but I'll take it any day against npm. I worry at every package upgrade on the JS side.

What's making it even worse is that the stdlib is very limited on the JS side, so this effect is compounded.

[ Parent | on HN ]