I saw it, it's actually pretty cool. But I suspect it's a very niche thing, and you might see someone build a third party extension.

Most people agree that a screen should feel like a physical desk where windows can pile, overlap, and scatter naturally. Would you use a tiling "system" for your physical desk? I highly doubt it.

Niri's infinite scrolling approach makes that into a rigid filmstrip sequence. It might be interesting for some people though.

This is nice and all, but it doesnt fit my workflow. I have a 4k monitor so I can have 5-6 windows open at once, they are all of different sizes because they are all showing different info and they are all in different places because its physical place is determined by its usage frequency.

In this setup theres the assumption that theres only ever two things Im looking at, and they are equally important because each one is 50/50.

Even if two can be configured to 3, and the 50/50 ratio can be changed, thats not the point, the desktop arrangement is a reflection of the task I am working on, not a rigid pattern enforced by a window manager.

I find these types of wms very bizarre. They must fit some people's mental model but its so far from being useful for me, I just find it fascinating that anyone could find this useful.

Yeah, they all have one quirk or another which seems to make the app your trying to work on impossible. For me, it was always the integration of async event loops w/ the widget framework.

As for the decade old roast, theres a few things I disagree with.

...

Using Qt, one would write:

auto widget = new QWidget{parent}; widget->show();

2 lines, all obvious, all working as expected.

...

No. It's 2 lines, which makes it "not at all obvious." Those 2 lines have so much baked in functionality, I have no idea what its doing until I read 100 pages of documentation and become an "expert" on the internals of that specific UI toolkit.

...

But let’s go into some details. Remember the quote about types? EFL takes that philosophy seriously. Everything is a pointer to something called Evas_Object, which translates to void *. Those knowledgeable in the horrible language of C know it’s a pointer to anything. And so it is.

...

Okay, now we see where the motivation to roast comes from. This guy hates the C language itself, so he's going to hate any GUI toolkit coded in C.

Theres no argument from me that C's syntax makes coding GUIs based on object hierarchies more difficult than languages with proper OO support, but the alternatives have their own problems as well.

At the end of the day, its good to have choices.

You got me there.

I forgot about GNOME/gtk+

Which is odd, because I've written a bit of gtk 3 code.

I don't know, I don't want to say anything negative, only that I'm looking forward to using enlightenment again. :|

Much like physicists who spend their careers searching for a "grand unified theory of everything," I'm a software engineer searching for the UI toolkit that runs on everything.

I wanted it to be enlightenment, way back in the day,

Before becomming enthralled with the widgets of gtk,

Gave both IUP and Agar a try, but much to my dismay,

There were quirks to be found, so I tossed them away.

:|

Last time I tried (few years back) Wayland support was at alpha basically and too buggy for actual use...