Paul Haddad

@tapbot_paul More like it forces you to think about potential issues. Subclassing hasn’t been banned, you just have to add a single keyword.

@davbeck Apple doesn’t add that keyword to a class in some new framework, now what?

@tapbot_paul @davbeck Apple changes the base class you had overridden and now your app is broken. Now what? https://en.wikipedia.org/wiki/Fragile_base_class …

@NachoSoto @davbeck I fix the app and re-ship, or I don’t. Not really any diff than whatever other bits they break in every OS release.

@tapbot_paul @davbeck how about not writing bugs in the first place? If we always fix bugs my introducing new ones, we'll never finish.

@tapbot_paul @davbeck if Apple knows there's no workaround for their bugs, maybe they'll get better at shipping quality software.

@tapbot_paul Well, apparently the core team never had to write software against Apple frameworks. They have no idea how buggy they are.

@tapbot_paul It seems like a lot of recent decisions are justified “it’s no so bad because you can just go and ask the vendor to fix it”.

@tapbot_paul Ugh. Sounds quite Java-ish

@tapbot_paul nobody is *banning* subclassing. Just better defaults IMO.

@daniel_duan @tapbot_paul This will raise the cost of developing software, and make bugs last longer. That’s the issue at stake here.

@tapbot_paul @Freerunnering but they rejected the non-subclassability proposal for now, didn't they?

@H2CO3_iOS Good heavens, no! Cross-module subclassing will be off by default. In this second review, we’re just arguing about the details.

@lorentey ah, then I misinterpreted Lattner's wording.