Being harder to update is the point. With ruby being untyped and lazy evaluated, it's even worse. If any library's api changes between versions, unless you're

Being harder to update is the point. With ruby being untyped and lazy evaluated, it's even worse. If any library's api changes between versions, unless you're sure you have a unit test for that function, it'll happily deploy and crash in production. Plus as long as you're using a service like snyk.io to make sure that you're covering security vulnerabilities, there's usually not much reason to updating if it works.