Joe Groff

@jckarter @bsneed @colincornaby If it truly “doesn’t affect end users at all,” what could be the point of the change?

@mjtsai @bsneed @colincornabyhttps://twitter.com/jckarter/status/755149856994316288 …

@jckarter Right, but presumably you expect that to ultimately benefit end users (indirectly).

@mjtsai They don't have Apple's resources to deal with all the backward-compat testing to cope with unconstrained subclassing and patching.

@jckarter @mjtsai Ehhhhh. It's never been a huge problem for me, I mean, we have test rigs for this sort of thing, but we work it out.

@jckarter @mjtsai For a lot of stuff like view controllers it's a built in assumption. But I was ok with just marking final.

@jckarter @mjtsai (We also have a lot of tests around it, but again, we'd mark final where we didn't want subclassing.)

@jckarter @colincornaby seems like it does to me. there's lots of swift frameworks already, many with objc compatibility built in.

@bsneed @colincornaby They're also mostly OSS, and hopefully move faster than Apple. Going from closed to open is a compatible change.