4 ms·

Not a great example IMO. Any accessible API is a public API once it’s released into the ether. Inevitably people build on those undocumented features (or come t

Not a great example IMO. Any accessible API is a public API once it’s released into the ether. Inevitably people build on those undocumented features (or come to expect them to exist) and it’s not sufficient for Microsoft or whoever to day “oops too bad, you built on a private API” because ultimately they would be disrupting their customers. I’m not against easter eggs though, you just have to be okay with the prospect of breaking expectations users may have in the future.

yellowapple 6y ago
> and it’s not sufficient for Microsoft or whoever to day “oops too bad, you built on a private API” because ultimately they would be disrupting their customers. Uhhh, that seems perfectly sufficient to me. Play stupid games (like relying on undocumented APIs), win stupid prizes (like watching everything break when those APIs change). Private interfaces should be used as a last resort, and with the full understanding that - being private - they have no obligation to be "stable".