▲ 12 ▼ Installing Java in 2025, and Version Managers (blog.hakanserce.com) submitted 11 months ago by rssbot@lemmy.bestiver.se [B] to c/hackernews@lemmy.bestiver.se 8 comments fedilink hide all child comments Comments
[–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (7 children) ...but one thing remains the same: it still sucks. permalink fedilink source hideshow 7 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 5 points 11 months ago (6 children) Not sure what experience with Java you are talking about. As a Dev, modern Java still rock solid and is finally quite convenient to use and the JVM itself is a great runtime. permalink fedilink source parent hideshow 6 child comments replies: [–] orbituary@lemmy.dbzer0.com 7 points 11 months ago* (5 children) As an admin who has to update it, work with it, or interact with it from a workstation or server, it's a terrible experience. permalink fedilink source parent hideshow 5 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (4 children) Ok, that I can understand. But any modern Java application should be shipped as a container were this isn't an issue. permalink fedilink source parent hideshow 4 child comments replies: [–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (3 children) "My car is super reliable, but only if you put it on the back of a big flatbed truck." permalink fedilink source parent hideshow 3 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] AudaciousArmadillo@piefed.blahaj.zone 5 points 11 months ago (6 children) Not sure what experience with Java you are talking about. As a Dev, modern Java still rock solid and is finally quite convenient to use and the JVM itself is a great runtime. permalink fedilink source parent hideshow 6 child comments replies: [–] orbituary@lemmy.dbzer0.com 7 points 11 months ago* (5 children) As an admin who has to update it, work with it, or interact with it from a workstation or server, it's a terrible experience. permalink fedilink source parent hideshow 5 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (4 children) Ok, that I can understand. But any modern Java application should be shipped as a container were this isn't an issue. permalink fedilink source parent hideshow 4 child comments replies: [–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (3 children) "My car is super reliable, but only if you put it on the back of a big flatbed truck." permalink fedilink source parent hideshow 3 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] orbituary@lemmy.dbzer0.com 7 points 11 months ago* (5 children) As an admin who has to update it, work with it, or interact with it from a workstation or server, it's a terrible experience. permalink fedilink source parent hideshow 5 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (4 children) Ok, that I can understand. But any modern Java application should be shipped as a container were this isn't an issue. permalink fedilink source parent hideshow 4 child comments replies: [–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (3 children) "My car is super reliable, but only if you put it on the back of a big flatbed truck." permalink fedilink source parent hideshow 3 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (4 children) Ok, that I can understand. But any modern Java application should be shipped as a container were this isn't an issue. permalink fedilink source parent hideshow 4 child comments replies: [–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (3 children) "My car is super reliable, but only if you put it on the back of a big flatbed truck." permalink fedilink source parent hideshow 3 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] orbituary@lemmy.dbzer0.com 4 points 11 months ago (3 children) "My car is super reliable, but only if you put it on the back of a big flatbed truck." permalink fedilink source parent hideshow 3 child comments replies: [–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] AudaciousArmadillo@piefed.blahaj.zone 2 points 11 months ago (2 children) I don't see how you'd have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue. permalink fedilink source parent hideshow 2 child comments replies: [–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent [–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent
[–] orbituary@lemmy.dbzer0.com 3 points 11 months ago Java isn't any of those. permalink fedilink source parent
[–] Deifyed@lemmy.ml 3 points 11 months ago It's millions of lines more code. In a dockerized world, there is zero reason to use another virtualization layer permalink fedilink source parent