this post was submitted on 13 Nov 2024
795 points (96.2% liked)
Greentext
4383 readers
1292 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's much better today, but in 2010 that was 100% accurate.
That being said, using Java as a first time programming language is like a 15 year old trying to fly an airliner to get a few blocks away to pick up some after school snacks. Obviously it's way overkill. Sure you could get across town with it, but it's probably 1000x more complicated than just a simple bicycle or even walking.
Java is industrial strength for professionals. There's absolutely no consideration made for educational usage.
There is also absolutely no consideration in Java for production usage.
Which other eco system has more stable libraries, which are easy to install and redistribute and deploy?
I would choose always choose the most boring language for the task. That the good thing about java that it is very boring and most likely won't run into a obscure problem if you stay away from reflection and unsafe.
Pretty much any compiled language using native binaries is easier to install and distribute. Java applications are an absolute pain to get to run to the point that most need specialized wrapper scripts (usually in shell on unix platforms) and need to tinker with memory management parameters on almost all of them.
Do you mean something like c or c++ where you have to deal with big little edian, libc, utf8, platform specific threads, various compilers feature sets and a lot of undefined behaviour. Also if you want to distribute a library it is much harder because you a have to package it yourself or what for a distro to package your library or build a header only library which has to be manually updated every time a new version comes out. With maven you just have to upload it and you can use it in another project
How often do thinker with the memory management in Java? Just use the g1 garbage collector, which will be fine most of the time if you have a problem just use another one.
You can also compile the program with GraalVM to a native binary, also most Java programs are servers where it make sense to have a systemd service to configure the server
As a sysadmin unfortunately every single one of those shitty Java projects forces me into dealing with that sooner or later.
Disagree. It's an outdated tool today. Professionals would not choose it for new projects.
Java isn't outdated it is stable, today you don't need JakartaEE you can use something like Spring Boot, Quarkus, or a microframework.
Try to run an
npm installon a 3 year old Angular or React project and most likely it won't work