Post #3720234
2026-06-05 17:45 UTC
@tisba@ruby.social P.S. the other end of this spectrum, where you pin your dependencies to require specific versions in a non-lock file, is absolutely horrible to work with if your package is ever installed in an environment along with other things. Bazel does that (or at least used to, I'm not sure if they've moved away from it in the most recent versions) and it has caused me and others a great deal of frustration 😅
Replies (1)
-
@tisba@ruby.social 2026-06-05 18:16
@diazona@techhub.social for a library, this kind of makes sense. But for an application that you develop this feels off. In Ruby, for example, most applications use Bundler, which allows to specify dependencies and it creates a lockfile. The lockfile is obeyed automatically, so CI, all developers or on deployment, you are guaranteed to get the exact same and expected versions. Ruby gems (Ruby libraries) don't have lockfiles, but rely on version constraints.