Children, this is the picture of “XML”. Document Markup Language. It was used by the end of the XX-th century.
This was a post from May 2015. Unfortunately it is still actual in May 2018.
This probably applies to you. Especially if you are an Developer. Or if you suspect you might be a .NET Lemming? (A member of any large group following an unthinking course towards mass destruction)
.NET and SharePoint in particular are two likely offenders here. It is now 2015 (May) … Oops? It is already 2018, May.
I have found some time to do it properly at last. If this is all news to you please start from here. the beginnings and motivations are described here.
Classification of patterns of usage aka “Shapes”
Sounds very pompous. But it seems it is not and it is very useful to understand how to use dbj.cond effectively. Just click on the image to jump to dbj.cond shapes catalog,
Click for dbj.cond() Shapes catalog
For the ones wondering why would anybody think of if-then-else , I might suggest to start from Wikipedia introduction to the issue.
There are 2 NPM packages one GitHub project and one JSFiddle so far.
I am currently in the stage of searching for simple but valid examples of CallStream validity (aka: usefulness) as interfacing concept and programming idiom.
Leonhard Euler
And, I think I have found one. CallStream + project Euler. The mathematical nature of some computational problems make them a great fit for the functional paradigm. For those of you who don’t know, “Project Euler is a series of challenging mathematical/computer programming problems…” (ProjectEuler.net). I have concluded I could use the simple and interesting solution for a problem from “Project Euler” to show CallStream in action. Continue reading “CallStream + project Euler”
