Experimental JSON decoding API

I don’t really like it. It can be useful for some cases but it introduces more complexity (more mental work) and it is harder to read and write compared to the existing pipeline. As @albertdahlin mentioned, having to write/read the same variable name 3/4 times, plus cryptic symbols “<|”,"->" makes it more error prone and all of this just to avoid position arguments.
(complex decoding can be done by lazy/map).
This is of course all about tradeoffs, but for me, Elm is already too verbose I would try to keep it cleaner.