Standa Lukeš

Thanks for reporting the issue. I believe this one is caused by a partially fixed bug that we don't use the DotVVM serialized for input arguments and instead call the...

Fix for v5 has been merged (#1898)

Thanks for the suggestion. I tried to implement support for `COPY TO STDOUT`, and yes it's possible (and quite easy) to do. However, on my tests, I see no performance...

Thanks for testing it out. In my experiments, it wasn't faster either. However, the bottleneck is usually pg2parquet, postgres can stream the data faster than pg2parquet can process it. I'm...

The header by itself can't help that much compared to the `link rel=preload` which we already emit. We buffer the entire response, including headers; mainly because at any point there...

I didn't think that copying the properties would be a problem, but may be a problem for correctness when a property would be added to the object. But ES2015 has...

I agree that this is probably the biggest refactoring we did in DotVVM and it certainly would not be that straightforward as I have just described, but when we will...

@djanosik These are all good points, thank you. 1. The VDOM will not touch the element unless something has changed in the virtual DOM, so it will not reset the...

@djanosik 3. Maybe the best solution would be to render pure HTML for server rendered controls and a JS function from the client-side bindings. We have quite decent id addressing...

2. This looks almost like an independent issue, I think @martindybal had some notes about someting similar. 3. I think we could generate first the HTML and then the javascript...