I don't see it as trolling. I see it as people challenging that it is a solid topic.
People? I'm referring to Matt, no one else is trolling. I'm truly sorry if I have offended anyone. All I am asking is for feedback on a pattern. I care little about whether it is new or when it was invented. I'm using this *right now* and am reaching out to you in an attempt to understand it better, but it seems we've somehow gotten into the merits of whether or not one should define a problem in a document before doing so. This is no good. I'd rather not land myself in a similar situation again, what could I have done to better illustrate my intention to you? Now, if we could move on from this, I do have some work to do in refining the document in regards to illustrations not matching the code examples, but hopefully the definition and goal should be rather clear in this thread; i.e. it is about reducing complexity in a specific type of situation, like the one described in the document. Do also have a look at the code examples posted above for further definition. So, what about this pattern would be amazingly helpful, less helpful, and down-right unhelpful? :) Thanks. Best, Marcus On 18 April 2014 09:33, Justin Israel <[email protected]> wrote: > In an attempt to reinterpret Matt's comments to reflect my own thoughts, > the way it appears to me is that the RFC is a very abstract description of > an implementation that wraps existing concepts. It positions itself as if > it is proposing something new, but I am not clear on the existing problems > that are not properly solved, and what your idea is really aiming to > change. That would be in terms of real concrete problems that need to be > solved, instead of saying a button might need to trigger something that may > or may not exist and it may or may not require a response either now or at > some point in the future. Otherwise I am not sure what the RFC is aiming to > do. It comes across more as a brainstorm for how to write your own > implementation of some Python program, as opposed to saying there is a new > way to do something. What specific problem do you want to solve? What have > you tried that has failed to meet your needs? > That is why I feel you are receiving criticism on the topic. I don't see > it as trolling. I see it as people challenging that it is a solid topic. > Not all criticism has to include contributions that will further your > design. Sometimes some people just don't get the goal and the intent. And > that's ok. While you say sync/async is not the focus, maybe then it's not > as clear as you had hoped, if commentors are focusing on the topics you > didn't intend to discuss. > > My 2 cents. > On Apr 18, 2014 8:14 PM, "Marcus Ottosson" <[email protected]> > wrote: > >> I had to turn to your LinkedIn for this one. Clearly you are a very >> educated man, and thus I would expect someone in your position to know when >> he is trolling. You strike me as bitter, Matt, and I'm having trouble >> absorbing your opinion on this matter. >> >> >> On 18 April 2014 08:50, Matt Chambers <[email protected]> wrote: >> >>> Sorry, I'm just confused as to why your taking some concept people have >>> been doing for 40 years and making an "RFC" for it. I applaud your >>> enthusiasm though. I wish I put as much effort into documenting. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Python Programming for Autodesk Maya" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/python_inside_maya/3a3fd118-0723-4d87-b9a8-2d3095c8f193%40googlegroups.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> *Marcus Ottosson* >> [email protected] >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCq8SuanVGOAuuVhVntTn8wXL9vpw3kQSJFxQOxGLru_Q%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCq8SuanVGOAuuVhVntTn8wXL9vpw3kQSJFxQOxGLru_Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2yAtNG5UM%2Bnvc22Rs29TmUwzgxuij1Um21_eU5rx%2BnfQ%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2yAtNG5UM%2Bnvc22Rs29TmUwzgxuij1Um21_eU5rx%2BnfQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Marcus Ottosson* [email protected] -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCvqrw%2B6Ae4RQdmyDWw%2BrTPGLBCp1CSx_b5mo-hGW4v1w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
