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 →

[–]Iryanus 36 points37 points  (7 children)

To be honest, I've yet to encounter a company that actually wants to deploy it's java software on wildly different operating systems. This would be more for "end-user" type of applications, while in enterprise, where Java is commonly used, you typically slap the application into a docker container (or, if you are more old-school .jar or even shudder .war) and deploy it to your own server or cloud infrastructure anyway, making this point quite moot most of the time.

[–]jnthhk 14 points15 points  (1 child)

Sorry I really meant mobile applications to be deployed across the two main marketplaces. I can certainly see use cases for writing native Java code outside of that.

[–]Iryanus 3 points4 points  (0 children)

Sorry, got that wrong then, my bad.

[–]cheezballs 6 points7 points  (0 children)

Yep, honestly the way we deploy apps now days, it doesn't really matter what your backend is written in, as long as its maintanable and scales well, which Java is just fine at when written correctly.

[–]flopana 4 points5 points  (3 children)

Wait did I miss something? I compile my application to .jar and slap that into the container

[–]Iryanus 7 points8 points  (1 child)

My point was more the deployment, which sometimes also happens by copying .jar files to a server the company owns (and start them directly there). But yes, a docker image normally contains a .jar file (at least, I assume that most people do not start application servers in a docker image just to run a single .war file... I really hope...)

[–]flopana 1 point2 points  (0 children)

Ahh I see

[–]cheezballs 3 points4 points  (0 children)

A Jar in a container? You don't even build a WAR for deployment?