Difference between revisions of "Composability"
Jump to navigation
Jump to search
(Created page with "Compositionality is the essence of Category Theory, and the whole point of creating PKC to ensure that one can leverage the mathematical insights of Category The...") |
|||
| (12 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Compositionality]] is the essence of [[Category Theory]], and the whole point of creating [[PKC]] to ensure that one can leverage the mathematical insights of [[Category Theory]] to construct and evolve [[PKC|personally-owned Knowledge Container]]s. | [[Compositionality]] is the essence of [[Category Theory]], and the whole point of creating [[PKC]] to ensure that one can leverage the mathematical insights of [[Category Theory]] to construct and evolve [[PKC|personally-owned Knowledge Container]]s. Mathematically, it is conceptualized as a form of [[universal construction]], and in software engineering, it is often realized through [[universal data abstraction]], such as [[monad]]. In hardware, it is achieved by modeling hardware system as some compositions of a specific [[universal component]]s, such as [[Nand]] or [[Nor]] logic gates. | ||
=Industrial Application of Compositionality= | |||
#[https://www.infoq.com/interviews/erik-meijer-linq/ LINQ] designed by Eric Meijer, is based on [[Monad]]<ref>{{:Video/Don't fear the Monad}}</ref>. Meijer is a proponent of applying theoretical models to software design. His opinions can be found in this video<ref>{{:Video/Category Theory, The essence of interface-based design}}</ref><ref>{{:Video/Alchemy For the Modern Computer Scientist - Erik Meijer}}</ref>. | |||
#[[OutSystems]] is a full stack software development platform that claims to have integrated the most layers or aspects of software development. This idea requires the notion of [[compositionality]] to reduce complexity. | |||
<noinclude> | |||
=References= | |||
<references/> | |||
==Related Pages== | |||
*[[has LogicModel::PKC DevOps]] | |||
[[Category:Category Theory]] | |||
[[Category:Universal property]] | |||
[[Category:Composability]] | |||
[[Category:Continuation]] | |||
[[Category:Hyperlink]] | |||
</noinclude> | |||
Latest revision as of 15:12, 9 September 2021
Compositionality is the essence of Category Theory, and the whole point of creating PKC to ensure that one can leverage the mathematical insights of Category Theory to construct and evolve personally-owned Knowledge Containers. Mathematically, it is conceptualized as a form of universal construction, and in software engineering, it is often realized through universal data abstraction, such as monad. In hardware, it is achieved by modeling hardware system as some compositions of a specific universal components, such as Nand or Nor logic gates.
Industrial Application of Compositionality
- LINQ designed by Eric Meijer, is based on Monad[1]. Meijer is a proponent of applying theoretical models to software design. His opinions can be found in this video[2][3].
- OutSystems is a full stack software development platform that claims to have integrated the most layers or aspects of software development. This idea requires the notion of compositionality to reduce complexity.
References
- ↑ Beckman, Brian (Nov 21, 2012). Brian Beckman: Don't fear the Monad. local page: jasonofthel33t.
- ↑ Meijer, Erik (Sep 10, 2015). Category Theory, The essence of interface-based design - Erik Meijer. local page: FooCafe Youtube Channel.
- ↑ Meijer, Erik (Jun 5, 2018). Alchemy For the Modern Computer Scientist - Erik Meijer. local page: FooCafe Youtube Channel.