miniblog.

Promoting NO_COLOR as an informal convention for controlling CLI output:

How do you help yourself (and teammates) prevent your JS bundles from becoming too big? You could expose library size in the IDE! Really interesting approach.

How do you help yourself (and teammates) prevent your JS bundles from becoming too big? You could expose library size in the IDE! Really interesting approach.

Finding a bug in GNU Tar, and tracking down the problem: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug (Old tools are often robust, but by no means bug free!)

Estimating the fundamental value of bitcoin by looking at its captive markets:

The entertaining consequences of an IoT toaster oven with an internet accessible video camera:

Prefer API elegance to implementation elegance, and prefer boring code to clever code: https://reactjs.org/docs/design-principles.html#implementation

It's fascinating how smartphone websites often consider *descriptions* to be secondary content! I've seen this both on Amazon and eBay. Apparently the title and pictures are sufficient.

Porting babel and closure compiler to Rust!

If the expression is true, the hardest problem in Computer Science would be naming cache invalidation strategies.

Microsoft's Edge moving to Chromium will reduce browser diversity. However, Safari/WebKit has forked from Chromium. Presumably they'll diverge over time? Browser vendors influence *new* standards, and both Apple and Google will need to do implementation work.

Stack Overflow is adding a new Ask Question wizard, with a lot more structure to guide users!

Programming in Rust has become so much easier than when I first started. Not only the continuing polish of the core tools (e.g. error message clarity, rustfmt is bundled now) but also the increasing breadth and quality of the libraries available!

The use of emoji/likes to signal the end of an online conversation: https://allthingslinguistic.com/post/126044747014/im-especially-intrigued-by-use-13-a-twitter A useful convention!

Reports of a new hardware bug in Intel CPUs, exploiting the Visualization of Internal Signals Architecture: https://hardwaresfera.com/noticias/hardware/se-ha-descubierto-una-vulnerabilidad-muy-grave-en-los-procesadores-de-intel/ My Spanish is rubbish, and I can't find any English coverage yet. Looks like it's from a recent conference and they've given 90 days to patch.