3 ms·
> Nobody is holding them to anything I don't get this argument. Part of sharing your work is making sure what you put out is actually helpful to people. If the
by omegalulw 5y ago
> Nobody is holding them to anything
I don't get this argument. Part of sharing your work is making sure what you put out is actually helpful to people. If they remove features people really like, then the library won't be as helpful - so it's perfectly fine for the OG devs to maintain this feature. The same thing with "scrambling" to fix - that could be because a sword is hanging over your head, or because you care about the people who use your work. Thinking this way, I can perfectly see them working hard to fixing this bug.
- manquer 5y agoIt is still a choice you make, do you want to be nice and do everything anyone asks of you ? Or stick to your principles and build only what you think is right? Developers are social creatures like anyone else and like validation and recognition from peers, that is understandable but not an excuse. It is no different from being able to say no when your boss ask you to build something you don't believe in or is against your morals, it is tough but our choice nonetheless. Their choice then to support this feature, and now to patch it. They could have no either time, no point in complaining about it after making the choice.
- phkahler 5y ago>> Part of sharing your work is making sure what you put out is actually helpful to people. No, people get to decide for themselves what is helpful to them. Assuming developers want to make the best tool they can, they still have to do so within the resource constraints they have. Dropping a feature or ignoring requests is part of that.