great talk, I learned a few things, but generally I already knew most of this (having played around with bevy a few months now). Is there a talk or resource (by you or someone else) you would recommend that goes beyond this level and more into how to write ergonomic, idiomatic, maintainable, easy-to-write bevy? I *think* my main issue currently is that the code I write is too complex: Despite using small systems, ... I simply end up with many systems that are technically separate but conceptually so related that I need to have all of them in mind when I change one.
I have implemented a lite version of this dependency injection myself now. It was... an experience. Basically I wanted callback functions, but one of the parameters could have an arbitrary type parameter, and the return type could also have an arbitrary type parameter. (Bounded by traits, actually, but arbitrary enough) I think it's based on three traits and a struct wrapper... Took me a long time to even understand some of the issues that cropped up. (The most important one being the ability for a type to have multiple Fn implementations. I just didn't consider that at all and was wondering why it kept claiming my blanket impls weren't bound properly... So if you want to do something like this, keep that in mind.)
Could you please fullscreen the slides instead of putting it in a small box in the bottom left corner. It's hard/inconvenient to see the actual content.
@@MeowEngineer I'm not gen z, but ok. Maybe I don't want to zoom in on every video? Or maybe I'm using a device where I can't zoom in? Either way people seem to agree that it's not optimal to have that kind of layout, and I'm just trying to provide some feedback.
Chris, we need a fine-tuned LLM for Bevy development. And after fine tuning, further refining using constitutional AI / RLHF. Then a voice integration - so we can just talk our systems. Curious about when to implement a Command versus just another function for the reusable aspects?
Fairly experienced with rust. Know nothing about bevy besides what it is. Took almost nothing useful away from this talk. Seemed like a bunch of gibberish jumping around. But maybe that's just me and it was meant for someone with a different background
it's probably aimed at people coming from something else and completely new to rust and ecs. I agree you'll get nothing of actual value besides of an okay overview of what you're going to be working with. Think about people with their entire careers resolving around c# and oop... or java. For them, seeing this is surely mind blowing.
great talk, I learned a few things, but generally I already knew most of this (having played around with bevy a few months now). Is there a talk or resource (by you or someone else) you would recommend that goes beyond this level and more into how to write ergonomic, idiomatic, maintainable, easy-to-write bevy? I *think* my main issue currently is that the code I write is too complex: Despite using small systems, ... I simply end up with many systems that are technically separate but conceptually so related that I need to have all of them in mind when I change one.
That was a great talk! Very easy to follow even for people like me who never heard about bevy.
glad you enjoyed it!
Great talk!
Great talk Chris!
🙌
Exactly what I was looking for. Thank you!
great talk, I learned a few things, but generally I already knew most of this (having played around with bevy a few months now). Is there a talk or resource (by you or someone else) you would recommend that goes beyond this level and more into how to write ergonomic, idiomatic, maintainable, easy-to-write bevy?
I *think* my main issue currently is that the code I write is too complex: Despite using small systems, ... I simply end up with many systems that are technically separate but conceptually so related that I need to have all of them in mind when I change one.
I learned a lot, thanks Chris!
I have implemented a lite version of this dependency injection myself now. It was... an experience.
Basically I wanted callback functions, but one of the parameters could have an arbitrary type parameter, and the return type could also have an arbitrary type parameter. (Bounded by traits, actually, but arbitrary enough)
I think it's based on three traits and a struct wrapper... Took me a long time to even understand some of the issues that cropped up.
(The most important one being the ability for a type to have multiple Fn implementations. I just didn't consider that at all and was wondering why it kept claiming my blanket impls weren't bound properly... So if you want to do something like this, keep that in mind.)
Could you please fullscreen the slides instead of putting it in a small box in the bottom left corner. It's hard/inconvenient to see the actual content.
Don't be cheap and just get UA-cam Premium. Then you can just pinch to zoom.
@@MeowEngineer I already have UA-cam premium.
@@MeowEngineer I'm not gen z, but ok. Maybe I don't want to zoom in on every video? Or maybe I'm using a device where I can't zoom in? Either way people seem to agree that it's not optimal to have that kind of layout, and I'm just trying to provide some feedback.
@@MeowEngineer And this is why I'll never pay for youtube from principle, hiding zoom behind a paywall...
There's plenty of alternative clients.
0:06 nice try chris, but there's no 'h' in ayup... great presentation, I'm learning a lot from your knowledge of rust.
a parenthasee a parenthado
Chris, we need a fine-tuned LLM for Bevy development.
And after fine tuning, further refining using constitutional AI / RLHF.
Then a voice integration - so we can just talk our systems.
Curious about when to implement a Command versus just another function for the reusable aspects?
If you are looking for how bevy’s Query system implemented, this may be a wrong place😂 to start
Fairly experienced with rust. Know nothing about bevy besides what it is. Took almost nothing useful away from this talk. Seemed like a bunch of gibberish jumping around. But maybe that's just me and it was meant for someone with a different background
I have the same feeling. I learned little about ergonomics…
it's probably aimed at people coming from something else and completely new to rust and ecs. I agree you'll get nothing of actual value besides of an okay overview of what you're going to be working with. Think about people with their entire careers resolving around c# and oop... or java. For them, seeing this is surely mind blowing.
Isn't he the guy that says he bans anyone who doesn't defend peedo files?
@@justanothercomment416 what is peedo files?
@@user-93fekod1o sound it out
great talk, I learned a few things, but generally I already knew most of this (having played around with bevy a few months now). Is there a talk or resource (by you or someone else) you would recommend that goes beyond this level and more into how to write ergonomic, idiomatic, maintainable, easy-to-write bevy?
I *think* my main issue currently is that the code I write is too complex: Despite using small systems, ... I simply end up with many systems that are technically separate but conceptually so related that I need to have all of them in mind when I change one.