Here’s Vim editor thesaurus completion. This kind of completion has its various limitations that I might detail later. I mentioned thesauri in passing but my Internet connection is pitiful and writing about editor meta feels a bit bizarre.
More Vim editor meta? Since posting a video of my LaTeX/Vim shenanigans, queries for tips arrive occasionally. Completion and whole line completion are boilerplate hammers. The more buffers and windows loaded, the more “robust”.
Banana trees are kind of invincible. Here’s what happens if you chop a sufficiently radioactive one clean across the mid…
I caught a glimpse of an interesting thing by chance.
Meta Platforms
Facebook hid the x
from their login prompt on
public pages–including government pages, then brought it back. ‘Twas on the
desktop before mobile and perhaps (who knows) for a subset (as a test). A “login
only public page” is for a near–distant future, set. Seriously though;
developer documentation will become my
final excuse to visit Facebook.
Isn’t this a beautiful lithographic painting? (Don’t worry, I got permission from the relevant authorities to post this)
The Chrome experimental recorder tool has been around for a long while. I thought it was still mostly but I got schooled and apparently, this is a more faster way to jump–start a puppeteer script/test:
Browser rendering engine feel: Webkit (Safari), Blink (Chrome) or Gecko (Firefox)?
Which browser engine “paints” the smartest on my device? In the clip below; Surf substitutes for Safari and Chromium for Chrome. My blog is the testee since there’s guaranteed cache control and jitter.
Surf and by extension Safari (or any Webkit–based browser) wins . Webkit feels smooth (sneakily, too smooth). It’s probably partly why Safari on macOS/iOS feels so fast. Chrome (not Chromium) is almost on par or so I’ve been told. Not exactly web dev but interesting huh?
Strange. In the last few years, I’ve abandoned search engines for most programming related queries by chugging along happily with Recoll. If I had the time I’d sit down and hack out a web front–end for its Python API but the desktop interface supplied with from my own web crawlers works beautifully (medoc92/recollwebui also exists).
Messing around with a statically generated site can easily lead into a web/browser spec rabbit hole. And… that’s when I remember exactly why everything ends up written outside the browser’s framework into a framework. I think Firefox is still the only browser that allows easily setting image fallback styling completely with just ?