Wasn't expecting `chart({ mark: ... })` primitives in a 3D WebGL 2 library that cover timeseries, heat-colored hour/day surface charts, and tiled dashboards off the bat—that’s quite a pleasant surprise!
There were two things in particular about the landing page that caught my eye:
1. Views that only render when there’s something to update (this is especially important for financial/trading dashboards when there are 8+ chart views open all day long and no way to afford 60fps render loop chewing up the GPU without any data).
2. Errors in option validation designed specifically to inform coding bots what to do.
Now, as far as `TIMESERIES` and `SURFACE` chart types go, how effective is `tween` when it comes to updating geometry buffer in live stream mode (e.g. adding new candle/bucket in real time)?
This is super cool, and I loved seeing the FPS stay locked at 120 on my phone. I didn't see this on the website, but do you have any docs that detail how your library compares to other popular options such as Three, Babylon, etc? Definitely giving this a try today.
One thing I noticed is that the "hover" functionality in most of the demos doesn't behave well on mobile. Taps don't stay active for long after interacting with something. Not sure if this is intentional or just a browser compatibility quirk (Fennec on Android 17). Happy to make a contribution if it should be a little more persistent!
Wow, that is amazing, these demo's are exactly the same demo's Claude keeps buildings for me for any 3d engine I try with it.
Even most comments in the code look exactly like my Claude output!
I guess they've must have trained on your codebase or something!
Wasn't expecting `chart({ mark: ... })` primitives in a 3D WebGL 2 library that cover timeseries, heat-colored hour/day surface charts, and tiled dashboards off the bat—that’s quite a pleasant surprise!
There were two things in particular about the landing page that caught my eye: 1. Views that only render when there’s something to update (this is especially important for financial/trading dashboards when there are 8+ chart views open all day long and no way to afford 60fps render loop chewing up the GPU without any data). 2. Errors in option validation designed specifically to inform coding bots what to do.
Now, as far as `TIMESERIES` and `SURFACE` chart types go, how effective is `tween` when it comes to updating geometry buffer in live stream mode (e.g. adding new candle/bucket in real time)?
This is super cool, and I loved seeing the FPS stay locked at 120 on my phone. I didn't see this on the website, but do you have any docs that detail how your library compares to other popular options such as Three, Babylon, etc? Definitely giving this a try today.
One thing I noticed is that the "hover" functionality in most of the demos doesn't behave well on mobile. Taps don't stay active for long after interacting with something. Not sure if this is intentional or just a browser compatibility quirk (Fennec on Android 17). Happy to make a contribution if it should be a little more persistent!
Yup, this is rad.
Ok, the bricks demo is laugh out loud fun, thanks!
This is insanely performant, wow!
That's very nice, but... why WebGL2 instead of WebGPU?
Having tried WebGPU recently, it still isn't at a point where it can be relied upon on all platforms.
Notably I have to use Chrome on Linux because Firefox doesn't provide it out of the box. It still crashes a fair bit on Chrome.
Really, very nice, some good aesthetic taste here, woooowy!
Wow, the demo is really great. It’s impressive that even these demos run fast enough on my phone.