Top all-time · #3954
Elliotte Rusty Harold
Personal blog · cafe.elharo.comprogrammingweb
Elliotte Rusty Harold writes The Cafes, a personal blog at cafe.elharo.com about programming and web. Since 2008, 19 different Hacker News readers have linked it 24 times, most often “Why Functional Programming in Java is Dangerous”. It is still writing: the last post was on 2026-09-04, and you can follow it by feed.
Most-linked posts?
- Why Functional Programming in Java is Dangerous2 people · 2 mentions · first linked 2013-01-23
What Hacker News says?
The thesis ( https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm ) with relevant section: http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch... The HTTP REST came from people mapping HTTP verbs to RESTful actions: http://cafe.elharo.com/web/why-rest-failed/ (2006) to https://martinfowler.com/articles/richardsonMaturityModel.ht... (2010)
Comment linking /web/why-rest-failed/
on “REST is the new SOAP”Submitted Java is Dead; Long Live Python as a story · 74 points
HN discussionIt is strange that the consensus in the Java community sort of ended up being against checked exceptions. I for one think that this consensus is completely wrong and I suspect that what looks like a consensus is just a bunch of very loud people shouting down everyone else (and to me not making very compelling arguments). Elliotte Rusty Harold's brief post on this pretty much nails it for me: http://cafe.elharo.com/b…
Comment linking /blogroll/voting-for-checked-exceptions/
on “Why should I have written ZeroMQ in C, not C++”Submitted A Square Is Not A Rectangle as a story · 67 points
HN discussionIt's not quite that simple. He doesn't directly addresses every interpretation. REST ( http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_ar... ) HTTP REST ( http://cafe.elharo.com/web/why-rest-failed/ ) GET/POST vs GET/POST/DELETE/PUT (HTTP REST) ( http://www.artima.com/lejava/articles/why_put_and_delete.htm... ) A more recent look at GET/POST over HTTP REST ( http://roy.gbiv.com/untangled/2009/it-is-okay-to…
Comment linking /web/why-rest-failed/
on “What RESTful actually means”Submitted Bruce Eckel is Wrong as a story · 22 points
HN discussionOh, I know about this already. Trouble is, panics aren't supposed to cross module boundaries. "The convention in the Go libraries is that even when a package uses panic internally, its external API still presents explicit error return values" http://blog.golang.org/2010/08/defer-panic-and-recover.html But crossing interfaces between modules is, IMO, core to exceptions. They're ideally suited to communicating the und…
Comment linking /programming/bruce-eckel-is-wrong/
on “The Go Programming Language, or: Why all C-like languages except one suck.”Submitted The Ten Commandments of Unicode as a story · 4 points
HN discussionConsidered by people who have used C++ and seen some awful problems creep in because of unnecessary operator overloading. Your last point actually highlights the problem - it is not more reliable because you are assuming what "+" and "*" do. EDIT: An old blog post about the issue: http://cafe.elharo.com/programming/operator-overloading-cons...
Comment linking /programming/operator-overloading-considered-harmful/
on “Everything about Java 8”Submitted XML 2.0: Thoughts on a new version of XML as a story · 3 points
HN discussion> looking at the URI the consumer must understand all about the given resource Just because? No. > The HTTP methods must be used to give the intent of the action that is happening. That interpretation (PATCH, DELETE, etc) is not "correct", which is endlessly maddening. It was a possible scheme, just like a waterfall process was a possible development scheme. There is no correctness implied. See: http://www.ics.uci.e…
Comment linking /web/why-rest-failed/
on “REST Anti-patterns”Submitted Overcoming Objections to Refactoring as a story · 3 points
HN discussionREST does not require a specific response. The original paper used specific verb as an example present in the wild, which has oft been misinterpreted as required usage. Formatted summary - http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_ar... - "The most frequent form of request semantics is that of retrieving a representation of a resource (e.g., the "GET" method in HTTP), which can often be cached for la…
Comment linking /web/why-rest-failed/
on “Show HN: Xmysql – One command to serve REST APIs for any MySql database”Submitted Why Functional Programming in Java is Dangerous as a story · 2 points
HN discussionI really like this comment from Uncle Bob: Inheritance is not ISA. It is a redeclaration of variables and functions in a sub-scope! http://cafe.elharo.com/programming/a-square-is-not-a-rectang...
Comment linking /programming/a-square-is-not-a-rectangle/
on “A Square Is Not A Rectangle”Submitted Don't Design for Reuse as a story · 2 points
HN discussionSubmitted Why don't Macs support multiple monitors? as a story · 2 points
HN discussionSubmitted Why Functional Programming in Java Is Dangerous (2013) as a story · 1 points
HN discussionSubmitted Why Functional Programming in Java is Dangerous as a story · 1 points
HN discussionSubmitted Why java.util.Arrays uses Two Sorting Algorithms as a story · 1 points
HN discussionSubmitted Why Hate the for Loop? as a story · 1 points
HN discussionSubmitted Why Pair Programming Works as a story · 1 points
HN discussionSubmitted Must Ignore vs. Microformats as a story · 1 points
HN discussionSubmitted Refactoring. What is it? Why do it? as a story · 1 points
HN discussion
