Alexis King

You’re technically right, but I find that to be a very odd API. I strongly prefer there be one correct way to do things, unless there is a meaningful difference...

That‘s not a bad idea, nor is it out of the question. Something like `data/collection/compat` or `data/collection/interop`? I think I would accept a PR for such a feature.

I think the real problem here is that laziness interacts poorly with needing to display values, whether that be in the REPL or otherwise. Correct me if I'm wrong. In...

I considered using `known-finite?`, but that doesn't really work since `print` can't be implemented for generic sequences in general, only on individual data structures. This is still relevant though—we just...

I think giving control of printing to the data structures themselves is still the right approach. The only issue is how to handle streams, which are the current data structure...

I’m not sure that it’s (currently) possible. Plus, as you mentioned in the commit message, it only works in simple cases where macros do not use other macros. This seems...

If we do that, I think it would be helpful to rename this package `websocket` and move this code into the `net/websocket` collection, since `rfc6455` isn't a very descriptive name.

Any further thoughts on this, a year later? I’d still appreciate renaming this package to `websocket` and exposing `net/websocket`, then just having `rfc6455` reprovide everything.

If you take a look at `react-apollo-todo/react-apollo/final-app/src/apollo.js`, you can see that it actually does open a WebSocket connection: https://github.com/hasura/react-apollo-todo/blob/914b6ad735fcb249a291c24a94b2257d500881ec/react-apollo/final-app/src/apollo.js#L40-L48 …but it then chooses to only use that connection for subscription...

This is an interesting idea, but storing sensitive information in environment variables is one of the more common use-cases (things like API credentials), so this would need to be enabled...