TJ Usiyan

@griotspeak @mpweiher Making it explicit will inevitably prevent some workarounds from being possible. Can’t foresee where bugs will be.

@mjtsai @mpweiher that is unfortunate. Subclassing a type not meant to be subclasses is also unfortunate.

@griotspeak Subclassing a type not intended for it may be unfortunate, it may be necessary/desirable. Either way it is fixable. @mjtsai

@mpweiher @mjtsai I simply believe that vendors who don't explicitly open their classes should received increases pressure to *fix* them

@mpweiher @mjtsai This should lead to them opting into subclassing (well done or otherwise) or fixing their types.

@mpweiher @mjtsai If the vendor does *neither* then they are **truly** terrible vendors and the language should *not* cater to them.

@griotspeak "I'll throw myself off a cliff in order to force the vendor to install safety nets" doesn't appeal as a sound strategy. @mjtsai

@griotspeak Empirically it is: dynamic OO is the recipe for arguably the most successful application toolkit in the history of computing.

@mpweiher All because of subclassing? I've encountered examples of discovering after the fact that some API wasn't meant for subclassing

@griotspeak Who said 'all'?? Please leave the straw men at home.