Why Go and Rust are not competitors

Re:Why Go and Rust are not competitors by kasey_junk on Thursday July 02, 2015 @10:24AM (#9819047)

Let me start by saying I think the argument for binaries vs fat jars is overblown.

That said there is more complexity with the jvm. Do you have the right jvm installed? Where was it installed? Are there multiple versions of the jvm installed? Do you care? Can you mess with it? Have you accepted the license for the jvm? Should I use docker to manage all this complexity? Is the docker agent working? etc.

In environments where you are deploying to a single architecture that is more complex than "copy binary". In environments with LOTS of servers the (admittedly limited) complexity difference can add up.

[ Parent | on HN ]

Re:Why Go and Rust are not competitors by pjmlp on Friday July 03, 2015 @04:17AM (#9824251)

IT says everyone uses version X.

[ Parent | on HN ]

Re:Why Go and Rust are not competitors by kasey_junk on Friday July 03, 2015 @11:08AM (#9825956)

This group IT, do they set up the servers? Do they make sure policy is enforced? Do they deploy your software? If so, they are doing the work and we should be asking them & not you whether they prefer JVM based solutions or single binary ones.

[ Parent | on HN ]

Re:Why Go and Rust are not competitors by pjmlp on Friday July 03, 2015 @12:23PM (#9826449)

Most of the companies I worked for, only IT has a say what devs have on their machines and servers. You need tickets for everything.

[ Parent | on HN ]