shabble

the double questionmark `foo??` is sometimes also useful, since it'll show full source for the function/method/thing if you do it to a function.

"People keep saying Macos is better than iOS..."

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

"..."

After being annoyed by this (and a handful of persistent others) a few too many times, I ended up with the following ublock rules:

    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'])

I don't think some sort of vaguely granular "last edited by XXX at YYY" annotations/tooltips/whatever would be too outrageous a feature to confuse everyone.

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".

maybe I'm just doing it wrong, but having looked at these capabilities occasionally, they seem pretty weak.

- 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.

and to squash a little further:

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

A more specialised variant that's also quite common is the "window watchdog" peripheral, which is similar to the timer version, but will also trigger a reset if the keep-alive signal arrives too early, as well as too late.

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.

I have a ublock rule like:

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