On windows at least, I almost always use 'alt+space; x' to maximise windows, as well as winkey+left/right/up/down, which is really the only resizing I do. Having to use the mouse is a pain.
Perhaps a combination of the two? Maybe standard drag-and-drop works as usual, but if you drag the item to some deadzone (like the side of the screen?), it will stick and you're free to scroll to where you want to put it.
Not too hopeful with accessibility, as it isn't pleasant to use at all with reduced motion enabled. They flicker when added and linger around when swiped away.
Wireless keyboards (like the one linked) typically use ZMK instead to my knowledge. It's similar to QMK—so much of the knowledge still applies—but it isn't 1:1.
Wouldn't you still be as sluggish as the GUIs you mention since it's HTML5? Is the benefit from only rendering a subset or something? I'm struggling understanding how rendering a page into a terminal is faster than just rendering to a regular window. It just seems like another layer between the browser and the GPU.
I think you have a misunderstanding of the full system. Like you are thinking the GUI is much simpler than it actually is. Conversely I think you're thinking that CLIs are much more complicated. There's a lot more going on than just painting pixels on the screen. Maybe start by asking why vim is several magnitudes less resource intensive then Microsoft word. Then ask the same about neomutt vs Thunderbird vs outlook/Apple Mail
I'm also not sure why you think it's an extra layer between the gpu. Both the browser and terminal emulator are sitting in top of the OS. But also remember if you run headless then your OS doesn't need to load the desktop environment, though you can still use the CLI. At this point clearly the GPU is seeing less, right?
I understand that a GUI is complex, which is why I'm confused about the performance benefit as HTML5 already acts like a GUI. Even if it's a terminal program, it would still need to calculate the layout and handle the DOM to remain compliant, no? A website can be as intensive as Word.
My logic with it being an additional layer is that instead of the browser rendering text to the screen, it would have to speak with the terminal for the terminal to instead render text to the screen. Same goes for rendering graphics. Besides a headless system I don't see much of a benefit to it.
