4 ms·
No. This website is slow because its a liveview style websocket on each drag and drop action. A wasm implementation would not exhibit these characteristics.
by mgh95 3y ago
No. This website is slow because its a liveview style websocket on each drag and drop action. A wasm implementation would not exhibit these characteristics.
- jiggawatts 3y agoAlso, internal-use apps are typically accessed over the LAN with much lower latencies than random Internet users.
- ptrwis 3y agoOn the other hand, remote work is very popular today, but if employees want to work remotely, it's their problem to have a good internet. I tested the Blazor server on a poor cellular network where packets could be lost or there were random long delays in packet delivery, and the application was unstable. It was better to set long-polling and enable compression, which is disabled by default. This is also a problem with websockets - messages are not compressed. Long polling again was less resposnsive on good internet connection. I'm curious how this would work in various configurations of quic/http3.
- jiggawatts 3y agoIt's possible to enable compression for WebSockets, but the real problem is latency, not bandwidth. You can't fix the speed of light.