The workload of the devs is irrelevant for suggesting and discussing features - people shouldn't hold back on discussions. The more something is discussed, the more mature the feature suggestion gets, the easier it will get to implement - particularly if many the "ifs and buts" use-cases are considered early on, at the non-technical level. Which features that actually do get implemented and the priority order is a different story - everyone is a volunteer, so there will always be a bias towards feature suggestions that a certain dev find fun, interesting or useful. Ideally our devs should enjoy themselves while implementing something, as it is something they do on their free time as a hobby.

I agree that developer workload should not be a factor in suggesting features. Also, this isn't even an actual feature suggestion, it's a discussion along the lines of the boldfaced "should we do this?". Developer workload absolutely can be a factor (even a large factor) in deciding which features actually do get implemented, but that too has to at some level be weighed against the proposed feature's usefulness. Even an extremely complex feature can be worthwhile to implement if it provides great value, whereas an extremely simple feature might still be decided against if it doesn't provide any value (or even provides negative value, as the case can be). Discussing what would be the value of some given functionality is an integral part of deciding if implementing that functionality is worthwhile.

I know It's irrelevant, but he wanted feature like automatic deletion. We want to have that also but we can't work soo fast for lackness of programmers. That was the main reason of saying that. And I mention it but didn’t clarify cause I always believe that seniors can understand "things" easily.

And if they "chose" easier language (like Node.JS, Django), than lot of people might help

Especially for an open source project, the beauty of having a discussion out in the open about whether or not some particular kind of functionality should exist (or even a more detailed feature request) is that if someone comes across this half a year, a year, two years from now and it isn't yet implemented, and said person thinks it's a neat idea that they would be willing to put some time and effort into, they can do it. However, if the publicly visible consensus is "that's a really bad idea and here are a dozen reasons why that's so", that person will probably realize that if they want to contribute code to Codidact/QPixel, there are things that are probably a better idea to work on and would be more likely to be positively received by the core developers even if they themselves think it would be a cool thing to add.

(All that regardless of the current developer workload and regardless of the specifics of the idea in question.)

deleted user