Mame Memo

Small fact about Isabelle: that's where the pipeline operator |> comes from. Here's a post about it with a few sources: http://mamememo.blogspot.com/2019/06/a-brief-history-of-pipeline-operator.html

"also" isn't an excellent name for it, but I like the idea of giving names to operators instead of using things like >>=, <$>, <*>. I have a hard time reading code with it, as I always pause to think "okay, how should I read that?". I wonder if that's something you get used to, or a difference in how people think.

An "actual" piet quine:

http://mamememo.blogspot.hu/2009/10/piet-quine.html

For me the image doesn't load, it's archived on stackexchange fortunately:

https://codegolf.stackexchange.com/questions/23193/output-an-image-of-your-source-code-not-quite-a-quine

$ ../npiet-1.1/npiet quine.gif > quine2.gif
$ diff quine.gif quine2.gif

It's freakin' impressive.

There have been issues[1] with seccomp. Maybe try with seccomp disabled for that container?

--security-opt seccomp:unconfined

More info here[2].

[1]: https://github.com/docker/for-linux/issues/738

[2]: http://mamememo.blogspot.com/2020/05/cpu-intensive-rubypython-code-runs.html

Feature request for pipeline operator in Ruby:
https://bugs.ruby-lang.org/issues/15799

See also:

https://mamememo.blogspot.com/2019/06/a-brief-history-of-pipeline-operator.html

https://mametter.hatenablog.com/entry/2019/06/15/192311