endgame

Neither `amazonka-route53` nor `amazonka-s3` seem to depend on `xml-conduit` these days, but a more fundamental direct dependency is `amazonka-core`'s reliance on `http-conduit`, which I can't see us easily fixing. And...

The new parser in `aeson >= 2.1.2.0`, [`Data.Aeson.Decoding.Tokens`](https://hackage.haskell.org/package/aeson-2.1.2.0/docs/Data-Aeson-Decoding-Tokens.html) is probably easier to use than `waargonaut` will be, as its `hw-simd-json` dependency doesn't build right now.

Is this [`collect`](https://hackage.haskell.org/package/distributive-0.6.2.1/docs/Data-Distributive.html#v:collect) from `distributive`?

I think the duality with Applicative is a good reason to retain the `*`. The `` around an operator "lifts" it in some sense, and `>

It would be really great if this was resolved. The open questions seem to be: * What do we do about `(>$$&$$$$

I also just noticed that `()` is also `infixl 4`. I wonder if the fixities of the proposed operators could be twiddled in a way that you get nice code...

This sounds like: "??? is to Divisible as Apply is to Applicative". It feels like it should be in `semigroupoids`, but isn't. Similarly: "??? is to Decideable as Alt is...

> I suppose the main benefit would be applying a function to two symbolic values and storing the result in state? Exactly. I can't imagine an exact use right now...

`sqlite` is a derivation with split outputs, so you probably want to expose `sqlite.dev` somehow.

As I said on the corresponding Discourse thread, please don't do this. The cleanup from the `aeson-2.2.0.0`/`attoparsec-aeson` split was bad enough without encouraging more packages to drop upper bounds. The...