jchassoul

just use bspwm!

happy vim8 + Denite user here!, Telescope seems great as well can't wait to try it out eventually with nvim!

The future of RTS is the acknowledgement of Brood War as our new modern digital chess.

I love bspwm!

It's all about messaging.

quoting: Soon we will have chips with thousands of cores with high-bandwidth interconnect. Such chips will power the next generation of Intelligent Applications.

Since message passing between Actors is the standard method to communicate, languages like Erlang are highly relevant.

Syntactic sugar causes cancer of the semicolon!

It is NOT, is cool that you love Clojure, Scheme or Common Lisp but LFE is not a re-implementation of any of those things nor envy any of the features on them.

LFE is a clean, beautiful an proper Lisp for the complete BEAM ecosystem.

If anything on the BEAM ecosystem interest you I highlight recommend you check out LFE! (=

There are no symbols! you have lots of little processes with lots of connections between them and you change the strengths of the connections and that's how we learn things.

Both are awesome papers, I found this very interesting:

"In 1975 Gerald J. Sussman and Guy L. Steele Jr. began experimenting with some interpreters in an attempt to understand the consequences of the Actor model of computation. This led to the publication during 1976–1978 of a series of papers describing a new dialect of Lisp called Scheme. Scheme was one of the first languages to have taken seriously the implications of lexical scoping and first-class functions. Namely, Scheme correctly treated closures—a closure is a function along with the local environment within which it was defined."

I heart Richard Gabriel once saying that the goal of Scheme was implement Carl Hewitt's Actor model but they discover closures instead, got hyped and forget about the original mission.

Later history repeat itself twice, Robert Virding a true Lisp Hacker implement LFE his own LISP for the BEAM ecosystem and accomplish the original Scheme goal and probably without even know or care much about it, in the similar way that once Mike Williams, Joe Armstrong and him build Erlang the best implementation (in my opinion) that we got from the Actor model without know nothing about it existence at the time of the development of Erlang.

Indeed the SIP over WebRTC open source stack is a thing of beauty!

Do you want to abolish the protagonist role of the channel abstraction like in CSP based languages and certain message brokers?

We can't have issues with channels if we're all actors and don't impedance mismatch the mixture when building our systems.