I had kind of forgotten about bevy since the updates rolled in less frequent. Nonetheless, a lot of progress has been made since. Cool to see it's still kicking!
I really want Bevy to win in the long-run, but compilation time and binary sizes need work. I remember doing a dive into this myself but I got lost quick.
It might be worth looking again. I've been trying it out over the past several weeks and used it for a couple of game jams. Incremental builds were snappy. The first builds took a couple minutes, but it was nothing compared to the last time I used unity.
The last unity jam games I contributed to clustered in the 7-12 Mb range for their browser playable versions, and 23 Mb for the one we published as a windows download because unity's html5 export was too janky for us to fix it within the jam timeframe. IIRC we used C# for those.
ramones | a day ago
I had kind of forgotten about bevy since the updates rolled in less frequent. Nonetheless, a lot of progress has been made since. Cool to see it's still kicking!
I really want Bevy to win in the long-run, but compilation time and binary sizes need work. I remember doing a dive into this myself but I got lost quick.
hoistbypetard | 23 hours ago
It might be worth looking again. I've been trying it out over the past several weeks and used it for a couple of game jams. Incremental builds were snappy. The first builds took a couple minutes, but it was nothing compared to the last time I used unity.
The two games I made weighted in at around 23 Mb for one that used 3d features and around 16 Mb for one that didn't in browser-playable form.
The last unity jam games I contributed to clustered in the 7-12 Mb range for their browser playable versions, and 23 Mb for the one we published as a windows download because unity's html5 export was too janky for us to fix it within the jam timeframe. IIRC we used C# for those.
Bevy is a lot more fun to work with, IMO.