I do not know exactly what all that means but does it needs to be desktop wide or just inside a specific app window?

Neither way works in Wayland. A program can know where it was clicked but not where the pointer was immediately before that. For that matter Wayland doesn't have a concept of "the" pointer; there may be multiple pointers.

I don't think this is true. As per wayland protocol docs (https://wayland-book.com/seat/pointer.html):

> Using the wl_seat.get_pointer request, clients may obtain a wl_pointer object. The server will send events to it whenever the user moves their pointer, presses mouse buttons, uses the scroll wheel, etc — whenever the pointer is over one of your surfaces. [...] The server sends this event when the pointer moves over one of our surfaces, and specifies both the surface that was "entered", as well as the surface-local coordinates (from the top-left corner) that the pointer is positioned over.

So the program should know the pointer's local coordinates.

Surely programs can know where the pointer is as long as it is over a window that belongs to the program. Otherwise hover wouldn't work.

Hover is done by the client telling the compositor it would like the cursor to change its shape if it is over a certain area the client is drawing. But the client does not know where the cursor is or where on the screen the client is (or even if the client is visible at all).

I like it. Currently I'm using BeerCSS and I'm pretty satisfied with it. This library is smaller. Any other selling aspect vs BeerCSS? Thanks!

I wanted to try it. How to install it on Opensuse (Tumbleweed)? I was unable to install the rpm for Fedora.

Fully agree on templates but I use Phlex to build UIs with pure Ruby on the server side. A pleasure to work with. And with something like Datastar, reactive UIs with practically no js.

I really don't like Hotwire and FE history (I'm playing with htmx, Datastar, Phlex and love it) but the ActiveSupport autoloader -> to Zeitwerk migration was pretty much something in the background, an implementation detail, at least in my experience. Most devs don't even know what is all this about.

Niri supports [floating windows](https://github.com/YaLTeR/niri/wiki/Floating-Windows). I think is the same as stacking, right?

No, stacking in i3 (that's what I was referring to) it's vertical tabbing. I've seen that Niri supports tabbing so I guess I just have to give it a spin to see if it fits.

From time to time I enter its website and think that it's a great concept. Anyone using it as daily driver?

I like it, specially the Phlex choice. I'd like to know if this framework would work nicely with Datastar js library and its extensive SSE usage. Thanks

Sh*t, just realized that Liskov SP collides with LSP from Language Server Protocol :(

Looks very nice, I just watch a great YT video from the developer here https://www.youtube.com/watch?v=DYWTw19_8r4

It's so rare to see such a clear and intuitive explanation. This video is amazing.

This. It is a rare and unique thing for the author to a) have the skills to put together such a presentation and b) take the time to do so. Thankyou.

Just watched some of his videos and they are really good. Kudos @nicoburns

The developer is rediscovering the concept of a GUI library. The modern variant is the mouse-driven GUI developed by Xerox in the 1970s (and later commercialized by them as Xerox Star) which Jobs famously copied to create Apple’s Lisa, and Gates famously mimicked to create MS Windows. Since they determine the look and feel of a platform and their design determines the ease with which developers can create apps for the platform, GUI frameworks became pivotal to platform wars across all sorts of products, from OSs to browsers, graphics engines and anything else whose success was determined largely by the interface developer experience.

I'm a gray beard like you probably but I disagree with this statement.

This library makes use of modern composable components, is declarative driven and not imperative; and doesn't do immediate rendering in all cases.

It can target incredibly different backends, e.g. DOM/canvas/raylib.

All of this in modern C as a `.h` library alone.

These are great features and not just a 'youngster discovers' project.

Maybe a README that shows how it works and what it does would help. As it is it is quite opaque IMO, with just a few high level comments.

The README for the project is one of the most detailed READMEs I’ve ever seen. The landing page for the website has as much detail as you can reasonably expect, even including a couple of feature demos. There are clear links to the docs and the code.

The developer has clearly put a lot of thought into this content. Worth taking a second or two to see what’s available before criticising it.

It's in the repo; landing pages are usually for generating interest.

https://github.com/nicbarker/clay

I swear to god, I thought this is AI generated response.

I’m still not sure it isn’t