<div dir="ltr">I also like modern things and I am happy with all the things that are *not* being included in Swift as well.<div><br></div><div><div>I understood what you said, Lord. Sometimes I wonder who are the people that decides what is “best” and what is “correct” and what is to be encouraged or not, but I’ll not continue this discussion. We will have to agree to disagree about some points.</div><div><br></div><div>Regards,</div><div><br></div><div>-Van</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 26, 2016 at 9:34 PM, Joseph Lord <span dir="ltr"><<a href="mailto:joseph@lordweb.net" target="_blank">joseph@lordweb.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Feb 26, 2016, at 10:54 PM, Vanderlei Martinelli via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> We have a hammer and pliers. Now we invented a screwdriver, let's throw the hammer in the trash. (If it was a sonic screwdriver would be cool.)<br>
><br>
> I believe that each tool is used for a purpose. Taking the possibility of other tools just because there is a new way to another does not seem to make sense.<br>
<br>
</span>The path of including everything that is useful leads to C++ and isn't what I want for Swift.<br>
<span class=""><br>
> Otherwise, what about eliminate classes for good? What do you (plural) think? So the Swift will be fully POP. (This remember me: "POP goes my heart!" I can swear I'm listening someone singing this song here.)<br>
<br>
</span>If it wasn't for existing code and particularly Cocoa Touch I might be tempted to propose removing implementation inheritance. Even the if that was the case a reference type would still be desirable and probably necessary.<br>
<span class=""><br>
> I like POP anda I like OOP. I'd like to use both in Swift development.<br>
><br>
> Remembering that Cocoa/CocoaTouch is fundamentally made using classes and subclasses in mind. I know that Objective-C does not have abstract classes, but this is a defect, not a quality.<br>
<br>
</span>Yes they are very class based, but they are also heavily protocol and delegation based and I think that is the better pattern to encourage. The only place I can think of where there is an abstract class is in gesture recognition and I think it would be better if there was an additional delegate instead.<br>
<span class=""><br>
> Well... Maybe we have a whole new set of frameworks for OS X/iOS/watchOS/tvOS coming and I do not know?<br>
<br>
</span>Existing code will not disappear even if that does happen but that doesn't mean inheritance should be encouraged.<br>
<span class="HOEnZb"><font color="#888888"><br>
Joseph</font></span></blockquote></div><br></div>