Maxim Fedorov

Agree, comments should be removed, let me update it. Not sure about export_all though, and compiler warning suppression.

I like this suggestion too. But I'm opposed to "export_all" (we had quite a history with it), and even more against suppressing the warning about it.

Same issue here: ``` INFO[0163] Taking snapshot of full filesystem... fatal error: runtime: out of memory runtime stack: runtime.throw({0x12f3614, 0x16}) /usr/local/go/src/runtime/panic.go:1198 +0x54 runtime.sysMap(0x4041c00000, 0x20000000, 0x220fdd0) /usr/local/go/src/runtime/mem_linux.go:169 +0xbc github.com/google/go-containerregistry/pkg/v1/tarball.WithCompressedCaching.func1() /src/vendor/github.com/google/go-containerregistry/pkg/v1/tarball/layer.go:119 +0x6c...

The stack traces I pasted are from 1.8.0.

One other feature me (and @josevalim I think as well) is really interested about is some way to extend pretty printing in the shell. There is some very basic mechanism...

It looks very similar to #6105 This change appears to be responsible for the new behaviour: https://github.com/erlang/otp/commit/e165a3368da#diff-280aa9e67bfae54121bde3ed8b7e1eea6f845f68ca0600c96331fbacb315672b

IIRC that's been discussed on the Erlang Forums (with no specific conclusion). I'm not sure if this behaviour is in fact desired - so far I know no other generic...

@voltone - it's finally happening, one of the first items we had under "what EEF Security WG should attempt". Thanks @dgud !

I actually like the idea of moving all BEAM flavours under one umbrella. Always wanted to have LFE Docker image.

Regarding `socket` performance, there is also Erlang Forum thread: https://erlangforums.com/t/high-er-cpu-utilization-with-socket-backend-esp-for-udp/1720 I am also observing some mixed performance data from `socket` (used directly, not via gen_tcp backend). There might be some...