Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Using ECST (or derived) as production ready #12

@julien1619

Description

@julien1619

Hi,

I'm a french developer and I watched your presentation at CppCon last year about an ECS using template meta-programming, it was really great! Based on what you said and presented, we've started to write a small game for iOS and Android. This game is currently in production and I'm thinking about updating our ECS to be closer to what you did here, and eventually contribute to it by forking and Pull Requesting.

So, I would have a few questions about it, and I thought it was convenient to put it here (maybe should I've split these in two issues):

  • Do you think there are any major issues that could prevent it from being used in production? I'm aware it's still WIP, but as it's a small project I'm working on, it's not an issue if, for example, API have to change from time to time.
  • I don't know yet if the full engine we're writing (SDL2, Bullet, ...) we'll be released as Open Source, but it's possible. As you used an AFL v3 license, that I didn't even know it existed, is there any problem using ECST or something derived from that, whether or not we're releasing it as Open Source? From what I read, it's more or less the same thing as the MIT license.

Thank you very much!

Julien

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions