Enlarge / Moolenaar in 2007. (credit: Sebastian Bergmann via Creative Commons )

Computing as we know it today was built in no small part by individuals who have written open source software—often for little to no personal financial gain—as well as by developers who use those tools. Few tools like that are as legendary and impactful as the Vim open source code editor, the first version of which was written and released by Dutch engineer Bram Moolenaar in 1991.

According to a note published by his family to Google Groups this week, Moolenaar passed away on August 3 at the age of 62. The post did not share his cause of death, stating only that he had been suffering from a medical condition for a few weeks. They wrote :

It is with a heavy heart that we have to inform you that Bram Moolenaar passed away on 3 August 2023.
Bram was suffering from a medical condition that progressed quickly over the last few weeks.

Bram dedicated a large part of his life to VIM and he was very proud of the VIM community that you are all part of.

The note goes on to say that they are arranging a Dutch-language funeral service in the Netherlands for Moolenaar, but that a date has not yet been set.

Invoking another user's privileges to execute a command . (credit: Cavan Images/Getty)

As detailed at Prossimo , a joint team from Ferrous Systems and Tweede Golf , with support from Amazon Web Services, is reimplementing sudo and su. These utilities allow a user to perform actions with the privileges of another user (typically a higher-level superuser) without having to learn and enter that other user's password. Given their age and wide usage, the Prossimo team believes it's time for a rework.

"Sudo was first developed in the 1980s. Over the decades, it has become an essential tool for performing changes while minimizing risk to an operating system," writes Josh Aas. "But because it's written in C, sudo has experienced many vulnerabilities related to memory safety issues."

Enlarge / Curling, like the cURL project, requires precision and is underappreciated.

When you first start messing with the command line, it can feel like there's an impermeable wall between the local space you're messing around in and the greater Internet. On your side, you've got your commands and files, and beyond the wall, there are servers, images, APIs, webpages, and more bits of useful, ever-changing data. One of the most popular ways through that wall has been cURL, or "client URL," which turns 25 this month.

The cURL tool started as a way for programmer Daniel Stenberg to let Internet Chat Relay users quickly fetch currency exchange rates while still inside their chat window. As detailed in an archived history of the project , it was originally built off an existing command-line tool, httpget, built by Rafael Sagula. A 1.0 version was released in 1997, then changed names to urlget by 2.0, as it had added in GOPHER, FTP, and other protocols. By 1998, the tool could upload as well as download, and so version 4.0 was named cURL.

Over the next few years, cURL grew to encompass nearly every Internet protocol, work with certificates and encryption, offer bindings for more than 50 languages, and be included in most Linux distributions and other systems. The cURL project now encompasses both the command-line command itself and the libcurl library. In 2020, the project's history estimated the command and library had been installed in more than 10 billion instances worldwide.

Enlarge (credit: jozefmicic via Getty Images )

As a relatively isolated junior sysadmin, I remember seeing answers on Experts Exchange and later Stack Exchange that baffled me. Authors and commenters might chain 10 commands together with pipes and angle brackets—something I never did in day-to-day system administration. Honestly, I doubted the real-world value of that. Surely, this was just an exercise in e-braggadocio, right?

Trying to read the man pages for the utilities most frequently seen in these extended command chains didn't make them seem more approachable, either. For example, the sed man page weighs in at around 1,800 words alone without ever really explaining how regular expressions work or the most common uses of sed itself.

If you find yourself in the same boat, grab a beverage and buckle in. Instead of giving you encyclopedic listings of every possible argument and use case for each of these ubiquitous commands, we're going to teach you how to think about them—and how to easily, productively incorporate them in your own daily command-line use.

Read 30 remaining paragraphs | Comments

Enlarge / Users can install Homebrew via the Terminal in macOS. (credit: Samuel Axon)

Popular Mac tool Homebrew has long been used by developers and others for package management on macOS, but as we lamented in our first M1 Mac review, it didn't support Apple Silicon when Apple's new Macs first launched late last year. Now, with the release of Homebrew 3.0.0, that's no longer the case: Homebrew now supports Apple Silicon natively, albeit not with every package.

The volunteer Homebrew team made the announcement on the Homebrew blog alongside today's release. While the native support is not yet comprehensive, it bridges the gap significantly, and users can still run Terminal via Rosetta 2 to do what they can't yet while running natively on Apple Silicon. The Homebrew blog post says "we welcome your help" in providing bottles for all packages moving forward.

Here's the full bullet point on Apple Silicon in the Homebrew 3.0.0 release notes:

Read 3 remaining paragraphs | Comments