upvote

points

by pjmlp5 hours ago |
comments
upvoteby 5 hours ago|
next
[-]
deleted
reply
upvoteby Shorel5 hours ago|
prev|
next
[-]
Dlang is my weapon of choice and I prefer it to rust.
reply
upvoteby slopinthebag3 hours ago|
prev|
[-]
including c++ with all of those qualifiers would be like me saying rust is fast with sccache, subsecond, cranelift, and making every single module a separate crate.
reply
upvoteby pjmlp3 hours ago|
parent|
[-]
The difference being the adoption culture across the ecosystem.

C++ game engines also don't need Bevy like tutorials, because most studios aren't compiling them from scratch, and tools like Live++ or VC++ hot reload are relatively easy to use.

reply
upvoteby slopinthebag3 hours ago|
parent|
[-]
unreal engine is compiled from scratch (depending on your definition of "from scratch") and has notoriously long compile times. heck you have to recompile the editor to make certain gameplay code changes. and it's by far the most popular AAA game engine on the planet. if it was so easy to fix with your suggestions they would have done it already.

but hey, just add subsecond and switch to cranelift. problem solved :)

reply
upvoteby pjmlp2 hours ago|
parent|
[-]
Unreal Engine has an installer, and they have done my suggestions, as they are the main customers of Live++ [0], advocates of tooling like Blueprints and now Verse for doing full games.

Many studios have delivered games with little to no changes to the underlying C++ code.

[0] - https://dev.epicgames.com/documentation/unreal-engine/using-...

reply
upvoteby slopinthebag6 minutes ago|
parent|
[-]
so... c++ compile times are fast, because you can simply not compile c++ and instead use blueprints? seems odd since we're talking about c++/rust compile times. turns out you can make rust compile times infinitely faster by not compiling it too...

but when you do have to compile c++, it can be real slow. maybe not as slow as rust, but it's not in the same league as eg. go, c#, zig, etc.

ue5's hot reload is by no means perfect either - many gameplay code changes require recompiling the editor. exposing c++ properties on a blueprint? recompile. modify a constructor? recompile. changing parameters, return types, or adding/removing UFUNCTION or UPROPERTY macros? recompile. you can simply search the web to read the experiences of thousands of ue devs complaining about slow compile times and workflows. it's the same with unity btw, search "reloading domain unity".

also verse is not in unreal engine. no studio is using verse for ue games. not sure why you threw that in.

i get you love c++ and dislike rust, but you aren't really making a good case for c++ when you group it in with other languages that have fast compile times ootb, make arguments that involve not using c++ (like blueprints, lol), and rely on brittle third-party hot-reloading solutions.

reply