Great video comparison between the two games! All your points on Unity DOTS are certainly valid, I will just clarify that components and systems can all be in the same class files, it is just a choice I make to separate them out into different files. The only things that need to be in their own files are the authoring components, which are what you put on a GameObject in the Unity editor to set the values - in the past there was an attribute that could be added to the data components to automatically generate this authoring component, but it has been removed... long story... 😐 Anyways this was such a fun experiment, I hope to have my comparison video up next Friday 😀

Thanks for the great content! just getting into rust and bevy and your channel has been great help.

Glad to see a new video out :)

Another great video thanks :)

I learnt Unity Dots from TurboMakesGames before finding your videos. But I prefer bevys ECS, it very easy to build a scene in blender then load it into bevy.

I wish you good luck finding a new Job

Good luck with the job search. Hope you get an awesome offer

5:00 im not expert at ecs, but as a user of it i think the reason he didnt place too many variables inside a component is so he can get more cpu cache hits while querying components since unity places them next to next in the memory. for example if you only wanna check health of an entity, when you have one struct named Health you can fit more health data into the cpu cache. also its easier to parallel for unity, since unity can only make system code parallel, if a component is not being writen by another system at the same time, otherwise unity have to wait for other systems to finish working on the component. also in unity ecs you have "archtypes" that lets you combine multiple components. so keeping data in seperete components, if they are not highly related and regularly queried together, is better when it comes to authoring components and gluing with gameobjects, i have never done that before i just use pure ecs, but i think for now its useful if you wanna use the editor visually other than that, you can just write pure ecs like i do

You said there could be a video on performance comparison. I wonder if linearizing memory layout in unity paid off.

I've been using Unity as my main engine and entry into programming (past text adventure games in python etc.) for around four years now, as both a hobby/interest thing and also for some school projects (programming classes etc.), and this video is quite interesting to me now that I've dipped my toes into working with Rust. I'm still very unaware of how bevy works, but all the things I love about my rust code seems to be present in your bevy game as well, which is pretty inspiring. I haven't used DOTS yet (because it untill recently was experimental etc.), and should probably give that a try, but all this video makes me feel is that I wish I could write the bevy code and work with it in a "Unity Editor" type environment. This isn't something I've tested, but I have this idea that Unity is uniquely friendly as a GUI for collaborating on games with normal people who aren't programming wizards, and that unfortunately might make it so I couldn't effectively collaborate with many amateur game devs in game jams if I was using something like bevy. What are your thoughts on this, as someone who actually has experience with it? I'll still learn bevy for the simple fact that it is the rust game engine™, just having a hard time pitching it to myself as productive for the goal of making games with other people.

Good comparison! Doesn't sound biased to me :P

it is very cool that you didint tray to be "neutral", thats makes clear the advantages of each engine, i like unity, but i love rust and i will give a try to bevy

- Structs don't require being in it's own file of the same name, it's perfectly acceptable being in a shared file like you have here as long as it makes sense organizationally. Personally, having a single file to dump components into that don't relate sounds like a nightmare to extend and refactor.

What about using other library for the UI? let's say egui, or wgpu , it's possible?

I've been thinking of using Unity lately, though I don't know if I can know both. I learned the "original" Unity back when. It was good, but just too many parts and pieces or something. But with AR, it looks like Unity is the way to go at the moment. Unity or Unreal. I wonder how much went into that integration, and what's possible using libraries today in Bevy regarding VR and AR (using various libraries). I'm especially interested in AR. That market is HUGE. So, I might be off to Unity for now. I don't want to, but I think it could be a while for Bevy to have VR/AR integration. I don't know if that's even on the plate, and is likely a BIG project. There's always some reason to use this one, or to use that one. I went went Godot at first. I think Unity is likely the best option for a real game at the moment. Unreal never interested me - didn't draw me in. Bevy drew me in, and has me sold, but it's just still early... Godot was fine. It drew me in. Had no real issues other than 3.2 was still early, but wanted 100% rust environment. Bevy is moving at lightning speed, but there's a lot of ground to cover... These Bevy developers are some kind of level beyond myself. I frankly, don't know how they do it... If they ever worked for the corps, I bet the corporate managers didn't know what they had. They usually don't.

Remember when "roguelike" wasn't more or less a synonym for "game?"

well you know cause of tribalism people are not going to be able to see to what you are saying here. but unity ecs is definitely convoluted compared to bevy. i saw a comment that said "no that's how it is c#" not understanding that the convention in c# (i have used c#) is to just stick everything into its own file, having used f# it was a breath of fresh air to be able to combine related types in modules and though I just recently started rust it seems to be similar in that regard. In c# every type (object) is in its own file stranded making you dance between a zillion different files like a mad man. i started off with c# and ecs but i think two things 1) c# is just a pretty verbose language compared to languages like f#, and 2) the ecs system is a garbled mess combining unity game objects and its actual ecs implementation. don't get me wrong unity has a lot more things going for it (minus the recent nonsense that occurred) but its ecs is nowhere near as clean and compact as in bevy. btw, as far as ui is concerned, i took a look at a library called bevy_iced which is similar to f#'s elmish, which is another plus for me. bevy just seems like all out win for me, but again. someone who is full in on c#/unity and are hardheaded refusing to step out of their echo chamber will never get to see the benefit that other languages/engines have to offer. one thing i will say that surprised me about bevy however was that the performance is not that good as i thought. maybe i had unrealistic expectations? but the idea of low-level (fast) combined with ecs (fast) made me think bevy would be super fast compared to unity.

2:40 Err no you could write your whole application in a single file in C# we just dont because its awful.

Bevy ECS does have its issues, what really killed me is the fact you cannot store a circular reference between components (I cant have 2 objects that both point to each other), plus you can only have 1 of each component on an entity leading to the need for many custom components that all hold the same type of value and serve the same purposes, and stuff along those lines but even with these quirks I feel bevy has plenty of advantages and things that make it really great to work with

3:56 EndSimulationEntityCommandBufferSystem versus..... Commands😂

bevy is code based approach, there are really2 heavy discrepancy.

Coming from an actual programmer who has worked with Rust ecs (not Bevy), Unity and Unity with DOTS: Do yourself a favor and try DOTS once. It's the difference between a toy engine and an actual workhorse. Baking/authoring is a basic requirement when composing high level elements in an editor and building a big game. Yes, dots is less suited to prototyping compared to what Bevy or old Unity were but that's like saying "dynamic type languages are better because you have to type less".

Lol, bevy code has so many problems. All these magic constansts and hardcoded values. Rust itself create a lot of visual noise from syntax - it is so harder to read. Dots has a lot of boilerplate code but it is much easy for team development because you have a lot of best practices majority of unity developers follow and bevy is not there yet.