A year with Go - Hackdot

Re:A year with Go by andrepd on Friday June 05, 2015 @08:46PM (#9669097)

I think you must agree that no matter how painless it is, binary < JAR + JRE, in terms of deployment effort.

[ Parent | on HN ]

Re:A year with Go by Skinney on Friday June 05, 2015 @09:45PM (#9669242)

Depends. For me, creating an uberjar with my default project/package manager is easier than to setup cross-compilation with Go. YMMW.

[ Parent | on HN ]

Re:A year with Go by nulltype on Friday June 05, 2015 @10:46PM (#9669410)

Why don't they just combine the JRE and JAR file? Then I can be sure it works when I download it.

[ Parent | on HN ]

Re:A year with Go by Skinney on Friday June 05, 2015 @11:06PM (#9669456)

For the same reason you don't deploy Windows, BSD and Mac OS X binaries of your Go program to a Linux server.

[ Parent | on HN ]

Re:A year with Go by nulltype on Saturday June 06, 2015 @03:16AM (#9670019)

Yeah I use the Linux binary, I'm not sure what you're saying here.

[ Parent | on HN ]

Re:A year with Go by Skinney on Monday June 08, 2015 @08:05PM (#9683298)

The JRE is platform specific, the JAR isn't. Bundling them makes little sense.

[ Parent | on HN ]

Re:A year with Go by nulltype on Wednesday June 10, 2015 @05:20PM (#9695516)

I think it makes a lot of sense. I can download the Windows version of an app and double click on it and it runs. As opposed to I double click on it and it's all "oh you don't have a JRE" or "you have the wrong JRE, mysterious error" or "you need to install this JRE", or it installs a JRE for me, but another app requires a different JRE.

[ Parent | on HN ]