Weird how you think removing features isn’t negative.

Reply to this note

Please Login to reply.

Discussion

negative means exactly removing something

it is a bad policy in software development, throws everyone off because sometimes even the feature you thought was stupid was used by a small minority who get very mad

add, never subtract, just make better features. this is how it can be that code written in #golang 12 years ago still compiles

the devs of go are the most wise computer programmers in the entire industry, not surprising when the most senior in charge invented the precursor to C and another built the operating system that basically everything now is (ken thompson and rob pike) they had decades of experience to learn this stuff and tehy are salty bastards about it for good reason, this modern "upgrade every other day" shit is so toxic to user experience, eventually they burn their entire loyal userbase

First, let's not put words in my mouth. 👍

Second, filtering types of data is objectively removing a feature. Filters are objectively negative things. Not in the "oh my feelings way", they often have positive effects, but they are negative features.

Often times, removing features is a good thing. Especially if it is unused, broken or unwanted.

Since this is not a consensus change, it should be noted that we have time to evaluate the damage and reverse it. We can all switch to knots or do something else if it has negative effects.

I know it's not that simple, but when shit is hitting the fan, that's when people get serious.

Removing a feature from the mempool policy (Removing the ability for them to set parameters on the OP_RETURN) is not the same as a node runner applying a filter. These 2 examples are not comparable one is removing the ability to set a limit, the other example is applying a limit.

Agreed. Didn't realise you were talking about that.

Yes, I agree that removing this optionality, especially when people are using it, is bad.