Ryan Riley

@waghanza this one looks above my pay grade. ;) I'm pretty busy at the moment, but if I get some time, I'll take a look.

@granicz and @Tarmil, this blocked https://github.com/the-benchmarker/web-frameworks/pull/2874/ from building successfully. All the frameworks in that comparison use .NET Core 3.1, and as it's running on docker, I don't have a good...

@Happypig375 Public Service Announcement

@Krzysztof-Cieslak, from what I can tell, LiveView does a diff on the server-side by diffing the components that changed, as well as on the client-side, so it always sends the...

Thanks for looking into this, @Banashek! A lot of this still reminds me of the [Blazor Server hosting model](https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-3.1#blazor-server), with the biggest exception being the diff on the server-side. @baronfel,...

> Is that just about, oh I don't want to use stupid JS frameworks or do we have any use cases where it's just better than "normal" client-side rendering. I...

Outstanding!!!

I vote for `AsyncSeq` because the pattern follows that of `FSharpList`. `IAsyncEnumerator` has all the problems of `IEnumerator`, including thrown exceptions and mutable state.

@dsyme :+1: Actually, I think now that a lot of F#x should be broken into smaller assemblies. My original thought was to do this with sources that could just compile...

Seems the easiest option here would be to just make the secure parameters automatically wrap with something that could be declared explicitly for other parameters, then referenced where necessary? That...