Top all-time · #10142
Pekka Paalanen
Personal blog · ppaalanen.blogspot.comsystemsprogramming
Pekka Paalanen's personal blog at ppaalanen.blogspot.com covers systems and programming. Since 2012, 8 different Hacker News readers have linked it 10 times. It is still writing: the last post was on 2025-03-13, and you can follow it by feed.
Too few sampled comments (7) to say how often HN recommends it.?
Why HN links it
HN commenters link this blog for its technical posts on Wayland and Weston, especially repaint scheduling and display latency. They cite its graphs and explanations when discussing compositor timing.
Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /2015/02/weston-repaint-scheduling.html4 people · 4 mentions · first linked 2019-09-22
What Hacker News says?
Wayland's latency was improved a few years ago to about half a frame, there's probably more room for improvement, but I think just getting a 240hz monitor is better investment of resources: https://ppaalanen.blogspot.com/2015/02/weston-repaint-schedu... The only applications strongly sensitive to latency are video games or similar, and they take a special low-latency path through the graphics stack, exclusive full-s…
Comment linking /2015/02/weston-repaint-scheduling.html
on “Understanding the working of X11 from the ground up (2017)”Submitted Testing 4x4 matrix inversion precision (2021) as a story · 4 points
HN discussionYeah, mutter/gnome-shell was pretty awful. Weston and wlroots (Sway/Wayfire/etc) never had the issues Gnome had. In fact Weston since 2015 has had a clever delay algorithm that allows clients to hit the very next frame if they sync to presentation-time feedback: https://ppaalanen.blogspot.com/2015/02/weston-repaint-schedu... (And Sway has a configurable delay; since Sway is so simple to render, the recommended max_f…
Comment linking /2015/02/weston-repaint-scheduling.html
on “Firefox 75 on Wayland now to have full WebGL, working VA-API acceleration”Submitted Weston on Android: desktop-shell as a story · 1 points
HN discussionMy point is, regardless of who does what when it comes to color management Wayland simply cannot be agnostic about it. At least since it wants to touch pixel data. Alternatively they could have given up on that and never introduced wl_buffer, leaving all the buffer management and drawing up to the client. edit: At least HDR has finally made Wayland devs wake up and smell the coffee. A good write-up here[1], with ong…
Comment linking /2020/11/developing-wayland-color-management-and.html
on “Window System X (1984)”Submitted Wayland on Android as a story · 1 points
HN discussionPekka Paalanen wrote a nice blogpost about the concept of repaint scheduling with graphs: https://ppaalanen.blogspot.com/2015/02/weston-repaint-schedu... (note that the Weston examples gives a whopping 7ms for composition). I'm making some assumptions about your chart as it is not to scale, but it looks like the usual worst-case strategy. Given a 60Hz refresh rate and a 1ms composition time an example of an optimize…
Comment linking /2015/02/weston-repaint-scheduling.html
on “Optical PCIe 7.0 connection hits 128 GT/s”>This happens in a buffer and is normally one display update behind in time. This assumes compositors perform their work right after each display refresh. Compositors can decide to perform their work later, some amount of time before the next display refresh (e.g. a few milliseconds). This allows to reduce latency because the new buffers submitted by clients (such as web browsers) can be displayed with less than 1 r…
Comment linking /2015/02/weston-repaint-scheduling.html
on “Pointermove event latency in web browsers”In case you haven't seen it, there's a new approach to Wayland/Weston on the Raspberry Pi. http://ppaalanen.blogspot.com/2013/05/weston-on-raspberry-pi...
Comment linking /2013/05/weston-on-raspberry-pi-accelerated.html
on “What people use their Raspberry Pi's for”I really don't understand this stance. I try to keep current on Wayland implementation work and was around when the Mir debacle was originally going down (and prior to it, when Canonical stated they would contribute to and use Wayland!). Writing a competing implementation when you could simply (and announced you would!) contribute to an existing open-source project, then publishing articles with misleading and vague…
Comment linking /search/label/android
on “Shuttleworth: Free software zealots are antisocial muppets who love to hate”