Hacker News Reader

Comment by icedchai | Hacker News Reader

Why is it "questionable"? It seems mostly IO, not CPU bound. Java gives you platform independent access to memory mapped files and non-blocking I/O.

View on HN

Garbage collection is a big downside since it introduces an implicit level of uncertainty and unpredictability performance wise. For intense I/O I'd also go with C++ over Java in general.

It depends on memory usage patterns. In some cases Java's GC could be even faster than malloc/free. I could say more, it's meaningless to discuss such provocative topic as "performance" with no any details.

Of course it depends. My point is, it's too unpredictable, even if you assume certain patterns are better or worse. That's why systems with RAII are much better by design in this aspect.

This is just cargo cult thinking: Java is bad. GC is bad. C++ is not Java, so it is good.

The only thing to do, is get on your coconut radio and wait for the planes to bring you some cargo. While you are waiting, Kafka is a useful MQ for event processing and is being used to solve real world problems today.

He gives a technical based explanation, wich is pretty accurate.. and not a emotional biased answer..

You obviously didn't get the point.

RAII semantics can be implemented in most GC languages nowadays with try/using/with/... Or with lambdas if the language allows for it.

RAII in C++ is a good pattern, but it does not avoid performance penalty of cascading release of resources, impossibility of using exceptions in destructors or thread contention with shared resources.

Reply on news.ycombinator.com