it's the exact same thing with a slightly different syntax. I do a lot of maven/sbt, and have done a lot of ruby/js and I think there's no difference but your f

it's the exact same thing with a slightly different syntax. I do a lot of maven/sbt, and have done a lot of ruby/js and I think there's no difference but your familiarity with them. if I could vote in either direction I think maven/sbt is actually easier because you don't need to deal with "global" install. very dumb feature to share packages across projects, much simpler to think about deps as always project specific. but then again no one forces you to use global install... so it's the same. it only gets bad once you need some hacky junk like rvm or virtualenv to achieve project dependency isolation. I will take a big Pom file or build.sbt over having to remember to enable the right installation of Python every time I switch projects any day.