> The issue is that moving from synchronous API calls to asynchronous message passing introduces new complexity. It's not suitable for every problem. This has

> The issue is that moving from synchronous API calls to asynchronous message passing introduces new complexity. It's not suitable for every problem. This has been a problem I've been trying to solve for years! Surprisingly, it's a fun problem space, mostly because I disagree that it isn't suitable for every problem. The solution I've been converging on is quite interesting, essentially a non-linear programming language that you write linearly (similar to how CPU branch prediction runs code that hasn't executed yet ... just on a more abstract level). It's pretty neat in how it works under the hood, but on the programmer level, it feels like just another programming language; but like erlang/elixir, the execution can be spread all over the world, or just your machine. Probably one of the coolest things was when I got optimistic mirroring working, where local code will "predict" what distant code will do and then allow your local code to run to completion but not commit the result until the remote code agrees with the prediction -- and if it disagrees the code has to rerun that portion. Fun stuff, but still probably a few years away from a HN post about it... it's just a fun side-research project atm.