C
Caudate
z.caudate.me · Personal blog · on HN since 2013
Caudate is a Clojure programmer who writes opinionated posts on Clojure libraries, language design, REST, and the Clojure community.
What HN saysHN commenters link it mainly for "On Whose Authority," whose HN discussion was reportedly killed, and for debate over Clojure's openness and typing.
15HN people shared it
3linked it in comments
13stories submitted
36story points
9 years agolast shared
2013people per year2026
Most-shared posts
- 1On whose authority?4 people · 5 points · first shared 2017 · discussion on HN
- 2Why clojure.zip sucks2 people · 5 points · first shared 2016 · discussion on HN
- 3Why the future is Not RESTful1 people · 7 points · first shared 2013 · 3 comments on HN
- 4Of qufoids and the monad effect1 people · 5 points · first shared 2014 · discussion on HN
- 5Data Driven Rethinkdb Clojure Library1 people · 4 points · first shared 2016 · 1 comments on HN
- 6Clojure, Dynamic Languages, Creativity and Simplicity1 people · 3 points · first shared 2014 · discussion on HN
- 7Gita – the introspective jgit wrapper1 people · 2 points · first shared 2015 · discussion on HN
- 8You took 3 months to write a mutable array for clojure?1 people · 2 points · first shared 2013 · discussion on HN
- 9Hy there Clojars1 people · 1 points · first shared 2017 · discussion on HN
- 10The abstract container pattern1 people · 1 points · first shared 2014 · discussion on HN
- 11Give your clojure workflow more flow1 people · 1 points · first shared 2014 · discussion on HN
- 12Language hair and popularity1 people · first shared 2014
What HN people wrote when they linked it
systems · 2018-01-17
they wont ... or at least not any time soon
if you search online they did address this repeated request
in summary
they do it for money,
they dont know how to do it for money if its open-source,
they already contributed clojure to the open source community
someone already was vocally aggressive about this in a blog: http://z.caudate.me/on-whose-authority/
and rich hickey didnt like it: https://www.reddit.com/r/Clojure/comments/73yznc/on_whose_authority/do…
--
My personal take on this
its not that datomic is closed source or that it cost a lot of money
its that for its cost, its a valid option for fewer people
i use ms sql at work, and it cost a lot of money
but .. you can easily make the business case for it
for datomic ... it would be much harder
datomic is a niche product .. which is not bad .. it is just where its at
mcguire · 2017-10-19
Then, there is the case of 'On Whose Authority (http://z.caudate.me/on-whose-authority/), the HN discussion of which was killed while the discussion of Rich Hickey's response (https://www.reddit.com/r/Clojure/comments/73yznc/on_whose_authority/do… was ongoing and both were on the front page.
__--__ · 2014-01-14
All this talk about formal type theory, but where are the references to the relevant studies? Where's the data? The few studies[1][2][3][4] I've found are inconclusive one way or the other and none of them focus on error rates. I found another conversation about how to go about studying error rate in dynamically vs statically typed languages, but all I really found was this article studying the affect of hair style on language design[5].
[1] http://pleiad.dcc.uchile.cl/papers/2012/kleinschmagerAl-icpc2012.pdf - maintainability
[2] http://dl.acm.org/citation.cfm?id=2047861&CFID=399382397&CFTOK… - development time
[3] https://courses.cs.washington.edu/courses/cse590n/10au/hanenberg-oopsl… - development time, take 2
[4] http://pleiad.dcc.uchile.cl/papers/2012/mayerAl-oopsla2012.pdf - usability
[5] http://z.caudate.me/language-hair-and-popularity/