4 ms·
>Then there's support for reactive programming, which is still in its infancy State management for UI I would think should be a first class objective rather th
by WhitneyLand 4y ago
>Then there's support for reactive programming, which is still in its infancy
State management for UI I would think should be a first class objective rather than 3rd on the todo list. See SwiftUI for something evolving toward this direction.
>The best way to illustrate the advantages of functional/relational programming over OOP is through a case study
No, the best way is to be right up front with a real life common problems and code examples that make life better. I’d prefer not to read this many dry theoretical pages before seeing any of those.
- mathgladiator 4y agoI'm curious what kind of examples would be compelling. I'm writing a language which takes exceptional control over state (https://www.adama-platform.com/ https://www.adama-platform.com/) And im having a bunch of fun with it now that I popping up the stack in UI. My docs have a minimal tic-tac-toe ( http://book.adama-platform.com/examples/tic-tac-toe.html http://book.adama-platform.com/examples/tic-tac-toe.html )
- pavon 4y ago> real life common problems and code examples that make life better That is exactly what a case study is. Looking at examples of real world cases.
- WhitneyLand 4y agoNo it’s not. Case studies are usually retrospective. That’s not very practical when a language is in the design/implementation stages. It is possible to present common problem scenarios and examples up front, even if something is at the idea stage. It’s commonly done, and can be an effective way of conveying your ideas and getting feedback without pages on end of speculative requirements.