Re:Why Java Is Still Worth Learning in 2025: A Developer's 2...
by lolive on Wednesday July 23, 2025 @05:14AM
(#44657178)
Apart from the comment of happymellon (blaming Spring for doing things behind your back), it happens that a factory , building objects for you , will have a “bug” and retain a reference to them for whatever reason.
That is sometimes tricky to figure out.
Nothing Java can be blamed for, as these kind of tricks can happen in any language.
([newbie at C but] I suppose in C, the consumer of the object can force its deallocation, which may lead to other nasty side effect]
[ Parent
| on HN ]
Re:Why Java Is Still Worth Learning in 2025: A Developer's 2...
by lucianbr on Wednesday July 23, 2025 @05:19AM
(#44657198)
> I've worked with Java for 25 years and have a love/hate relationship.
> Java garbage collection is both great, and terrible.
> Nothing Java can be blamed for
I mean, it's not like we're discussing Java or anything. So they hate java because of something that can happen in any language?
Re:Why Java Is Still Worth Learning in 2025: A Developer's 2...
by lolive on Wednesday July 23, 2025 @05:37AM
(#44657317)
They expected not to have to deal with memory at all, I presume ;)
[to go a bit off topic, the debugging of those issues is reasonably tool-assisted in Java, whereas I honestly don’t know how to solve them in, let’s say, Javascript/TS).