It's an over-simplification of Chinese idiom "浑水摸鱼", which is literally 'catching fish in muddy water'. Origninated from Thirty-Six Stratagems (三十六计). It generally mean "to take advantage of a chaotic situation or a crisis". It is later extended to express slacking off.
I'm using a [Gprinter GP-1324D](https://www.ebay.com/itm/365264659480) in everyday work, printing task tracking stickers, various labels, etc. It's designed to print shipping labels / recipients in business scenarios so it's fairly robust. The only con I can think of is its physical size. I'm not familiar with eBay, but on Xianyu(Chinese second hand market app), yes you can buy one using only $20, shipping included.
If done comprehensively, this strategy has the potential to be much better than a traditional stacktrace because you can embed local variables within each additional error context string.
The main problem with traditional stacktraces is that, while you get line numbers, local variables at every stack frame are not preserved. So unless the error is obvious like FileNotFound, you’re left guessing as to how the error happened.
While still being hella verbose and probably too much effort for most code, the upfront investment would obviate the need for adding debug print statements or dropping into a breakpoint to inspect the code after an exception.
That said, the post does feel like copium for the ridiculous verbosity in Go and re-inventing chained exceptions.
"Disabled" is not metric among those who have disabled it, while WebGL enabled allows identifying different browsers with WebGL enabled.
I know what you mean, but statistically, I don't think that it is easier to guess the person from those who have disabled it versus the list of all browser fingerprints where is that matching or very close unique fingerprint.
Unless you disable all JavaScript you’re leaking something.
Honestly, you’re still leaking a bit without js, as long as where you’re connecting to is checking.
The game is just choosing what you’re okay telling wherever you connect to.
It makes you look the same as everyone else with webgl disabled. This happens to be a reasonably large number of people, because it's the default setting in a variety of privacy focused browsers.
I’ve been using Firefox since the Quantum version is out. It feels slightly slower to Chrome but it's negligible to me. Otherwise I can't tell a difference (except some heavy web based Office like solutions screaming 'Your browser is not supported!' but actually works fine).
not that I know of. I had a lovely system that had audio alerts for all sorts of things and multiple time windows for comparison and statistics etc. long ago now, big mass of python script tuned for that environment.
Made my office sound like a jungle: bird chirps for firewall probes, coin clatters and cash register "Kaching!" for sales page hits and actual "someone gave us money" sales, etc. It was fun.
