@mitchellh curious: every frame here is a full raw bitmap which is fine locally but adds up fast remotely. do you plan to do anything smarter with images on the Rex server-to-client link (compression, video, etc), or is that not much of a concern?
@ladybirdbrowser now speaks the kitty graphics protocol https://t.co/9SyZPpPLsK. huge QoL for developing on remote machines. works perfectly in Rex by @superlogical
Nice thing about using Rust in @ladybirdbrowser: it becomes significantly easier to parallelize things when you have confidence that they're not racy!
Here's what it looks like when we distribute JS parsing to a thread pool instead of parsing synchronously on the main thread:
@PavitraGolchha@awesomekling@ladybirdbrowser response stream, which means we can process chunks as they are arrive instead of waiting for the whole response body like it was before.
We switched all our network requests in @ladybirdbrowser to be unbuffered, which means we can now see ChatGPT responses incrementally as they come in!
Props to @KalenikW for fixing this (and all the bugs it uncovered)!
google maps progress update:
- implemented enough webgl support for globe view and vector tiles
- libjs is much faster than a year ago, but there's still lots of optimization work to do before we can seamlessly decode tiles
working on graphics in ladybird, it was surprising how hard it is to deliver something consistent on linux vs mac. currently our linux build lags behind both feature & performance wise, e.g. webgl is only supported on mac at the moment and
more complicated apis compared to mac counterparts, and, more importantly, it's harder to make sure everything works consistently on different hardware, especially when you are a small team.
I've added basic pointer events dispatch and fixed a few issues with CSSStyleDeclaration. Now, it's possible to paint shapes on https://t.co/hpVMj51yup. Implementing missing features for open-source web apps is so much easier than dealing with minified production websites.
I checked a website saved couple months ago as a "nice image decoding stress test". Apparently, the combination of switching to libwebp for animated WebP decoding and using Skia for rasterization helped a lot there.
@mrunix0 yes, we use skia for webpage and canvas rasterization, although we still have a lot of work to do to efficiently coordinate painting from the LibWeb side
after doing more research, it turned out o1's speculations were right. it just didn't know this thing named "The percentage height calculation quirk" and there is a spec for it https://t.co/ZZUJPdlOLk
frustrated trying to understand how engines resolve CSS percentages I reached out to o1. really impressed! not sure about the speculative part about how engines work, but the info based on the spec seems solid and even links to the relevant section!
https://t.co/ziy4wbpdtZ