Thinking About The Apple Studio Display

-

iWoz Book raising iMac display

Steve Wozniak continues to support Apple in unexpected ways. His book, iWoz, raises my iMac 27" 5K Retina Display computer to a comfortable eye level.  Long time users of the iMac will recognize this setup, as the stand is not height adjustable.

I confess I have not read Wozniak's book, and no, I did not buy the book simply to adjust the height of my display. Rather, I purchased this book for my son in 2006, who needed a subject for a grade school book report.  Wozniak's goal was to share the thrill of engineering with young minds, and he succeeded. His hardcover book serving as a monitor accessory was a bonus.

When Apple recently announced the Apple Studio Display with a height adjustable stand, my Apple Watch betrayed my heart rate. It was everything I wanted for my next computer: 

  • display separate from the CPU
  • 27" 5K Retina Display with native 2x resolution
  • beautiful construction
  • a height adjustable stand
At $1600 I wouldn't hesitate.  But add $400 for the height adjustable stand, and my Apple Watch recommended that I should breathe.

I watched three popular YouTube hosts discuss this display, ranging from the entertaining and angry Linus who brute forced the "non-removable" plug from the back of the display, to a calm and thoughtful Marques Brownlee who sadly concluded "the Apple Studio Display is a bad deal," to Rene Ritchie who seemed to understand me best: "The mac-nerd heart wants what the mac-nerd heart wants."

I won't need to upgrade until 2024 or 2025 -- enough time for the monitor landscape and pricing (unlikely, but one can hope) to change. Until then, I have the iWoz book, which doesn't look too out of place under my iMac.




Comments

klin said…
I enjoyed iWoz. It's one of the books I read while researching work directions I might take - page 5 of https://www.slideshare.net/KenLin5/garagelabs-startup-insights.
2:30 PM
Post a Comment

Popular posts from this blog

MR2 Check Engine

-
Image
Shown here is the 1991 Toyota MR2. Thanks to the mechanical skills of a family enthusiast, it purrs, growls, and turbo whistles like a dream.   My hardware ability doesn't go much further than oil changes. Rather, my expertise is in software, and I wrote an Android App (iOS version is in progress) to diagnose the flashes of the check engine light. This second generation MR2 predates the OBD2 connector, a standard used to diagnose engine, transmission, and emissions problems quickly and easily. Instead, we have a flashing check engine light which needs some deciphering, followed by a lookup in the service manual. Basically, you count flashes to arrive at fault code number. A short pause (~1.5 seconds) indicates the start of the next digit. A medium pause (~2.5 seconds) indicates start of the next fault code. And a long pause (~4.5 seconds) means the sequence has ended and will repeat. The video below corresponds to the codes 41 and 51. Using the the MR2 Check app and selecting ...
Read more

Bookshelf: UNIX A History and a Memoir

-
Image
  A man page will give you, in black and white, specific information about UNIX. Brian Kernighan's new book adds color and depth about UNIX you won't find anywhere else. I'm not a gray beard (yet), but I imagine they would plow through the book knowingly, but at the same time, learn a few things. Those new to UNIX -- recent college grads or those experimenting with Raspberry Pi -- would be better off starting with Chapter 8 which describes more relatable events and the descendants of UNIX, including Minux and Linux. It's when they start to ask questions like "Where does UNIX come from?" and "Why is Gamora grep?" that they should start from the beginning: Bell Labs, 1969. Kernighan opens with a birds-eye-view of Murray Hill New Jersey, zooms in on the buildings, the offices, the significance of Center 1127, and offers a brief look at some of the key players there. As I progressed through the book, the two factors that made UNIX not just possible, bu...
Read more

Raspberry Pi 5 Resource Limits

-
Image
I was fortunate enough to get a Raspberry Pi 5. I had no particular purpose for it other than to explore it and have fun. On UNIX and Linux based systems, part of that exploration involves checking the default resource limits . The screen shot above is a vimdiff of the rlimits for the Raspberry Pi 400 (left) and the Raspberry Pi 5 (right). Both are running their respective 64-bit versions of Raspberry Pi OS. Four of the 15 resources turned up with diffs, and it's no surprise that the pi5 would have the higher limits. These include the number of processes , the locked-in-memory address space , the number of pending signals , and the realtime priority .  They all serve the common purpose of improving realtime performance.  The last item, realtime priority , is the most telling.  On the pi400, the current and max values are 0.  On the pi5, they are 2.  These settings most likely support hardware destined for the Pi5's new PCIe connector. For a detailed review o...
Read more