3 ms·

system management What does that mean? concurrency Some data structures and databases deal with concurrency.

nkrisc 6mo ago
In this case systems are the S of ECS and contain all your game logic, acting upon the entities and components (E and C). By system management I assume they mean the APIs bevy offers for scheduling and sequencing systems and events so your game logic remains modularized while still running in the correct order.
- fluffybucktsnek 6mo ago
  Exactly this.
- CyberDildonics 6mo ago
  It seems like you're calling an entire game engine "ECS". I'm not sure what the point is here, the whole question was what justifies having a 50 MB hello world binary. It doesn't matter what you put into a data structure, the data structure itself shouldn't make 50 MB binaries.
  - fluffybucktsnek 6mo ago
    No, they aren't calling the entire game engine "ECS". Entity-Component-System is an architecture that Bevy is structured around. As I have previously stated, I wouldn't blame the data structures used behind Bevy just yet, given Rust's tendency for making bloated binaries. What is taking the most space in this 50MB binary? How does it scale with the complexity of the application?
    - CyberDildonics 6mo ago
      Even if you can put a function pointer into a data structure, that's still just a data structure.
      - fluffybucktsnek 6mo ago
        I don't know where you are trying to go with this logic. You still haven't assured that the 50MB is actually related to data structures used behind by bevy, lest you are insunating that the data structures used by bevy are solely responsible for that size, which is not what the post claims.
        CyberDildonics 6mo ago
        You should probably read the whole thread. You jumped in half way through and got all mixed up.
        fluffybucktsnek 6mo ago
        I know the thread. Your point is about whether Bevy's "data structure" is worth 50MB. I pressing on the fact that you haven't shown what this 50MB actually are. But, out of curiosity, do you also consider the Linux Kernel also a data structure?
        CyberDildonics 6mo ago
        I pressing on the fact that you haven't shown what this 50MB actually are. To be clear you think an ECS implementation is 50 MB? But, out of curiosity, do you also consider the Linux Kernel also a data structure? Do you think a spreadsheet the holds function pointers is a kernel?
        fluffybucktsnek 6mo ago
        > To be clear you think an ECS implementation is 50MB? No. > Do you think a spreadsheet the[sic] holds a function pointer is a kernel? Do you think an entire engine, including its system scheduler, is a spreadsheet? If so, shouldn't be hard to apply the same argument to any kernel. Of course, it all relies on your definitions and sense of reductionism.

In this case systems are the S of ECS and contain all your game logic, acting upon the entities and components (E and C). By system management I assume they mean the APIs bevy offers for scheduling and sequencing systems and events so your game logic remains modularized while still running in the correct order.

fluffybucktsnek 6mo ago
Exactly this.
CyberDildonics 6mo ago
It seems like you're calling an entire game engine "ECS". I'm not sure what the point is here, the whole question was what justifies having a 50 MB hello world binary. It doesn't matter what you put into a data structure, the data structure itself shouldn't make 50 MB binaries.
- fluffybucktsnek 6mo ago
  No, they aren't calling the entire game engine "ECS". Entity-Component-System is an architecture that Bevy is structured around. As I have previously stated, I wouldn't blame the data structures used behind Bevy just yet, given Rust's tendency for making bloated binaries. What is taking the most space in this 50MB binary? How does it scale with the complexity of the application?
  - CyberDildonics 6mo ago
    Even if you can put a function pointer into a data structure, that's still just a data structure.
    - fluffybucktsnek 6mo ago
      I don't know where you are trying to go with this logic. You still haven't assured that the 50MB is actually related to data structures used behind by bevy, lest you are insunating that the data structures used by bevy are solely responsible for that size, which is not what the post claims.
      - CyberDildonics 6mo ago
        You should probably read the whole thread. You jumped in half way through and got all mixed up.
        fluffybucktsnek 6mo ago
        I know the thread. Your point is about whether Bevy's "data structure" is worth 50MB. I pressing on the fact that you haven't shown what this 50MB actually are. But, out of curiosity, do you also consider the Linux Kernel also a data structure?
        CyberDildonics 6mo ago
        I pressing on the fact that you haven't shown what this 50MB actually are. To be clear you think an ECS implementation is 50 MB? But, out of curiosity, do you also consider the Linux Kernel also a data structure? Do you think a spreadsheet the holds function pointers is a kernel?
        fluffybucktsnek 6mo ago
        > To be clear you think an ECS implementation is 50MB? No. > Do you think a spreadsheet the[sic] holds a function pointer is a kernel? Do you think an entire engine, including its system scheduler, is a spreadsheet? If so, shouldn't be hard to apply the same argument to any kernel. Of course, it all relies on your definitions and sense of reductionism.