News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers (2015) by adamc on Wednesday May 16, 2018 @12:44PM (#17083885)
Your second paragraph got to the heart of it. If we want to use some standard build toolchain, it needs to use a nice language and not feel obscure. I was explaining to someone a bash script I wrote, and he said "why not use Python". There were reasons but... he was right, Python would be much easier to use and maintain, and we have a lot more developers who know it.

That said, Maven is incredibly suck-tastic.

Re:The sad state of sysadmin in the age of containers (2015) by eropple on Wednesday May 16, 2018 @12:47PM (#17083924)
Eh. It's not my favorite thing out there, but Maven's fine for what it is. It's designed for and explicitly for well-behaved Java artifacts. If your Java artifacts are not well-behaved, you're going to have a bad time--in my experience, most of those cases are doing things you probably shouldn't be doing.

(You may be a wizard and have a reason to do them, for sure--but that's what writing Maven plugins is for. Or not using Maven. You've got choices.)

Re:The sad state of sysadmin in the age of containers (2015) by clhodapp on Wednesday May 16, 2018 @01:08PM (#17084161)
Given the limitations of the platform, there really isn't a such a thing as a well-behaved JVM library that depends on other libraries, unfortunately. Oracle really dropped the ball by only serving their own needs with the module system.
Re:The sad state of sysadmin in the age of containers (2015) by eropple on Wednesday May 16, 2018 @01:40PM (#17084509)
Can you expand on this? Having done a pretty decent bit of JVM development, I've never really run into issues even doing some not-out-of-the-box stuff.
Re:The sad state of sysadmin in the age of containers (2015) by weaksauce on Wednesday May 16, 2018 @01:00PM (#17084070)
What reasons? I did some ruby shell automation and it’s dead simple to get it working and working correctly. I imagine python has a similar story.