You should try reading my blog post, hopefully it will change your opinion of Protocol-Oriented programming. I would be interested to hear what you or anyone else think of Protocol-Oriented programming after reading my post.
Jon
···
On Feb 14, 2016, at 8:34 PM, zhaoxin肇鑫 <owenzx@gmail.com> wrote:
I have not read your blog. But in my opinion, what Apple called protocol programming is actually so called functional programming. It is not object programming at all. It uses protocols and structs to avoid object programming.
zhaoxin
On Mon, Feb 15, 2016 at 7:59 AM, Jon Hoffman via swift-users <swift-users@swift.org <mailto:swift-users@swift.org>> wrote:
Numerous tutorials that I have seen take a very Object-Oriented approach to the protocol-oriented programming (POP) paradigm. By this statement I mean that they tell us that with POP we should begin our design with the protocol rather than with the superclass as we did with OOP however the protocol design tends to mirror the superclass design of OOP. They also tell us that we should use extensions to add common functionality to types that conform to a protocol as we did with superclasses in OOP. While protocols and protocol extensions are arguably two of the most important concepts of POP these tutorials seem to be missing some other very important concepts.In this post I would like to compare Protocol-Oriented design to Object-Oriented design to highlight some of the conceptual differences. You can view the blog post here: Mastering Swift: POP and OOP
Jon
_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users