miniblog.

I really like the gather macro, abstracting the idea of accumulating a list of results: https://stevelosh.com/blog/2018/05/fun-with-macros-gathering/ I often use `yield` for this in Python, but it gives both laziness and accumulation, so the reader has to work out which you wanted.

Huawei developing a FOSS operating system and trying to get it off the ground:

Looking at performance of a new site I've written, and realised I'm slowly serving over 600 KiB of CSS! I suppose the first set of profiling data is often surprising.

PHP is adding union types, and even has a 'false' type to clarify the possible return values from built in functions!

Clippy has a ton of clever lints I haven't seen before. E.g. it suggests that `let _v = println!("hello");` could be `println!("hello");` because a variable of type () is pointless. Warning about recursion in main is an excellent idea too.

On sleep, human factors, and things that are known to improve performance more than technology choices:

Using spaced repetition apps with 1Password to help you memorise passwords without storing them in plaintext: https://boinkor.net/2018/11/memorizing-passwords-with-anki-1password/ Cute idea, although ideally a password manager minimises the memorisation necessary. It's a nice example of composing apps though.

A (slightly dramatic) history of Engelbert's vision for knowledge tools, his prototypes on early timesharing systems, and the transition to personal computers:

"Real languages start with all types on the left, and then drift to the right in old age. Like people." Fun, tongue-in-cheek review of Rust.

As blog comments become increasingly less fashionable, I've often seen people write "email me instead". Perhaps there's a compromise between these? A website could have a comment box that emailed the author. This minimises friction for commenters, but avoids spam on the site.

Excellent discussion of different types of comments, their value, with a ton of examples: https://antirez.com/news/124

I'm increasingly persuaded that the best kind of architecture diagrams are ASCII text art. It seems to be the only format that others will edit. I keep seeing an antipattern where someone draws a comprehensive diagram and it keeps getting used even as it becomes less accurate.

After experimenting with emoji on a range of platforms, I've realised it's really hard to develop a good visual across different platforms. Emoji rendering varies massively based on the system's default emoji set. I ended up using image rendering so all users get the same style.

I've seen steganography in images, but putting secret data in text is a clever idea: https://medium.com/@umpox/be-careful-what-you-copy-invisibly-inserting-usernames-into-text-with-zero-width-characters-18b4e6f17b66