Re:APL Style: Patterns/Anti-patterns
by seanmcdirmid on Sunday March 04, 2018 @12:00PM
(#16515374)
Plenty of programming problems are non-transformative, anything interactive for one. If you want to see attempts to make it transformative, there is pure FRP (not the fake kind, see Antony's Courtney's dissertation as a good example of how weird this looks at an extreme) and lenses. In either case, it feels like trying to shoe horn one solution to a problem into the wrong kind of abstraction. Much of the today's web work is also non-transformative.
[ Parent
| on HN ]
> anything interactive for one
I feel there's a misunderstanding in how you use "non-transformative" versus how I interpret it. E.g. aren't interactive charts mostly about transformations? (data => aggregation => affine transforms => render the graphics)
Re:APL Style: Patterns/Anti-patterns
by seanmcdirmid on Sunday March 04, 2018 @05:37PM
(#16517221)
Mostly? Maybe, maybe not. Every program has transformational elements, but they may or may not dominate. A rendering pipeline is, but if you are implementing a text editor, you might not be doing many transformations at all.