@lightweight I think there's a happy medium to strive for here: Software should strive to be userfriendly (meaning it is helpful, doesn't waste people's time, & is reasonable to learn), but often I hear "user friendly" used to mean "I don't want to learn something new". Which isn't a reasonable ask when trying something new.
Ofcourse what is considered "userfriendly" is somewhat (but not entirely) subjective, & we need leeway to create something better than you're used to!
@teleclimber in my experience, people, in fields where their role *depends on their digital capabilities* resolutely refuse to learn. It's both risky (short-sighted for people with those role responsibilities) and a pathetic abdication. They tend to lack pride in their skills and competence.No wonder people get such little job satisfaction because they're voluntarily disempowered. 1/2
@Sexypink Not entirely what prompted this toot, but if you're responding to the "/2?" I can sometimes make educated guesses about how long my threads will be.
* Deprecated regular-expression engine, disabled in all builds * 3rd file full of sub-pseudoteletype routines * Another globbing implementation * Expose events to TCL * Logging, including to TCL channels * Abstractions around TCL channels * TCL breakpoint debugging * Stdlib adaptors to previously-internal APIs
I'm not entirely sure why TCL includes all this code, beyond there appearing to be a traditional distrust in the standardization of UNIX"s standard library.
Covering a few days later than I thought I would, but what else do I see in Expect's codebase?
* Deprecated `select`-syscall I/O utilities, disabled in all builds * API around terminal-windowsize accessing IOCTLs * It's own date-formatting utility * Opening sub-pseudoteletypes * Implementation of glob-patterns * Utilities upon those sub-pseudoteletypes, across 2 files * Multiple sources for input events, including a noop one * Configuring redirects on /dev/console * Legacy cleanup routine
@privacybrowser The thing that strikes me here is that not only do I believe this offer would be harmful to your users if implemented, but also harmful to takeads' customers by lying in their statistics. But I guess it makes the number go up...
I think this is a great corporate-political move for iOS Safari to benefit the web even if not their users.
As an upstart browserdev it is not appropriate for #Haphaestus to follow through! It is my prerogrative to question the Attention Economy leading to the all the excitement I see for this, & instead implement aggregatated pull notifications most sites still support.
Folks, it’s encouraging to see more of you writing alternative text on images here so people who use screen readers can also take part but please make sure the text really is the equivalent of the image.
So, for example, if you’re posting a screenshot of some text, don’t just say “Excerpt of article” or “A tweet by so-and-so” but actually copy/paste the text from it (many platforms let you do this with images these days).
Folks who use screen readers have the right to hear what we see.
A browser developer posting mostly about how free software projects work, and occasionally about climate change.Though I do enjoy german board games given an opponent.Pronouns: he/him#noindex