<@U0HUJ25V1>: The thing with websockets for JPro i...
# tornadofx
e
@thomasnield: The thing with websockets for JPro is that they almost abuse them. Just hovering over something needs to keep sending events to keep the UI in sync, so it is incredibly network resource hungry compared to a JavaScript frontend. And latency is more important than brandwidth.