Ryan Morshead

Quick to implement if a deprecation warning is included until the old syntax is dropped. I worry about the syntax being off-putting though. Technically React also has a similar issue...

I guess the whole framework is probably odd to Python devs though, so maybe this isn't so bad.

Ok, here's what I think we should do here: 1. clearly document this. 2. see how commonly people report problems with this. 3. based on the commonality of the problem...

I think we could probably skip the qualname check and allow lambda comparisons by, as you say, just checking byte code equivalence.

True. Though technically, all we really care about is whether, given the same inputs, the output is the same (assuming the function is pure). The file name then, only matters...

There's definitely a lot of room for improvement. The areas to focus on, probably in this order, are: 1. Computing JSON patches. Right now this is using a pure Python...

Yeah, scrap what I said before, we need to profile before doing any work. It's very possible that using JSON patch doesn't provide any significant benefit in the most common...

This is probably a bug in Victory, we just need to confirm this.

Related to #346

This seems to describe a need for third party libraries to subscribe to, and send messages over, the websocket both on the server and the client. This simply isn't possible...