Re: Why I believe that using class based prototyping is suboptimal
On Sat, Dec 16, 2017 at 4:05 PM, vitalije wrote: > As I promised in other thread few days ago, that I will write in more > detail about what I believe to be a better way to make prototype, I am glad > to report that text is on the web. > Not the best time for me to read or respond directly. I need a break from this week's intense work. Both my thumbs are sore, but not too sore to summarize from what I have done. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Why I believe that using class based prototyping is suboptimal
Hi, Thanks for your post. On 17/12/17 08:44, vitalije wrote: > > I read all three parts and found it interesting, although it wasn't > > Thank you very much for your effort and feedback. > > > So I guess after reading both pieces I get your point more - avoid > constructing complex state to manage something that is essentially a > process. At least I think that's what your saying :) > > Yes, that's what I wished to say. > This conversation remembers me Programming Across Paradigms, by Anjana Vakil: https://www.youtube.com/watch?v=Pg3UeB-5FdA Now that functional programming is getting a new impulse, is interesting to see the continuum that this talk is proposing. Dealing with global state and a lot of intertwine in a mechanical clockwork alike fashion makes development complicated. Functional and Objects keeps state confined, the first in more aggressive way (i.e only in particular IO monad) and the second by keeping it inside small objects that communicate only through messages that makes easy to reason about state (at least in the Pharo/Smalltalk case). Its interesting how the talk invites us to use the proper paradigm to think about the problem, instead of looking everything from the same paradigm and force the problem to fit it, that I think shared Vitalije idea of avoiding complex state to model what is essentially a process (a core proposal of functional programming and the metaphor of the assembly line used by Anjana and Richard Hickey). In my case, despite of using exclusively Pharo now for my programming/modeling, I try to get as much inspiration as I can from other communities and paradigms (indie video gamers, clojure, music live coding, this community). I think that this broader panoramic and experience improves my coding, even despite of happening only inside Pharo, so thanks Vitalije and Terry for the talk :-). Cheers, Offray -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Why I believe that using class based prototyping is suboptimal
On Sun, 17 Dec 2017 05:44:34 -0800 (PST) vitalije wrote: > I agree, contrasting code examples would show more. I was feeling > uneasy about criticizing Leo's code base too explicitly. I'm not sure if Leo is the best example to make the comparison, a more self contained example might make the comparison accessible for a larger audience. > However, I feel that I need some tool for documenting process. There > are lot of screen recording tools, but I want something more specific. Leo has a slide show / demo functionality, and also screen-capture-now and screen-capture-5sec, which screen cap. the Leo window to .leo/screen_captures. There's no feedback, seeing they assume you don't want "Image saved to /home/tbrown/.leo/screen_captures/2017-12-17T09-40-53.png" visible in the log in your example images. The 5sec version fires after 5 seconds, so you can open menus etc. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Why I believe that using class based prototyping is suboptimal
> > I read all three parts and found it interesting, although it wasn't > Thank you very much for your effort and feedback. > > So I guess after reading both pieces I get your point more - avoid > constructing complex state to manage something that is essentially a > process. At least I think that's what your saying :) Yes, that's what I wished to say. Perhaps the > example would help more if there was more contrasting between one > approach and another, with only one solution explored there's less of a > feeling for the comparison being made. > I agree, contrasting code examples would show more. I was feeling uneasy about criticizing Leo's code base too explicitly. I was afraid that it may sound offensive and that was not my intention. So, I decided to just tell how I feel when reading such code, explaining about what might be found there and left the readers to look into code if they want and see for themselves. I am tempted to go right now to hunt this bug and write about my journey there. That may show in more contrast code examples and make my previous post clearer. However, I feel that I need some tool for documenting process. There are lot of screen recording tools, but I want something more specific. I have an idea how to make Leo record my work and later make video or slide show and record voice explanations. I will work on prototype of such tool next few days and if I made something useful, I will use it to make bug hunting video/slide show. In any case I will report here when ready. Thanks again for your feedback. Vitalije PS: blog doesn't support comments yet. It is brand new, domain is registered on Friday and on Saturday evening it was launched. Hopefully, comments will be enabled soon, and until then this forum is place for discussion. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
