Changing the default but keeping the configuration option is the most reasonable position. Core is right to change the default to reduce split pool miner centralization, but no code cleanup is worth this level of community discord
Login to reply
Replies (1)
it's also just bad API policy in general. i favor golang because they adhere to the rule of not breaking APIs if it can be avoided. they recently added a breaking change for the JSON encoder but you have to specify it with a /v2 at the end of the import and enable the v2 codebase in an experiment.
it's fine to make a new API for stuff, but you should retain old codebase and APIs, they have very low cost of maintenance so it isn't a reasonable action for a software project used by other people.