Comment by jcelerier

> Like, just look at the amount of results for "Minecraft" "slow"

My niece was playing it just fine on a decade-old Mac mini. I've played it a bit on a Raspberry Pi.

The sales figures suggest my nice's experience is fairly typical, and things such as you quote are more like the typical noise that accompanies all things done in public — people complaining about performance is something which every video game gets. Sometimes the performance even becomes the butt of a comic strips' joke.

If Java automatically causing low performance, neither my niece's old desktop nor my Pi would have been able to run it.

If you get me ranting on the topic: Why does BG3 take longer to load a saved game file than my 1997 Performa 5200 took to cold boot? Likewise Civ VI, on large maps?

> one of the most notoriously slow and bloated video game ever?

I like how you conveniently focus on that aspect and not how that didn't prevent it from being one of the biggest video game hit of all time.

Those two can be true at the same time. And that's one thing that a lot of technical people don't get. Slow is generally bad. But you cannot take it out of context. Slow can mean different things to different people, and slow can be circumvented by strategies that do not involve "making the code run faster".

The fact that it was later bought by Microsoft (and rewritten in C++ so it can run on consoles[1]) is not relevant to the argument that you can, in fact, write a successful and performant game in Java, if you know how.

[1] My source is just comments in HN.

Are we talking modded? Cause Vanilla minecraft runs on a potato, especially if the device is connecting to a server (aka doesn't have to do the server-side updates itself).

Runs fine on an essentially single threaded 7350k with a 1050ti I built 8-9 years ago.

The server runs on a single thread on a NUC, too.