I might sometimes come across somewhat jaded with regards to adding new features. This has a lot to do with the fact that a lot of people mistake open source for "If I want a feature, you must make it". It's a lot less than it used to be, but the 20th time someone does this, you tend to get a bit blunt in your responses (Note that it's not an excuse, its a reason. You're right to notify me, or any of us, if this happens).
We're not against adding features suggested by the community (have a look at the github, we've included a lot of features that were suggested by you guys), but we like to see better arguments than "But my work flow requires this" or "I think this is nice". I want to know -why- you think this is nice or why a certain workflow would be better (or even better; state a problem and spar with us on how to improve this instead of pushing a single 'solution').
- 1
Recommended Posts
Top Posters In This Topic
44
24
14
12
Popular Days
Jul 4
15
Sep 15
15
Jul 2
14
Jul 3
14
Top Posters In This Topic
nallath 44 posts
cloakfiend 24 posts
gr5 14 posts
Blizz 12 posts
Popular Days
Jul 4 2015
15 posts
Sep 15 2015
15 posts
Jul 2 2015
14 posts
Jul 3 2015
14 posts
Posted Images
nallath 1,119
I'm not aware of such plans.
Yeah we did. But it's a lot of work to get right. We're already over our ears in work with everything, so something like this won't get a high priority. There are marlin firmware builders out there that work pretty good.
Link to post
Share on other sites
LePaul 321
Some of this may be lost in translation, as he is advising to give users what they want even if you do not find it useful I'd value his feedback given his software development background.
There seems to be a lot of resistance to the ideas suggested from the developers. I don't think that is your intention, but the way some of the replies come across, it reads that way.
Link to post
Share on other sites