As the image does not change much frame to frame, I presume that if you compute it and display it every fifth frame or so, nobody would ever notice.
262 karma · joined June 12, 2022
As the image does not change much frame to frame, I presume that if you compute it and display it every fifth frame or so, nobody would ever notice.
What Joe did in his thesis is to show you how you can build reliable systems (and up point, reliable distribuited systems) by using a given set of Lego blocks.
The reason why you need the erlang vm to implement something like that appropriately – and that you cannot do that fully on a different VM – is that without the underlying plumbing, supervision trees would be leaky - in Java, you cannot kill a thread that is holding up to resources and hope that everything will always go well, And do not have ways to monitor different processes.
In clojure you could easily create the same features with a bit of macro magic.
Here on HN there is plenty of announces of new things “like X but in Rust” - even when X would be fine in Python or Bash.
If that happens to be a bottleneck and you can do better, you should definitely do it in code locally. But these are two ifs that need to evaluate to true
I mean, I love Clojure, and used it for personal and work projects for 10+ years, some of which have hundreds of stars on github. But I cannot count the time wasted to spot issues where a map was actually a list of maps. Here Elixir is doing the right thing - adding gradual typing.
So in the end, you have to fight the half-assed small language that was created and have to find a way to connect to some real language to get things done.
Documentation facilities in Elixir are extremely powerful, as you can use Elixir to generate the documentation itself! See e.g. the way UML diagrams are embedded here: https://hexdocs.pm/say_cheez_ex/readme.html#uml-dot-graphs - nothing stops you from creating them dynamically based on external information, test results, external services or whatnot.
This in turn means that the structure and style is shared by many libs in the ecosystem, and everything is natively cross-referenced.
Current workplace maintains a good amount of tech docs written in AsciiDoc that have been written over approx 20 years, that create PDF/ebooks and are published as a searchable online version with Antora. It works pretty well.