4 ms·

Dependency management in ruby is trivial with bundler.

taligent 14y ago
For small, single apps sure. But if you have large apps with multiple Ruby versions then dealing with rvmrc, bundler and gem incompatibilities is a nightmare. Java's forward compatibility is a lot more robust.
- jdminhbg 14y ago
  You have an app with multiple Ruby versions?
  - taligent 14y ago
    Yes. I take it you've never worked at an enterprise company before ? Every time a new developer comes on board they just love to add new technology X and then in the years to come other developers add Y and so on. Of course there are developers who have to manage this.
    - calinet6 14y ago
      Enterprise company? Ha. Just try dealing with three different decade-old JVM versions once. You'll pray for bundler.
- damoncali 14y ago
  But if you have large apps with multiple Ruby versions then dealing with rvmrc... Why on earth would you do that?
- rsyntax 14y ago
  What use case is there for "multiple Ruby versions" within the same app?
tmo9d 14y ago
Oh I disagree entirely. After having spend two days debugging someone's versionless Gemfile / bundler problem on my CI server, I want someone to pay for my pain.
- jbail 14y ago
  That's not Bundler's fault. It's the fault of the person who made the versionless Gemfile. There's really no comparison between using Bundler and mucking around with JAR files or Ant scripts in Java. I've even seen Python codebases with a Java-esque rats nest of dependencies that are just as painful to get setup correctly. Bundler is way easier. I've never been on a Rails project where it took more than 30 minutes to get the env setup and it's in large part, thanks to Bundler. Admittedly, I haven't touched Java in a few years, but last I checked, Java had nothing like Bundler (which is a shame, because it could really use it).
  - tmo9d 14y ago
    Hey, don't forget Gradle - http://www.gradle.org http://www.gradle.org - Gradle syntax for declaring dependencies is similar to Maven. But there's a very close comparison between Bundler and managing dependencies with Maven or Gradle. And there's a huge difference. Maven Central has never been compromised because they have a secure method for deploying artifacts, RubyGems? You've had a fun month with RubyGems, right?
    - jbail 14y ago
      If you are going to base your argument on a one-time security vulnerability in RubyGems, then I'm just going to get out of your way and let you troll on.
  - tmo9d 14y ago
    Hey, don't forget Gradle - http://www.gradle.org http://www.gradle.org - Gradle syntax for declaring dependencies is similar to Maven. But there's a very close comparison between Bundler and managing dependencies with Maven or Gradle. And there's a huge difference. Maven Central has never been compromised because they have a secure method for deploying artifacts, RubyGems? You've had a fun month with RubyGems, right?

For small, single apps sure. But if you have large apps with multiple Ruby versions then dealing with rvmrc, bundler and gem incompatibilities is a nightmare. Java's forward compatibility is a lot more robust.

jdminhbg 14y ago
You have an app with multiple Ruby versions?
- taligent 14y ago
  Yes. I take it you've never worked at an enterprise company before ? Every time a new developer comes on board they just love to add new technology X and then in the years to come other developers add Y and so on. Of course there are developers who have to manage this.
  - calinet6 14y ago
    Enterprise company? Ha. Just try dealing with three different decade-old JVM versions once. You'll pray for bundler.
damoncali 14y ago
But if you have large apps with multiple Ruby versions then dealing with rvmrc... Why on earth would you do that?
rsyntax 14y ago
What use case is there for "multiple Ruby versions" within the same app?

tmo9d 14y ago

Oh I disagree entirely. After having spend two days debugging someone's versionless Gemfile / bundler problem on my CI server, I want someone to pay for my pain.

jbail 14y ago
That's not Bundler's fault. It's the fault of the person who made the versionless Gemfile. There's really no comparison between using Bundler and mucking around with JAR files or Ant scripts in Java. I've even seen Python codebases with a Java-esque rats nest of dependencies that are just as painful to get setup correctly. Bundler is way easier. I've never been on a Rails project where it took more than 30 minutes to get the env setup and it's in large part, thanks to Bundler. Admittedly, I haven't touched Java in a few years, but last I checked, Java had nothing like Bundler (which is a shame, because it could really use it).
- tmo9d 14y ago
  Hey, don't forget Gradle - http://www.gradle.org http://www.gradle.org - Gradle syntax for declaring dependencies is similar to Maven. But there's a very close comparison between Bundler and managing dependencies with Maven or Gradle. And there's a huge difference. Maven Central has never been compromised because they have a secure method for deploying artifacts, RubyGems? You've had a fun month with RubyGems, right?
  - jbail 14y ago
    If you are going to base your argument on a one-time security vulnerability in RubyGems, then I'm just going to get out of your way and let you troll on.
- tmo9d 14y ago
  Hey, don't forget Gradle - http://www.gradle.org http://www.gradle.org - Gradle syntax for declaring dependencies is similar to Maven. But there's a very close comparison between Bundler and managing dependencies with Maven or Gradle. And there's a huge difference. Maven Central has never been compromised because they have a secure method for deploying artifacts, RubyGems? You've had a fun month with RubyGems, right?