Joe Armstrong, co-creator of Erlang, wrote about software design, concurrency, RPC and why he implements things from scratch.
HN links it for his essay on RPC, "The road we didn't go down", and for his posts on language and VM design.
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-live-websockets.html
RIP Joe
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.html
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-down.html
> 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.
No idea how pg handles it, but here is an easy do-it-yourself way:
http://armstrongonsoftware.blogspot.com/2006/09/pure-and-simple-transaction-memories.html
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/
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/
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-erlang.html