Gilbert

@ljharb I think such a strong stance to take would make sense if `$$` were made globally available, but here it's only on the right-hand side of a pipeline –...

I agree it's implicit, but I would not equate to `with`. Yes we'd be loath to reintroduce `with`, but this is not remotely the same thing.

@rpominov Adding `#` as syntax will be a rough and uphill battle. It's hard enough convincing to add [papp](https://github.com/mindeavor/es-papp) to `Function.prototype`. ```js [1, 2] |> List.map.papp(x => x + 1)...

For the record, here's the discussion on the pipeline op: https://esdiscuss.org/topic/the-pipeline-operator-making-multiple-function-calls-look-great

Love it. Super intuitive. Since it's just a vnode, would it work in any part of a tree, not just components?

I have an idea for an api but first I need to know: how does `m.updateIf` / `m.compare` keep track of previous values?

As the author of [mithril-cc](https://github.com/gilbert/mithril-cc), naturally I'm excited about this 😄 Regarding `initial` in the closure component form, I'm concerned the age-old [stale attrs problem](https://github.com/MithrilJS/mithril.js/issues/683) will rear its ugly head...

Ah right, since both versions are functions, mithril doesn't know what version your component constructor is until *after* it runs once, which poses a problem.

The stale attrs problem is more confusing IMO, as it's much harder to document (not to mention its inelegant workarounds). But it seems there's not much mithril can do here,...

Another con of Option 2 is the dilemma between only providing the `attrs` getter, or providing a plain object `attrs` in the returned view function but risking a similar shadowing...