Why not use a distributed binary to launch Pumpkin?

[therabug]

Right now, Pumpkin needs to be compiled to run, and that takes time when you use release mode (which is the case every time). Instead of making compiling part of the process, I think it should be optional. I like FerrumC's approach as they provide a binary to start the Minecraft Server. I think that's necessary because when you use Pumpkin to create a large Minecraft server, there's downtime when you make an update to the server, and when you compile, there's even more downtime.

[Jimster4312]

I'm sure that will come when development is much further along 👍

[therabug]

Yeah probably

[Snowiiii]

While Pumpkin is not released it makes no sense to provide any Official downloads. But you can download Pumpkin executables from our Workflow which is ran every commit

[therabug]

Yeah, I totally agree. I was saying that should aim for a stable release.

[Snowiiii]

Well yeah all Pumpkin releases will have precompiled executables available. Also you said that there could be down time if there is an update, What about just compiling first before turning the current Server off?

[therabug]

Well yeah all Pumpkin releases will have precompiled executables available. Also you said that there could be down time if there is an update, What about just compiling first before turning the current Server off?

idk maybe I didn't thought about that

[suprohub]

???
Incremental compilation like:

[therabug]

I tried compiling twice in release mode, but Rust didn't rebuild the whole thing. This still makes it slow to compile the local source code. It recompiles source code, but not crates and it takes minutes.