4 ms·
> suddenly not only does that accounting system no longer work sigh.. have i suggested anywhere to suddenly make releases with features removed? does everybod
by keymone 7y ago
> suddenly not only does that accounting system no longer work
sigh..
have i suggested anywhere to suddenly make releases with features removed? does everybody in this thread have a mental blocker on the word "deprecation" or something?
there are ways to remove features properly and gradually. deprecation warnings, hiding the feature behind deprecation flag, moving the feature out into a plugin, etc.
i honestly wasn't expecting to have to respond to such strawman comments.
- astine 7y ago"have i suggested anywhere to suddenly make releases with features removed?" Yes you clearly did: "legacy code and backwards compatibility are dumb excuses to not cleanup the codebase and make bad practices like those listed impossible." "...it shouldn't be part of postgres..." ""not giving a shit that somebody's 20 year old codebase breaks on today's version of $project"."
- keymone 7y agoGood job selectively quoting only the bit following right after “deprecation” stuff.
- astine 7y agoJust because you also listed deprecation doesn't mean that you didn't also list removing features and not caring about the existing user base. You didn't clarify which was the better option so it's hard for me to parse this as anything but an endorsement of suddenly removing features and I suspect that's what other people are seeing as well. If you have any doubt about this, look at your comments. You have one comment only mentioning deprecation and that one has no downvotes but the later ones which mention removing features do. If you didn't mean to say that, I would suggest editing the comment or at least clarifying what you meant.