Joe Armstrong
armstrongonsoftware.blogspot.com · Personal blog · on HN since 2007
Joe Armstrong, co-creator of Erlang, wrote about software design, concurrency, RPC and why he implements things from scratch.
What HN saysHN links it for his essay on RPC, "The road we didn't go down", and for his posts on language and VM design.
21HN people shared it
10linked it in comments
13stories submitted
332story points
3 years agolast shared
2007people per year2026
Most-shared posts
- 1Erlang's Joe Armstrong on RPC: "The road we didn't go down"5 people · 32 points · first shared 2008 · 6 comments on HN
- 2UBF and VM opcocde design3 people · 6 points · first shared 2008 · discussion on HN
- 3Comet is dead, long live websockets2 people · 109 points · first shared 2009 · 46 comments on HN
- 4Itching my programming nerve2 people · 24 points · first shared 2008 · 15 comments on HN
- 5Armstrong on software2 people · 1 points · first shared 2009 · discussion on HN
- 6Why I often implement things from scratch (2006)1 people · 144 points · first shared 2020 · 144 comments on HN
- 7Concurrency is easy1 people · 11 points · first shared 2011 · discussion on HN
- 8Content Editable1 people · 3 points · first shared 2009 · discussion on HN
- 9Where's my cheese1 people · 1 points · first shared 2012 · discussion on HN
- 10JSON protocols (part 1)1 people · 1 points · first shared 2009 · discussion on HN
- 11Road we didnt go down1 people · first shared 2016
- 12Making money from erlang1 people · first shared 2007
- 13Invasion of privacy1 people · first shared 2008
- 14Pure and simple transaction memories1 people · first shared 2008
What HN people wrote when they linked it
samwilliams · 2014-02-28
Can you elaborate on what exactly that is, please? I don't see mention of any new syntax on the 'Armstrong on software' blog [0]. The highlights of R17 include maps and named funs, both of which add to the grammar of the language!
[0] http://armstrongonsoftware.blogspot.com/
while · 2008-07-25
Follow the link mentioned on the page. http://armstrongonsoftware.blogspot.com/2008/06/itching-my-programming…
mietek · 2024-03-09
Yes. More on that from the creator of Erlang:
http://armstrongonsoftware.blogspot.com/2008/05/road-we-didnt-go-down.…
Bye, Joe.
mikhailfranco · 2019-10-11
I think most people today would use a web front-end to Erlang/Elixir, with events over websockets (cowboy), using WebGL in the browser, with either server-side rendering (Phoenix LiveView) or client-side JS integration (pick your poison).
https://github.com/phoenixframework/phoenix_live_view
These ideas were first proposed by ... joearms, of course, way back in 2009.
https://armstrongonsoftware.blogspot.com/2009/12/comet-is-dead-long-li…
RIP Joe
pyotrgalois · 2016-08-10
In some way this article by one of Erlang creators is related to your comment:
https://armstrongonsoftware.blogspot.com.ar/2008/05/road-we-didnt-go-d…
> The fundamental problem with taking a remote operation and wrapping it up so that it looks like a local operation is that the failure modes of local and remote operations are completely different.
dugmartin · 2015-03-30
This sounds a lot like CORBA (http://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture…
The big problem with distributed classes is that network communication links are fragile and you need to bake how to deal with failures into your methodology. Erlang handles this in a way that Joe Armstrong explains here:
http://armstrongonsoftware.blogspot.com/2008/05/road-we-didnt-go-down.…
nimrody · 2011-03-13
For some information on why Erlang did not go the RPC way:
http://armstrongonsoftware.blogspot.com/2008/05/road-we-didnt-go-down.…
narag · 2008-06-26
It seems that Sweden has just approved a similar rogue law:
http://armstrongonsoftware.blogspot.com/2008/06/invasion-of-privacy.ht…
ntoshev · 2008-01-16
No idea how pg handles it, but here is an easy do-it-yourself way:
http://armstrongonsoftware.blogspot.com/2006/09/pure-and-simple-transa…
It doesn't matter it is in Erlang - you can do it in any language. A Lisp that implements software transactional memory is Clojure (runs on the JVM):
http://clojure.sourceforge.net/
sri · 2007-07-05
Why prove anything to anyone?
Just build something cool, make $$$,
move on, build something else cool and make $$$, ....
http://armstrongonsoftware.blogspot.com/2006/08/making-money-from-erla…