chatman edited a comment on pull request #1684:
URL: https://github.com/apache/lucene-solr/pull/1684#issuecomment-686808345


   > Wow. I'm not even sure that would be polite to say to a junior engineer 
(that may be presumed to not know concurrency) than a very senior one here. 
   
   I don't understand your ideas of politeness, but if someone offered me 
help/advice in writing code in any area, no matter how "senior" or "junior" I 
am or he/she who is offering help is, I would be grateful.
   
   > I think you know full well that Ilan doesn't need your help writing 
concurrent code. Yet why would you offer help? I think this is a false offer 
(you know Ilan will not take you up on this); -- it's a pejorative offer that 
belittles who you offer it to as being beneath the abilities of your own. I 
wonder why you would say that? Maybe you don't believe it's worth it to make it 
easier for plugin writers at the expense of Solr having such concurrent code 
(i.e. where does the concurrency/complexity go) -- fare, but then just say that 
without belittling anyone's intelligence.
   
   Ilan is a reasonably new committer, so I am not fully aware of his 
background or his "seniority". I just offered help in writing concurrent code 
that I consider clean. But, now you have made couple of assertions that I will 
keep in mind:
   "Ilan doesn't need your help writing concurrent code"
   "Ilan will not take you up on this"
   
   
   > "pejorative offer that belittles who you offer it"
   > "as being beneath the abilities of your own"
   > "belittling [..] intelligence"
   
   Even though I won't stop you representing/misrepresenting Ilan as you have 
done above (by claiming he is not open to help in this area), at least please 
don't put misrepresent me with the motives behind my words. Just to clarify: I 
thought Ilan was inclined towards having tons of classes (and thereby 
"polluting solr-core") because he wanted to avoid having the plugins make 
concurrent requests, since I thought he perceived doing so as complicated. I am 
of course not doubting anyone's ability to write concurrent code (and of course 
not "belittling anyone's intelligence"), but I wanted to offer suggestions on 
doing so *cleanly* (without complications).


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to