3 ms·
It is the future of game development. I think that Rust makes it easier to build your own engine from public crates. In some sense blueprints are necessary bec
by adamnemecek 6y ago
It is the future of game development. I think that Rust makes it easier to build your own engine from public crates.
In some sense blueprints are necessary because using CPP sucks. I can imagine that instead of Blueprints, Rust based engines will use some DSLs.
- creata 6y agoBut Pfhreak's point is that most people don't want to "build their own engine", they just want something that lets them make a game, and Unity and GameMaker are very good at giving you that running start, even if you know very little programming. The Rust gamedev community, so far, hasn't even tried to create that experience.
- adamnemecek 6y agoMost people don't want to build their engines since it's hard in cpp. If building an engine consists of selecting a couple of crates, people might have a different opinion.
- Pfhreak 6y agoNo, most people don't want to build their engines because building engines is a different thing than making a game. People want to build just the part that's unique to their game. Very, very game devs care about how things are drawn to the screen or what's happening in their physics engine -- they just expect those things to be easy to use default features.
- deleted 6y ago[deleted]
- mrnothing_123 6y agoone te driver tend to be write in c or c++ make it mor reasonable to use the same langues, ogre3d for (c++), heaps( for haxe i love it compiled to c++), mono(for c#/ c++), raylib (c/c++), i dont know why you want spend at of time in make a engine that need some of this frameworks, whit weird interface to use rust
- adamnemecek 6y agoYou won't be doing interop with these frameworks, if that's your point.