Doug Beardsley

This is definitely still relevant, and it's a very easy issue to fix. The main question at this point is maintainer buy-in.

This issue is specifically asking for (1), not (2).

@codygman No, 2 does not address 1. Sometimes you actually want the existing `Show` type class. If we could rewind the clock and make `Show` render to `Text` instead of...

Hey Bryan, it's really about a lot more than 5 or 6 keystrokes. It's about uniformity and standardization. In different places and projects I've seen it called `tshow`, `showt`, and...

> Let me put it this way: the _right_ thing to do is to use `text-show`. I'm worried that offering `tshow` from `text` will quash any incentive to do the...

In the vast majority of situations I don't care about char-to-char compatibility or performance. I care about avoiding an additional (heavy) dep way more.

All of them. You shouldn't have to incur a single extra dependency just to get _a composition of two functions you're already depending on_. It would still be unacceptable if...

Hmmm, I'm not sure what's going on. It sounds to me like Nixos probably ships with a more recent version of aeson. Not sure why you're not getting the version...

What exactly are you proposing? Did it work after `stack init`? If so, I don't see the need to include a `stack.yaml` because that's just another thing to maintain.

Can you give some details about the problem you ran into with `stack init`? It sounds like we should fix it so that works.