Hey, Your lucky, i just made benchmarks all this time :D. Check them out https://snowiiii.github.io/Pumpkin/about/benchmarks.html

Please, just use one measurement unit across all measurements for easier comparison (i.e. RAM in MB, time in ms).

Wow. Pumpkin's runtime is way better (faster, much less RAM used) than the Java versions. Congrats.

I wonder what the Kotlin-based Minestom is doing differently that causes it to have numbers between Pumpkin and the Java versions.

For comparison's sake, do you have build times for Pumpkin? I'll assume that's where critics may target.

> For comparison's sake, do you have build times for Pumpkin? I'll assume that's where critics may target.

How bad could it be? I cry while async-stripe crate builds.

> I cry while async-stripe crate builds.

The build times on async-stripe are inhumane. I wish the project didn't use so much codegen.

Just tested compile times

Compiling from Nothing

*Debug:* 10.35sec *Release:* 38.40sec

Recompilation (pumpkin crate)

*Debug:* 1.82sec *Release:* 28.68sec

I will put them into the benchmarks

Minestom is not based on Kotlin, im guessing they went with a kotlin template instead. Minestom is a server implementation that doesn't use any Mojang code and by default doesn't do much for you but provides the utilities to add the things yourself.

I literally said Holy Shit out loud. This is an incredible improvement, and I'll refer to this in the future when I'm asked if we should make something new in Java.

Keeping in mind that this server appears to implement only a tiny subset of the features the ones it is benchmarked against do... No lighting, mob spawning, mob ai, redstone functionality, tree or plant growth, water/lava flow, etc.

These wouldn’t significantly affect the first 10 chunks loaded?

More than a "yes, it should". While loading chunks you need to take redstone, nature and mobs into account. If you don’t - you need to find them and resolve at runtime with even bigger costs, relying solely on difference between programming languages in performance.

Yes but also consider the extensibility accessibility Java gave us. EVERYONE was building Minecraft mods back in the beta days. I might go as far as to say that extensibility is what made Minecraft so great.

What I always found surprising was how many minecraft mods there were despite mojang having absolutely no mod support for the game.

After learning that to make a minecraft mod the process was basically decompile minecraft fight the terrible names provided by the decompiler to make your changes then recompile it, I lost all interest.

Yarn[1] has pretty much fixed this along with fabric.

[1] https://github.com/FabricMC/yarn

No doubt about it. I don't think Minecraft would have gotten as far as fast in the public consciousness without content creators like Yogscast being able to produce so much novel content from modded Minecraft.

I was suprised myself thats its that bad. Well optimized binary is that what your CPU loves not a big JVM runtime

Hey, Sorry Im not native english speaker, I will try to fix all grammer issues now thanks :D