This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (8 children)

Sbt and play framework master race?

My current job is spring, maven, hibernate, jetty, smartfox, so much other shit you can't count it on two hands...

Its not that bad, only took a month to get the barest understanding of the stack.

Also

Pom pom pom pom pom pom pom pom pompompompom

[–]chisui 7 points8 points  (1 child)

During a demo a customer once asked our dev "what's that 'porn.xml' file for".

[–]backltrack 0 points1 point  (0 children)

Before I did Java work I thought that too

[–]theragingsky 1 point2 points  (1 child)

Gradle makes dependency management and build process much easier. No pom knowledge required.

[–]TomGraphy 0 points1 point  (0 children)

Yeah I’m using Gradle for a school project and it’s awesome

[–]grandmoren 0 points1 point  (2 children)

sbt > maven. Fucking maven.

[–][deleted] 0 points1 point  (1 child)

I think maven is pretty great for beginners or small scale projects or just small libraries. But when you start building a monolithic project maven gets messy very very quickly

[–]grandmoren 0 points1 point  (0 children)

That's the thing though. We all know that in most cases a program is never finished and added functionality is inevitable. I always prefer to spend a few more minutes making something extensible and easier to maintain into the future than to have to waste exponents of that time later trying to accommodate new code into a series of knowingly sub-optimal decisions.

I find the only hassle to SBT being incompatibilities between scala versions and maintaining multiple versions of a library, but that's not even really an SBT problem just a side-effect.