I think we have far more that we agree on in this conversation than we disagree on
👍
For better or worse, these folks have come to believe that “slick looking” = thoughtfully designed = featureful and advanced. And that “sterile/boring looking” = amateur UX design = complicated and difficult
Well that’s a good point, I’d say if someone’s attention cannot be captured by the content, then that’s a different kind of audience.
I’m probably the opposite: my favorite chat technology is (you guessed it) IRC. (Not despite, but, among other things, because of its minimalism making it much more accessible, since with clients like control over color themes is a non-issue, as well as over distractions such as pictures, website previews or animations.) It’s a learned lesson though, I’ve just been using computers for long enough that I’ve simply learned that things that are full of whistles and bells are almost always ADHD minefields, if not outright waste of time. I’ve learned far, far, far more from man pages in terminal than Stack Overflow (and that’s not even whistle-bell-ey thing.)
Human preferences can be mind-boggling. For f-'s sake if there’s anything that traumatized me more than having to use threads in Google Chat, it’s that I’ve heard people say they liked it. Yeah, I don’t think I’ve ever recovered from that. It’s like clicking the really wrong link on p||
nhub.
We can’t break that mentality in the general public by simply repeating over and over that they’re wrong. It just doesn’t work that way, sadly
That’s why I’m not suggesting to do that.
The right way is just to do the right thing and let the users find out that (or whether) the stereotype is wrong. It’s an uphill battle but IMO that’s just how it works; the good forms will win over long time; they just need to be maintained with patience and honesty. That’s why I’m against this proposal which seems to be just guessing what some unspecified (but large, trust me) group of users surely want.
It’s an “abopt, extend, extinguish” approach and it works. There’s a reason corporate enshitification pioneered that strategy. We can use it too, but for good :)
I guess my point is that you taking it on yourself to distinguish what is “good” or “bad” – that’s the problematic part. (I see that you did not mean that seriously, though…)
nit: you mean
yaml.safe_load()
.