4 ms·
he already did... https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Origin%3A-Facts https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Ori...
by jd3 11y ago
he already did...
https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Origin%3A-Facts https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Ori...
- cpeterso 11y agoInteresting. He still hasn't answered why a user should pick one or the other. If he wanted to focus on refactoring and larger features, he could have enlisted a "lieutenant" to manage bug fixes and releases while he works in a dev branch. The uBlock "brand" had quickly become the "new, memory-efficient ad blocker", but now the brand has been divided and muddied. This seems like a good example of the problems with 'product line extension', where a new extension should have used a new name. https://en.wikipedia.org/wiki/Product_line_extension https://en.wikipedia.org/wiki/Product_line_extension
- jd3 11y agoI don't understand why he doesn't just re-po the repo (ha) from the guy he gave it to. it would solve the strange monetization problem and fix the schism the two projects have created for end users.