Skip to content

Comment on Asynchronous clean-upparent

Comments

Describing Minecraft as "solid" makes me very scared reading "certified safety systems". Minecraft is the most standard possible example of Java's badness and bloat. It's explicitly what software should strive not to be.

It's a game first and foremost, and it mostly works, quite well, with multiple players. It's a completely different set of requirements from safety software.

And people write mods for it and have had success. If that is not solid what is. For real what's so bad about minecraft, it even runs on a relatively old laptop of mine with 8 gigs of RAM without any lag.

In most safety software you can't even use dynamic memory. Maybe a lot of the software we write in that domain would be considered "bloat" in others, but I don't know what are the constraints that Minecraft faces that drove it to be implemented the way it is. But despite the bloat, they managed to do a lot.

For real what's so bad about minecraft, it even runs on a relatively old laptop of mine with 8 gigs of RAM without any lag.

When Minecraft came out, 8G of RAM would be pretty much the highest-end system you can buy. It's really not the flex you think it is.

In terms of the opposite direction from Minecraft in stability is Factorio, which can easily run on a multiplayer server for a gaming group on a potato of a computer and whose high-end multiplayer record is well over 500.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.