graydon2 | The Rust I Wanted Had No Future:

In a recent podcast about Rust leadership, the BDFL question came up again and Jeremy Soller said (in the understatement of the century) that "I believe Graydon would have said no to some things we all like now". And this echoes a different conversation on reddit where I was reminded that I meant to write down at some point how "I would have done it all differently" (and that this would probably have been extremely unsatisfying to everyone involved, and it never would have gone anywhere).

Boy Howdy would I ever. This is maybe not clear enough, and it might make the question of whether the project "really should have had a BDFL" a little sharper to know this: the Rust We Got is many, many miles away from The Rust I Wanted. I mean, don't get me wrong: like the result. It's great. I'm thrilled to have a viable C++ alternative, especially one people are starting to consider a norm, a reasonable choice for day-to-day use. I use it and am very happy to use it in preference to C++. But!

There are so, so many diferences from what I would have done, if I'd been "in charge" the whole time.

It sounds like I would have very much liked the Rust as it was envisioned…

– via mjtsai.com

Why Emacs has Buffers - Mastering Emacs:

If you’re new to Emacs, you may wonder why you read and write text from buffers as opposed to, you know, files or documents. There’s the fact that it’s not skeuomorphic, and thus the term lacks the spark that connects it to a real-life concept. Most people have heard of files and documents in real life, and the term buffer is instead a capacious term with little grounding to most people.

To computer scientists and programmers alike, however, the term buffer has meaning and purpose; it’s still an unsatisfactory answer, even if it is the real reason why Emacs uses the term buffer. And just leaving it there – that a buffer is a chunk of memory and used as a means of shuttling data to and fro peripheral hardware, like your disk – does not go far enough in explaining why. All editors use buffers internally.

In Emacs, the buffer is the focal point of nearly all user (and machine!) interactions. You read and you write, and you do so in a structure that tugs at its roots in computer science, but it’s so much more than that. And that’s really what I want to talk about, as it will go a long way towards explaining why Emacs and Emacs Lisp is the way it is.

Swift Playgrounds I haven’t had a chance to play with it yet, but it looks like Swift Playgrounds just added all the necessary thing to become a full-on SwiftUI IDE…

5 Signs It’s Time to Quit Your Job – Accidentally in Code:

By now, we’ve all heard of the great resignation. Over the past 18 months or so, many people have had more time to think about what they want from their jobs, and the kind of conditions they are willing to accept.

Of course, the great resignation often glosses over the number of people who died (like “essential workers” who are still somehow not essential enough to merit a living wage) or who were too burnt out to keep going (like healthcare professionals). For knowledge workers, this conversation has often been about perceived entitlement, such as those who don’t want to return to the office.

Regardless, your current job is just a moment in your overall career, and it’s worth thinking critically about whether it’s serving your longer term career goals. So, here are five reasons why you might want to think about quitting.

Collin Donnell - Remove Duplicate Path Entries:

export PATH=$(echo $PATH | ruby -F: -ane 'puts $F.uniq.join(":").chomp')

This is beautiful.