simon/post-scarcity
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Updated regularity (markdown)

Simon Brooke 2019-01-23 22:24:11 +00:00
parent 7cae954640
commit 15388ed0db
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
regularity.md

@ -5,7 +5,7 @@ A regularity may also have an association of methods, that is, functions which a
But, for example, if we have a regularity whose members represent companies, and those companies each have employees, then there might be a method `:payroll` of companies which might internally look like:
```
(defun payroll (company)
(lambda (company)
(reduce + (map do-something-to-get-salary (:employees company))))
```
@ -17,4 +17,6 @@ which would be accessed
(companies:methods:payroll acme))
```
But salary is not a property of a company, it's a property of an employee; so what is this thing called `do-something-to-get-salary`? It's a method on the regularity of employees, so in this example, is is `::shared:pool:employees:methods:salary`.
But salary is not a property of a company, it's a property of an employee; so what is this thing called `do-something-to-get-salary`? It's a method on the regularity of employees, so in this example, is is `::shared:pool:employees:methods:salary`.
There are issues that I haven't resolved yet about the mutability of regularities and homogeneities; obviously, in order to provide multi-user visibility of current values of shared data, some regularities must be mutable. But mutability has potentially very serious perfomance issues for the hypercube architecture, so I think that in general they should not be.