One of the most important projects I ever keep an eye for was Amethyst.
Amethyst was a ECS Rust game engine, it was my first time looking on how a big project was developed, it's where I heard about cache locality for the first time, how pull requests and issues are discussed and reviewed and the discussion of various topics, including a disc. thread that lead to the creation of their ECS lib.
Then, I tried using Amethyst, I also did knew a bit about Rust although I surely wasn't prepared (I didn't knew anything about native coding like C and C++).
It was a disaster, I couldn't even put a sprite on the screen (actually, I don't remember if I even got a window open).
I got really frustrated and started feeling stupid.
I gave up, some time later I realized that it wasn't me the stupid one (I wasn't prepared though), but Amethyst was very very hard indeed due to it's complexity
Later, a developer would iterate over Amethyst and create a new engine heavily inspired by it: Bevy
(there's a forum post about this, unfortunately it got down, trying to find on web archive now)
Anyway, I wrote this little 🧵 because Amethyst looked like the future, the right way of making games, and if I couldn't make something with it, then it was because I was wrong.
Which seems pretty much the point of that article.
A good tool it's the one which solves your problems (making a game), instead of creating new ones to solve.
I couldn't make a game with ECS after many tries, I might try again later, but my dumb framework is allowing me to do a game now, and that's what matters.
Also, again, I do have a great respect for the Amethyst project, I learn a lot there, but it wasn't the tool I needed.
(I may start using engines again though, too much work 😅)
@Andre_LA too true! I use Godot over Unity because Godot just clicked with how I code and think immediately. I could get down to business fast and keep motivated and learning. I never had that aha moment with other engines, and that's okay.
Add comment