Łukasz Jan Niemier

Traditionally in most languages the stdout is buffered and stderr is not, this follow libc "standard". Additionally Elixir's logger use `:user` as a default device instead of `:standard_io` and that...

Not really, Erlang (as you have spotted) uses `standard_io` by default, it is Elixir that is using `user`. And as I said, it is not possible to do anything about...

@josevalim I didn't have much time to spare to work on remaining 2 issues. I will try to make it a thing in 1.12 after I release `enough` library which...

IIRC these do not require OTP 23, but the problems can be for example with formatter and "compile" step, which is not present in Erlang's formatters and which is used...

Yes, currently there is no way to format the reports (structured messages) in **Elixir formatter**, however, you can do it **Elixir translator**. It will require some workarounds to not format...

Whatever works for you. If you do not care, or you will handle all formatting on your own, then I would go with Erlang logger formatter for `logger_std_h`. The only...

@josevalim I have added few points. Maybe we should split this issue into set of smaller ones that will describe each of the needed tasks, and then join them using...

Added more stuff. Some of them are ready to be done in OTP 24+ (migration from `:console` to `:logger_std_h`) and added links to Erlang issues in few others.

@polvalente it is not my doing, but it sounds like bug, so you probably should create separate issue for that. The formatter output should not change as it may be...

@josevalim I agree that in this particular situation it makes sense to use custom attribute instead, but imagine something like that: ```elixir defmacro defrecord(name, tag \\ nil, kv) do quote...