[
https://issues.apache.org/jira/browse/SOLR-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084016#comment-14084016
]
Yonik Seeley commented on SOLR-6315:
------------------------------------
bq. First, this class is entirely bogus the way I see it. Its javadocs are
completely unrelated to the class itself.
You know... I'm so tired of this style of communication (that seems like it has
become the norm in Lucene and is now expanding in Solr) that I almost didn't
respond. The validity of one's arguments has become conflated with the force
and aggressiveness with which the argument is made. It almost feels like it's
a wolf pack complete with alpha male. If you're not forceful and aggressive,
you risk getting steamrolled. Hand in hand with adjectives designed to make
more of an impact... "shit", "broken", "horrible","fucked up", "terrible",
"bogus", "stupid", etc...
Making strong assertions also hampers collaboration since it causes unnecessary
strong emotional attachment to initial positions
(http://en.wikipedia.org/wiki/Confirmation_bias#Persistence_of_discredited_beliefs)
We used to speak in terms of improving things, and avoided denigrating
contributions (new or past).
The history of some of these cultural changes is interesting (esp the need to
"up the ante" via adjectives... everything has become "horrible" or "completely
broken"):
http://markmail.org/search/?q=shit+list%3Aorg.apache.lucene.java-dev
http://markmail.org/search/?q=horrible+list%3Aorg.apache.lucene.java-dev
http://markmail.org/search/?q=stupid+list%3Aorg.apache.lucene.java-dev
It's also instructive to go back and look at the first time that "horrible" was
even used on the list (2004):
{quote}
> I thought that it might be a good candidate for Lucene 2 as the FSDirectory
> code is horrible and non-J2EE compliant.
Your constructive criticism is greatly appreciated!
Have a nice day,
Doug
{quote}
I'm bringing this up because I think some committers have gone down this
"supercharge all your arguments" path without consciously realizing it because
it has become more common. To those who recognize and resist taking that path,
thank you.
> Remove SimpleOrderedMap
> -----------------------
>
> Key: SOLR-6315
> URL: https://issues.apache.org/jira/browse/SOLR-6315
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: SOLR-6315.patch
>
>
> As I described on SOLR-912, SimpleOrderedMap is redundant and generally
> useless class, with confusing jdocs. We should remove it. I'll attach a patch
> shortly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
