"average time to resolution" is also susceptible.

Both of these are pretty common all over the place, including OSS e.g. https://isitmaintained.com/#metrics

I suspect this sort of thing is one of the major motivations for the (as a user/reporter) infuriating rise in automated "this bug hasn't been touched in NN days, autoclosing for staleness" bots on various issue trackers.

"There are two ways we can fix this problem: we could make iOS better?"

"..."

    www.youtube.com##ytd-rich-grid-media.ytd-rich-item-renderer:has(a[href='/@MrBeast'])
    www.youtube.com##ytd-rich-grid-media.ytd-rich-item-renderer:has(a[href='/@BeastReacts'])
    www.youtube.com##ytd-rich-grid-media.ytd-rich-item-renderer:has(a[href='/@BeastPhilanthropy'])

If necessary, could treat tables or other complicated compound entries as a single editable item, although given the mysterious passion everyone I've ever worked with seems to have for putting just about everything into a table regardless of need, I'd hope it could be granular to a cell-level, at least.

Trying to collaboratively write complicated documents with a bunch of inter-relations between sections, from different people (in my case, documentation & regulatory paperwork for medical devices) is a massive pain, and I feel like it's too obvious a problem to be confined to my particular niche.

I vaguely recall Word is widely used for preparing huge legal documents, where the content and stakes are probably similar, so maybe there are some solutions, unless they're just "throw interns at it".

[1] https://github.com/CriticMarkup/CriticMarkup-toolkit

- There's no equivalent of "git blame" that I can find to see who/when a particular line/paragraph/section changed.

- I can't see if there's a way to view my changes separate from other edits to the document, or isolate changes by single authors generally.

- "diffing" via the "compare documents" action seems to want to generate a new document with track-changes edits for changes from old/new, but mangles the histories to present all changes as by the invoker of the diff, at that time, which isn't all that useful.

It's definitely better than nothing at all, but a long way short of where I'd hoped we'd be regarding collaborative document authoring at this point.

    perl -ne '/^(?=([abc].*){3})(?!.*([abc]).*\2).{8}k.$/&&print' /usr/share/dict/words

I'm not sure how well that copes with modern security features like cert pinning, but it's closest I can think of.

[1] https://docs.mitmproxy.org/stable/concepts-modes/#transparen...

I just had a quick check and can't obviously see if that has been fixed/worked around in pylsp-mypy, on the off-chance that you might know :)

It can be useful where you've got a mainloop doing some very predictably timed activities, and allows detection of faults which cause your watchdog servicing to occur too frequently.

I think it's quite common in DSP and things like motor control, where you often have hard realtime requirements and things happening too soon is just as bad as too late.

[1] https://www.st.com/resource/en/reference_manual/rm0090-stm32...

    www.youtube.com##div.ytd-rich-item-renderer:has(ytd-channel-name a[href="/c/SOME_CHANNEL_HERE"])

CLI by and large treat the terminal as something to read/write lines to, with maybe some rudimentary interaction support like redrawing the same line for a progress bar etc.

TUI use the various positioning and mode configuration escape sequences of the terminal to (typically) display "full-screen" applications within a terminal.

Vim/Emacs would be obvious examples, or any of the Curses-based menu-ish systems.

Try piping vim (not in batch mode) to a pager, and it doesn't really know what to do.

There is some middle-ground, Github's `gh' command will use a TUI-lite interactive menu prompts for various parameters if omitted, but can run non-interactively and be piped / folded / mutilated etc if the appropriate args are given.

I've looked periodically for something in this vein, but the only one I can see right now is https://pypi.org/project/matplotlib-terminal/ which I haven't had much luck getting running.

No wonder there are some $5 MCUs going for $500+ each (and apparently selling well at those prices, even)