Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too much purity, not enough ageism #413

Closed
tonymorris opened this issue Jul 2, 2013 · 1 comment
Closed

Too much purity, not enough ageism #413

tonymorris opened this issue Jul 2, 2013 · 1 comment

Comments

@tonymorris
Copy link
Member

@tonymorris tonymorris commented Jul 2, 2013

As we have recently learned from our self-proclaimed experts, misogyny is out and ageism is in. In particular, it has come to our attention that "young communities tend to be arrogant." Let us consider the very real-world, pragmatic consequences of this astute observation[^1]. This means that of our 15 or so contributors, we must remove those who are of that age that I wish I was; you know, 21 and all bouncy. Sorry guys, you are contributing to the arrogance that we do not wish to publicly display (haha, get it?). Spend a bit more time in the world and let us know how you go. Ageism is the new misogyny, woot woot! We are an accepting community, especially of new standards that benefit everyone, especially me. See you on the other side of 30 guys, sorry!

Also, I think we have too much purity. As we have also learned, the benefits of purity are a myth. All those people who happen to have a grasp on the subject matter were wrong. No this does not include you[^2]. As a result this new wisdom, I think there is a bug in the Cofree data type. These are not as useful as everyone keeps pretending they are.

Instead, we should rename Cofree to AbstractTransactionAwarePersistenceManagerFactoryProxy which has a more pragmatic, reasoned trade-off between purity and real-world application. Further to this, we should remove the recursion from Cofree and instead write a user-guide on how to use loops in Scala. Perhaps the biggest benefit of this rename is that lazy people are more likely to learn Haskell. This is because of the accepting and warm nature of the new data type. However, let us also acknowledge how outrageously false it might be to suggest that Haskell has a lot to learn in light of Scala's… fun bits.

As we have moved away from first using the word pimp, then retracting it, we now need to come up with a word to denote age discrimination, then retract it so we can pretend to be the good guys. I suggest the word swonkytonk to denote anyone born 10 years before the median age of all of us, who is therefore, a contributor to our collective arrogance. Suggestions welcome.

[^1]: Never mind the double-think! Yep, just keep on walking.
[^2]: http://www.scala-lang.org/node/11615?page=2#comment-51718 Any man who needs to say I am the king is no true king.

@tonymorris tonymorris closed this Jul 3, 2013
@tonymorris
Copy link
Member Author

@tonymorris tonymorris commented Jul 3, 2013

I just realised you cannot delete github issues. I was just having some fun. Sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant