3 ms·

One man's tech debt is another man's API stability

• deleted 3y ago
  [deleted]
• flanked-evergl 3y ago
  One man's API stability is another man's perpetual nightmare, especially if the API is bad. Things have to change to get better, and if systems are designed in a way which prevents API improvements, then you will just have perma-crap software.
  • marcosdumay 3y ago
    > perma-crap software Yeah, we are talking about Microsoft here. I guess some people will pop-up from nowhere and disagree with your rationale, but it is flawless. Everybody loves the stability anyway.
  • xp84 3y ago
    This seems an odd place to be making this argument though. Of all the things that you might do if you had carte blanche to break all backcompat in Windows, you’d really pick these reserved words? like, how important is it to make a file named just con or prn? Or a Teams channel or Sharepoint group for that matter? I’d be aiming more for something like the backslash as path separator, or eliminating all system dependencies on drive letters. (I know NTFS can mount elsewhere, but too much stuff uses and assumes drive letters.)
  • Dalewyn 3y ago
    The notion that change is always good/better is false, and change for the sake of change is terrible.
    • flanked-evergl 3y ago
      Not having the ability to change is worse than change for change sake.