01-15-2017, 07:37 AM
I agree, though on the other hand, it's good to talk about those issues (and vent them out), just so that someone doesn't go and spend so much time implementing something on those lines, only to be rejected because most other people don't like it / have a better idea. As long as the talking is on topic and not too time-consuming.
We are spread quite thin already, but that's pretty normal with open-source programs and voluntary work. Most of us, if not all, joined the project with some vision, wanting to do something. And either we manage to do that, or we don't; but there's no way anyone can be forced to touch a part of the code that they don't want to touch. I'm pretty sure I won't be touching any redstone-related code anytime soon. Similarly, most people don't want to bother themselves with the Lua API details, or optimizing memory usage. To each their own. We can only hope to spark interest in more new people, so that they join us with their new additions to our work.
We are spread quite thin already, but that's pretty normal with open-source programs and voluntary work. Most of us, if not all, joined the project with some vision, wanting to do something. And either we manage to do that, or we don't; but there's no way anyone can be forced to touch a part of the code that they don't want to touch. I'm pretty sure I won't be touching any redstone-related code anytime soon. Similarly, most people don't want to bother themselves with the Lua API details, or optimizing memory usage. To each their own. We can only hope to spark interest in more new people, so that they join us with their new additions to our work.