@cyberspook @11112011 @7 @bonifartius @helene @ins0mniak > It’s simply more ergonomic and it makes more sense for typing.
I disagree, but there's no objective metric for ergonomics so we're not going to get anywhere. That was the point of the Dvorak rant: it's of dubious value and it's not worth evangelizing a keyboard layout.
> The reason software is designed for QWERTY is the same retarded reason why we still have outdated standards all across the industry and science. Like, look at math. Its notation and numbering system are a fucking disaster.
This was an entertaining rant but misguided. What exactly are you optimizing for? What makes you so certain your solution is optimal? We have a use-case for mathematical notation and it works well enough in the places where it's applied; it's a tool for communication. Who are you going to communicate with? We're here speaking English and it's got a number of infelicities but it gets ideas across and that's the point of language. (It might be interesting to see what would have happened if World War II had not occurred and the Polish mathematicians hadn't been executed, but it did happen and they were executed and their notes were burned and we lost a lot of math, logic, physics.)
The thing you have to optimize for being useful, and useful means a compromise with the situation on the ground. What everyone else uses gives utility to what you use. You decide to work as a cashier at a coffee shop, someone comes in and offers leaves as payment.
> a society tends to be a controlling, standardizing asshole.
You're thinking of it like it's an agent instead of a landscape. Our freeways' dimensions are the sizes they are because that's how big our cars were, which are the size they are because that's how big the roads were, which are the size they are because of the size of wagon axels, and the initial wagons were imported from Europe, and those wagons were the size they were because that's how big the roads were, and the roads were built by the Romans based on the width of their wagons' and chariots' wheels, and Rome built the roads. Nobody's controlling anything, it's not an asshole maneuver: if you're going to make a car, do you figure out the optimal distance for the wheels or do you make a car that fits the road? If you decide to make your car extra wide or extra thin, where do you plan to drive it?
So, nothing's going to
> Tiling WMs differ drastically from stacking VMs
It's really not a big difference. I mean, screen/tmux/acme/dvtm essentially act as tiling interfaces. They're just muxing a VT or a framebuffer. I use both, it makes almost no difference. Lack of sloppy focus was a dealbreaker for me since around the time I started using AfterStep. This is one of the reasons I use qwm (a tiling WM) in Inferno: sloppy focus. When I started using rio more often, the time it took to adjust was nil.
> otherwise might as well say that tablet interfaces aren’t differen’t from stacking or tiling WMs
You're telling me that an Arabian is different from a Kentucky Saddler¹ and I'm saying "Well, look, that's just horse breeds, it's all horses. Here's some weird shit, here's an ox, an octopus." The breeds are only different if you only care about horses or if you only know about horses. If we were talking about horses, that'd be one thing, but we were talking about water for housing an octopus and you come in and say "You don't need that much water if you're riding a"...let's say one of these horses doesn't need as much water². In the context of this conversation, no, not any window manager is *that* different.
I don't know, I understand that you like tiling WMs. I've used them; I still use them. I have used them for years. It's not that different.They're different UI branches of essentially the same thing. "DE" versus "No DE" is a bigger shift. (Let's say a DE is an ox or something. A donkey.⁵)
Speaking of the difference between an octopus and a horse, there is a system called "Octopus". Octopus is different from anything else I've ever heard of. It's tiling, but uses the mouse, except the mouse is used for gestures so you have the same UI on touchscreens, the layout is device-independent and gives a view of the same system to every client, and the UI can also be serialized and deserialized, so your entire system has session save/restore. Here are some of the papers, it's very interesting. Everyone's used a tiling WM: there's not a lot to consider. This is something different, it's something worth thinking about.
> And using the keyboard only in stacking WMs doesn’t count
Presumably tiling WMs that include a floating layer also don't count.
¹ If you are guessing that everything I know about horse breeds I got from RDR, then you are correct.
² I really know nothing³ about horses.⁴
³ Almost nothing.
⁴ I probably should have gone with a different metaphor but I don't want to argue about tiling WMs or Dvorak so I don't want to rewrite that paragraph.
⁵ If I can call Gnome a donkey, then I changed my mind since writing the other footnote⁴ and I like this metaphor again.
2007--ui_in_octopus.pdf2008--using_the_octopus.pdf2012--personal_pervasive_environments.pdf