4 ms·
> The motion is much more natural and smooth, as if things had a bit of mass/ momentum. While I agree the motion itself feels fairly natural, there is a lag wh
by vladvasiliu 3y ago
> The motion is much more natural and smooth, as if things had a bit of mass/ momentum.
While I agree the motion itself feels fairly natural, there is a lag when you first start to move things around, which feels very weird. Once things start moving, they move as I expect them to, but only after a delay.
This is on Firefox 113.0.2 on Linux/X11 on a 4k@60Hz screen.
- kaliszad 3y agoThank you for the feedback. Unfortunately, Firefox (my daily driver for all things but OrgPad) is even slower than Chrome/ium for rendering. We, or mainly my colleague, will at some point rewrite most of the rendering into WebGL which should speed things up greatly. On the way there, we might rewrite even more stuff to canvas rendering but there are diminishing returns especially because font drawing in canvas is rather slow - we have to do a lot of caching which makes memory consumption a problem. Btw. you can probably confirm most of this using the browser profiler - you should see that OrgPad code usually occupies a fraction of the ~16 ms needed for smooth 60 Hz rendering. The rest is usually compositing on the GPU, something we can only affect by doing even more rendering on our own. How sad, in 2023 we are not able to draw a few hundred divs on a screen with absolute position without lag.