2 ms·
It's competitor, Amethyst, fails to build on Linux with current Rust. I think it's something to do with outdated dependencies of winit running into namespacing
by Macha 6y ago
It's competitor, Amethyst, fails to build on Linux with current Rust.
I think it's something to do with outdated dependencies of winit running into namespacing issues with macros that were added to the standard library
- yazaddaruvala 6y agoI was under the impression that Amethyst was not a competitor. There was a post stating Amethyst was basically in need of a re-architecture that could never be resourced and because Bevy was already based on that “new” architecture it was easier to switch all development effort over. But maybe this thread is out of date. https://community.amethyst.rs/t/bevy-engine-addressing-the-elephant-in-the-room/1645 https://community.amethyst.rs/t/bevy-engine-addressing-the-e...
- Macha 6y agoCertainly that rewrite was huge, and it is currently "mostly complete", but Bevy launching when it did helped stifle a lot of the momentum. However, it was picked back up again in November and is now mostly complete: https://github.com/amethyst/amethyst/issues/2517 https://github.com/amethyst/amethyst/issues/2517 From outside at this point, the rewrite looks like a mistake , given the lost momentum and the current state of the project, but maybe when they finally get it out it'll turn out differently in 6 months.
- royjacobs 6y agoThis may come off as snarky, but as long as I've been following Rust and Amethyst the latter seems to always be in some kind of "not quite there yet but it will be after the next rewrite/rearchitecture". Same goes for Conrod, its GUI library. It seemed like an inevitability that some other library would come along that would move forward a bit quicker.