shkaboinka

4 ms·

1. 1.▲
   by shkaboinka 10y ago

   ...and if you're brave enough, think about how Christopher Alexander's philosophy of "unfolding wholeness" applies so much more to an AST than to the stack-machines of the 1960's: https://youtu.be/98
2. 2.▲
   by shkaboinka 10y ago

   I believe that switching to a stack machine is short-sighted and a big mistake: The AST format could open up new possibilities for software, some of which are observable in Lispy languages like Scheme (I won't list them here). Instead,
3. 3.▲
   by shkaboinka 10y ago

   Here is a PDF of a version with an added preface with that disavowment. His reasoning (focus on human application rather than just on method itself) makes sense to me, but I'm still excited to see read the methods. https://m
4. 4.▲
   by shkaboinka 10y ago

   Alan, of you are aware of DCI, what is your response to it? It (or more specifically, Jim Coplien) claims to build on your vision of OOP, but also criticises "emergence" within the OO vision. (Personally, I think those problems ar
5. 5.▲
   by shkaboinka 10y ago

   I've seen similarities between your work (OOP) and that of Christopher Alexander (Patterns). Do you have anything to say about how your/his works tie together? (Note that Alexander's work is perhaps even more misrepresented i
6. 6.▲
   by shkaboinka 10y ago

   Trygve Reenskaug (MVC inventer ) and Jim Coplien (Patterns/Hillside) developed the DCI paradigm as a way model code around the roles played by objects, rather than the concrete type (class) of each object. video: https://www