5 ms·
"... Java, have you learned to easy yet?" Try Play, Grails, Vert.X. And you know what it isn't easy. Having to deal with Ruby's dependency nightmares.
by taligent 14y ago
"... Java, have you learned to easy yet?"
Try Play, Grails, Vert.X.
And you know what it isn't easy. Having to deal with Ruby's dependency nightmares.
- spellboots 14y agoDependency management in ruby is trivial with bundler.
- taligent 14y agoFor 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 agoYou have an app with multiple Ruby versions?
- taligent 14y agoYes. 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 agoEnterprise company? Ha. Just try dealing with three different decade-old JVM versions once. You'll pray for bundler.
- damoncali 14y agoBut if you have large apps with multiple Ruby versions then dealing with rvmrc... Why on earth would you do that?
- rsyntax 14y agoWhat use case is there for "multiple Ruby versions" within the same app?
- tmo9d 14y agoOh 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 agoThat'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 agoHey, 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 agoIf 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 agoHey, 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?
- saryant 14y agoI've been using Play every since 2.0 came out and I'm a huge fan. It's just fun to work with.
- squidsoup 14y agoAre you using Java or Scala with Play 2.0? Play looks like an excellent framework, but my perception is that Play 2.0 is very Scala oriented. Scala seems a bit daunting.
- saryant 14y agoI'm using it with Scala. My understanding is that Play can be used without writing any Scala whatsoever. That said, you can start with Scala as "better Java" and ramp up to its advanced features. That's how I began. At first you're just replacing for-loops with map/reduce, eventually you'll start passing around implicit variables and using for-comprehensions all over the place.
- tmo9d 14y agoRight, and I'm calling Grails, Play, Scala, Vert.x Java in that article I wrote. I think a lot of Rails folks walked into a closed box in 2008, and they should have. Rails was hugely different from the alternatives back then. The world has caught up. That's one of the points I didn't quite make very well. Ugh.
- calinet6 14y agoThat makes sense. The landscape has definitely changed, and you're right, there are alternatives now that didn't exist when Rails was just starting. I think Rails still has some advantages, and a head start in both development concepts and supporting libraries and frameworks. My point wasn't that Java and its kin are necessarily incapable of these things, just that Rails has had that mindset from the start, and as such deserves the mindshare that it receives.