4 ms·
Forking is a huge resource sink, if it goes anywhere at all. It disrupts network effects that software benefits from. It is, if nothing else, leaving a local m
by andrewflnr 3y ago
Forking is a huge resource sink, if it goes anywhere at all. It disrupts network effects that software benefits from. It is, if nothing else, leaving a local maximum of utility for everyone. In short, it's inconvenient, if not actually painful and heralds future inconvenience/pain. Anger may not be wise, depending on the specifics, but it should absolutely not be surprising.
- thesuperbigfrog 3y agoForking might be seen as a form of protest against the current leadership or their failure to address the needs and concerns of the community. If the community does not agree with the leadership's actions (or failure to act) then a fork might be a possible road ahead. Compare: OpenOffice - LibreOffice Jenkins - Hudson MySQL - MariaDB and many others.
- andrewflnr 3y agoWell yes, I assume this is basically a protest, but it's only effective as such because of all the pain stuff. If forks were easy, they wouldn't be notable, and the (threat of) willingness to endure pain is a strong signal of the pain a group is already suffering. Anyway, "it's a protest" is pretty much sufficient in itself to answer the original question of why people might get angry about it. :P
- unaindz 3y agoOpenwrt - LEDE, which got merged again into openwrt
- solarkraft 3y agoNo fork: No change.
- SSLy 3y agoCompare and contrast your opinion with EGCS