This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
I respectfully disagree; 2D ancillary menus have several significant benefits over a bare terminal, but they still need a 1D terminal in that menu. And I get that there was a significant time period, specifically between 1986 through 2006, where this wasn't the case.
But when I have two programs that start with the same name, like say Visual Studio and Visual Studio Code, I'd have to type out the entire name to access the second application. (I'd also have to know the name of the binary, that doesn't necessarily match the name on the box, and sometimes it isn't even a binary, but a part of one [so now you have to memorize the launch argument, and tab-autocomplete generally won't help you with that].) With a proper menu representation (and I admit the Windows 10 and 11 are very much not this; StartAllBack is mandatory on Windows machines), the sequence is 'vis' (or similar) + [down arrow] + Enter, speed the terminal cannot hope to match (unless you decide to manually configure an alias for it- but a general purpose solution for this is a lot more convenient, because it works everywhere, which is the same argument vi users make about learning it).
Selecting text and objects is something else that has an intrinsic 2D representation for reasons that become obvious if you don't know how long the line is (which you kind of have to for terminal-based selection), or if you need to see the document you're copying from as well as the document you're pasting to.
Menus are preferable here because, on an ATM, they're literally just keyboard buttons that map directly to the action. If you want to withdraw 200 dollars, you don't have to translate '1. View Balance. 2. Deposit. 3. Withdraw.' -> 'Enter amount to withdraw' into keyboard commands, you press the [equivalent of the] 'Withdraw' keyboard key, and then the '200 dollars' key. There's no potential of anyone misreading or mistranslating the input, since the menu changes based exactly on what's relevant at the time; it's drastically more intuitive.
Computer interfaces have legitimately advanced since 1970 and that's OK. They took a huge leap forward back when the OS wars weren't yet won, then slowed down, then came back for a time when OS X became relevant again, then desktop UX took a backseat to mobile UX. (Which made a great leap forward in 2007, then another just as large one in 2009 with webOS, and then regressed to where we are today.)
In my opinion the world is overdue for a new desktop UX paradigm, since unlike the 2010s it's now crystal clear that desktop PCs (including laptops) will never go away, and it's time we go after the things we missed the last time, like how to display text in readable locations and not to truncate the important parts (which is also something the terminals still have problems with in applications that show data in tabs). Maybe once someone figures out how to get an LLM to spit out all the hooks and hacks you need to reliably replace explorer.exe (not that the Windows source code isn't in LLM training sets already, of course), we'll finally get someone applying the UX research the rest of the way.
Yeah, they're clearly picked in spite of it.
Unless you're Tesla or (to a point) Rivian, but those are software companies that just happen to make cars. Every "X drives" video I watch on YouTube has the infotainment clearly lagging by a half second or more, and with the absurd power of even 15 year old computers this is just not a thing that should happen. Car UX was legitimately better when the engineers (or rather, the execs directing the engineers) were forced into the simplest embedded development; as soon as they got access to something more advanced than embedded C it all went to shit.
And at this point I think good car UX is dead and buried because consumers aren't even in any position to care. Hey, at least the auto lanekeep will stop you from leaving the lane after you get flashbanged by drivers who are too brain-dead to turn their fucking brights off (or you're too busy fucking with the infotainment's lack of switches to be able to stay in your lane).
More options
Context Copy link