Alexander Kalenik (@KalenikW) profile picture
Krakow
Joined November 2015
Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)Photo by Alexander Kalenik (@KalenikW)
Replying to @ladybirdbrowser
@ladybirdbrowser now speaks the kitty graphics protocol github.com/LadybirdBrowser/l…. huge QoL for developing on remote machines. works perfectly in Rex by @superlogical
21
31
9
784
39,051
@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?
1
13
1,634
lb caught up in terms of responsiveness on real style-layout-painting stress test -- gh pr review page! pre-alpha dogfooding is going smoooooth
5
774
Alexander Kalenik retweeted
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:
17
26
2
692
37,332
Alexander Kalenik retweeted
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)!
9
12
1
820
84,011
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
I tried to open Google Maps in Ladybird and was surprised by how not bad at all we are doing there even without WebGL or GPU-accelerated canvas!
1
9
2,427
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
1
7
1,736
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.
1
1
1,143
seeing platform differences from this angle makes it clear why i usually have a better software experience on mac. it's simply easier to build for.
2
980
I've added basic pointer events dispatch and fixed a few issues with CSSStyleDeclaration. Now, it's possible to paint shapes on excalidraw.com/. Implementing missing features for open-source web apps is so much easier than dealing with minified production websites.
1
7
46
6,675
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.
8
1,583
I tried to open Google Maps in Ladybird and was surprised by how not bad at all we are doing there even without WebGL or GPU-accelerated canvas!
2
11
1
281
27,798
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! chatgpt.com/share/66f6c2f9-6…
1
2
917
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 quirks.spec.whatwg.org/#the-…
1
2
575
Ladybird is almost capable of handling my daily github workflow. recently I fixed a performance issue where we were incorrectly invalidating layout on every scroll change in "File changes" page. it's still sluggish but good enough to review a small PR.
2
6
191
14,125
If I could make just one change to the CSS standard, it would be ensuring elements with "overflow: hidden" and "overflow: scroll" automatically establish a stacking context.
1
4
991
currently, that's not true, meaning each element within a stacking context could potentially have a different containing block and, therefore, a different clip rectangle and scroll offset.
2
1
565
I'm not sure if it was intentional or a design mistake with "overflow", but newer CSS properties like "transform" and "clip-path" force an element to establish a stacking context, making implementation much simpler.
389
this is totally fine until you try to speed things up with optimizations like scrollable layer compositing. then, it becomes frustrating when one layer can be split into three simply because it's interleaved with an absolutely positioned element.
1
348