Simon Peyton Jones

Well, it was only on Windows, and only when you compile a module that was not in the current directory.

But in that stage, our users were very forgiving, and somebody wrote to us and said, well, by the way, Simon, you might like to know that GHC does this, but hey, don't worry about it.

I just copy all my files somewhere else before I compile, and then I copy them back.

So, of course, those days are long gone.

We pay a lot more attention to our users and have much more rigorous CI testing than ever we did.

So that's a story from a long time ago, but it's a good cultural story because it suggests that we care about our users very much, but we care about users who in their hearts want to be principled.

We're trying to appeal to.

One of the things I like best about Haskell is people often say, I just enjoy writing Haskell.

It's fun, right?

My boss doesn't allow me to because, you know, it somehow doesn't fit with my production shop.

But for me, I would go for, I love writing this stuff every time.

Every time.

That's very rewarding to me.

Oh, yeah.

This was just a little play on words.

It was in a retrospective on Haskell.

I gave an invited talk at Popple a long time ago, probably 20 years ago.

So it's a little play on words because you can read it as either avoid success at all costs.

That's what we've been discussing.

Success at all costs means compromise your principles in order to satisfy your users or think that you're satisfying users.