| > You surely don't expect this to survive all future refactorings and cleanups? The Win10 bar code has been there, since October 2021, though? I don't know how frequent refactorings are (at M$FT) but given it's been there for nigh three years, I don't see how that's a relevant factor. Even _if_ it were refactored (and/or cleaned-up), it wouldn't be omitted from the release notes, right? Unless it's on the roadmap _for_ cleanup, this change to try to "disallow" the program, purely based on the program name and no other identifiers, doesn't give me (don't know about anyone else) much faith that removal would either be executed or executed well (e.g.: legacy Win code spaghetti'd to other code that they haven't changed/fixed, yet). If I were a betting person, new feature 'x' for cloud or advertising purposes would take priority over any modification[s] or clean-up/removal. In other words, there's no ROI (read: profit) in fixing their technical debt, currently, and there hasn't been for almost three years (if we go with the lifetime of the Win10 bar code existing still in the Win code-base). Why would that suddenly change? |
And it could be removed tomorrow. That's the point.