Archive for September 5, 2023

Tuesday, September 5, 2023

Forklift 4


We have optimized every aspect of the app to ensure lightning-fast performance. Whether you’re browsing files, transferring data, or managing your storage, you’ll notice a significant improvement in speed. You will experience the biggest change in performance when you’re synchronizing files.

We believe that a great user experience begins with a beautiful interface. ForkLift 4 sports a sleek, modern design that not only looks fantastic but also enhances usability.

It looks pretty good, but I’m not a fan of lists of iOS-style checkboxes. The Settings window seems inspired by the Ventura System Settings, but it doesn’t actually use the same coloring or sizing. I do like that the pop-up menus look like pop-up menus.

Our Newly Added Protocols: Dropbox, Google Drive Team Drives, and Microsoft OneDrive


  • Option to save view options for specific folders
  • Synchronization of favorites through iCloud
  • Option to color the icons in the sidebar
  • Connecting to Amazon S3 buckets with bucket level only permissions and using two factor authentication

They’re “introducing lifetime licenses to a wider user base.” It’s $19.95 for 1 year of updates or $34.95 for 2 years.

See also: John Voorhees.


Update (2023-09-07): Binarynights:

After the release of ForkLift 4 we have received extensive feedback from our dedicated user base expressing their disappointment over the absence of an upgrade path from previous versions of ForkLift.


We will reward existing users by offering an additional 100 days of free updates. If you purchase a 1 or 2-year license and provide your old license key during the purchase, you will receive 100 extra days of free updates on top of the currently available 100 day bonus, totaling 200 days of additional free updates, equivalent to a 54% discount based on the 1-year license.

The macOS App Icon Book

Michael Flarup:

The macOS App Icon Book is a beautiful artbook dedicated to preserving the craft of app icon design. It’s a vibrant journey through the art of desktop app iconography for macOS. The book features hundreds of icons created by designers and developers from around the world over the course of more than a decade.

The icons in the book showcase conceptual and executional excellence in icon design and create a tapestry that tells the story of visual design on one of the most influential platforms of our time. It is both a source of inspiration and a historical archive, inspiring new work and preserving old icons for future generations.

I’ve backed the kickstarter and contributed some icons from the history of my apps, including an unreleased SpamSieve icon. They are still accepting icon submissions.

See also: Iconic:

With a breathtaking collection of unique photography, Iconic: A Photographic Tribute to Apple Innovation takes the reader on a tour of the most visually stunning and important products produced by the world’s most innovative company — Apple. Follow Apple’s journey from 1976 through a photographic collection of their most important desktops, portables, peripherals, prototypes, iDevices (iPad, iPod and iPhone) and packaging.


Update (2023-12-19): Michael Flarup:

I have received my first advance shipment of The macOS App Icon Book. Here’s a little unboxing video showing off the finished book.

Update (2024-01-10): I received my copy of the book today, and it looks great.

Notification Center in Sonoma

Mario Guzmán:

Reminder that Design should be not just about how it looks but also how it works…

I was hoping since we can move Widgets onto the desktop that perhaps we’d get more spacing for Notifications but nope… 😒

Mario Guzmán:

[Look] at how useful it used to be! Everything was clear, legible, none of this “on hover” bs… and look how many notifications you can have in the list view… wow!

Why does macOS continue to just regress?

Both Growl and Notification Center in previous macOS versions (before Big Sur) worked better than what we have now.

Nick Splendorr:

My running theory is that Apple is bad at retaining talent, and shifts people around too often. There’s no way there’s a “Notifications Team,” and instead we’re seeing some work to bring things into visual alignment, then moving on to something else. Like all software, the problem is ultimately mismanagement because you KNOW people in the company are bothered by this, too!

Joe Rosensteel:

I think my favorite are Shortcuts error notifications, because they don’t stack at all. When my Apple TV (home hub) reboots and my thermostats can’t connect I get a new, non-stacking notification every 10 minutes. Who designed that?


How Various Image Formats Compress One-Pixel Images

Jon Sneyers (2016, tweet, Reddit):

However, actual image formats tend to have a “header” that contains quite a bit more information. First of all, the first few bytes of any image format contain a fixed identifier that is only there to say “Hey! I’m a file in this particular file format!”. This fixed sequence of bytes is also known as the magic number.


Headers can contain all sorts of meta-information about an image. Some of it is format-specific information to indicate what kind of subformat is used, and is necessary to decode the pixels correctly. Some of it might not be necessary to decode the pixels, but is still useful to know how to render them – e.g. color profiles, orientation, gamma, or dots-per-pixel.


Besides headers, image formats may have other kinds of “overhead”. They may contain all kinds of markers and checksums, intended to make the format more robust in case of transmission errors or other forms of corruption. Also, sometimes some kind of padding is required, to ensure that the data gets aligned properly.

One-pixel images – the smallest possible images – reveal exactly how much “overhead” there is in an image format.

Jon Sneyers:

In this second part of the blog post, we go to the other extreme: extremely predictable images.

The most predictable image is a large rectangle in a single color.


The uncompressed PBM format obviously has a file size that is (asymptotically) linear in the number of pixels (1 bit per pixel in this case). But JPEG and lossy WebP are also linear in the number of pixels (quadratic in the width of the square) – just with a better constant factor. In other words, they seem to have some inevitable cost per pixel. For JPEG, it looks like you need at least 2 bits per 8×8 macroblock.


The PNG curve goes in a more or less straight line, with some ‘coughs’ and ‘jumps’ around powers of two (1024, 2048, 4096) which might be due to the changing behavior of the underlying zlib compression at such boundary points.