Name</th>	Size</th>	Resolution</th>	Price</th>	Released</th></tr></thead>
LG UltraFine 5k</td>	27"</td>	5120x2880 (5k)</td>	$1300 USD</td>	2016</td></tr>
Apple Pro Display XDR</td>	32"</td>	6106x3384 (6k)</td>	$6000 USD</td>	2019</td></tr>
Apple Studio Display</td>	27"</td>	5120x2880 (5k)</td>	$1600 USD</td>	2022</td></tr> </tbody></table> The table above represented the options for off-the-shelf name brand models available to Mac users until very recently, and they all have problems.</p> Despite its price, the UltraFine 5k has cultivated a reputation for substandard build quality, strange technical issues, and poor customer service and warranty support from LG.</li> The Pro Display XDR is eye-wateringly expensive at $6000, has no webcam or speakers, and its local dimming technology that justified its price in 2019 is now heavily outclassed by that found in the displays of the 14"/16" MBP and 12.9" iPad Pro.</li> The Studio Display has no inputs other than a single somewhat dated Thunderbolt 3 connection and its port selection consists of only 3 USB-C 10GB/s ports, making it underwhelming at $1599.</li> </ul> No matter which you select, you're trading something off and probably paying more than you'd like.</p> The Solution (?)</h3> Considering the situation, when news of a 6k 32" monitor from Dell broke, I was intrigued. On paper, it look great:</p> 32" size (31.5" viewable)</li> IPS Black panel</li> 6144x3456 resolution</li> 223 pixels per inch</li> 1.07 billion colors</li> 2000:1 contrast ratio</li> 450 cd/m² brightness</li> 99% DCI-P3, 100% Rec 709, 100 sRGB color</li> Built-in 4k webcam</li> 14W stereo speakers</li> Thunderbolt 4 w/140W charging, Mini DisplayPort 2.1, and HDMI inputs</li> 4x USB 3.2G2, 2x USB-C 3.2G2, 2.5GbE ethernet, downstream Thunderbolt 4 ports</li> Built-in KVM</li> VESA mount compatible</li> </ul> Looking at these specs, it feels fairly certain that professional and prosumer Mac users — the same crowd who'd consider purchasing one of the three monitors in the table above — is one of the primary audiences that Dell is targeting with this product. Thunderbolt is still a rare sight among desktop PCs and is almost entirely absent from AMD-based laptops, and most Windows using pros would likely prefer one of the numerous more affordable 4k monitors mentioned in the last section. Also lending to this idea is how Dell is offering a Mac version of its display manager app intended for use with this monitor, which is unusual for a company competing head-to-head with Apple in the desktop and laptop computer market.</p> It also feels a lot like the often-wished-for "little brother" of the Pro Display XDR that keeps the 32" size and 6k resolution, but drops the fancy backlighting in favor of something more traditional to bring its cost down.</p> Priced at $3200US, the Ultrasharp 6k 32" is still quite expensive, but for users who don't need the XDR's blistering maximum brightness or support for HDR, it looks like a reasonable value relative to the XDR. Its massive "forehead" comprised of speakers and a webcam make it something of an eyesore compared to an Apple display, but in my opinion it's not that much worse than the LG Ultrasharp 5k with its large top bezel or the now-discontinued 27" iMac with its chunky bezels and even more gigantic "chin".</p> When the monitor became available for purchase on the Dell web store a few weeks ago for $700 below MSRP, I ordered right away with the thought that such a large discount wouldn't be seen again any time soon. After sitting in a pending state for a couple of days it shipped and it came in a few days later.</p> The Reality</h3> Unpacking and setup of the Ultrasharp U3224KB was easy. It comes in a box that's "suitcase style" that has a handle and opens on its side, as Dell has been using for their monitors for some time. The included stand seemed decent, but I didn't test it since I mounted the monitor on a desk clamp arm instead.</p> Build quality is fine, but its back feels notably hollow and plasticy. This doesn't matter too much since the back of a monitor isn't something that's touched frequently, but feels somewhat incongruent with its price. Its buttons and joystick are decent, if perhaps a touch too noisy with their clicks.</p> After plugging it into an M1 Max MBP, its picture showed up after a short but notable delay.</p> While testing the monitor with various content, I noticed something odd: parts of the screen displaying light content were overlaid with a chromatic "glitter" effect. The lighter the color, the more visible this "glitter" was, being most evident on white parts of the screen, and though backing away to normal usage distances reduced its intensity, it was still visible enough to be distracting. I'd heard in the past that some Dell monitors suffered this issue as a result of aggressive anti-glare matte coating, but had never seen it in person. It was disappointing to see, but I thought might be something I just needed to acclimate myself to. In retrospect, this was the first sign of trouble.</p> The virtual real estate offered by the Ultrasharp's 6144x3456 resolution is a noticeable upgrade from the typical 27" 2560x1440 and its 2x counterpart 5120x2880 and fits IDEs like Xcode more comfortably. This was welcome, because things can easily get cramped with all of the editor panes, sidebars, and inspectors open at any given time.</p> Its color is quite good, though a bit less deep compared to glossy Apple displays due to matte coating. Contrast is also good, but to my eye the improved contrast ratio this display's IPS Black panel offers over more traditional IPS panels wasn't readily visible. Despite its high pixel density its sharpness is a bit disappointing which probably another casualty of the heavy matte coating, which makes for a subtle "haze" or softening effect that wouldn't be as noticeable on a lower DPI monitor.</p> Already, I'm feeling some ambivalence creep in.</p> Next up was testing the webcam. The image it delivers, though as detailed as one might expect of a 4k webcam, has major issues with skin tones, turning my face an odd shade of purple or orange depending on if my high CRI desk lamp is turned on or not. It also had trouble handling the lighting environment of a bedroom on a sunny afternoon, badly blowing out highlights. Dell's display manager utility offers some knobs to tweak, but unfortunately nothing to help the webcam with its struggles with lighting and skintones.</p> Its speakers are fine, but not nearly as nice as this monitor's price might suggest. To my ears devices as old as the Thunderbolt Display and as compact as an iPad Pro sound better, which is a bit incredible considering the oversized visual footprint of the Ultrasharp's speakers. They're probably designed primarily with conference calls in mind which is reinforced by the presence of capacitative call control buttons that light up when your hand approaches them on the bottom left bezel, and they're perfectly usable for that, but for media purposes one would be better served by picking up some $50-$100 external speakers or even just leaving your MacBook open and using its internal speakers.</p> By now, I'm beginning to question if makes sense to keep this monitor.</p> While testing it with my Windows PC with the monitor's Mini DisplayPort input, something caught my attention. In the little info panel that shows up when the monitor acquires a signal, it was reporting that it was running with 30-bit color when plugged into the PC and 24-bit when plugged into a Mac. Strange. My first thought was that it was a quirk of the Thunderbolt connection, but this was proven incorrect when plugging my Mac into its DisplayPort input by way of my Dock with a DisplayPort output produced the same result.</p> Some googling later, I came across a thread on the MacRumors forums</a> where other buyers of the U3224KB had found that there's a quirk with M1 and M2 Macs that limits DisplayPort link throughput of monitors connected via Thunderbolt, reducing colors to 24-bit. In the thread it was discovered that if users make use of third party utilities to force a resolution of 6016x3384 — the same as used by the Pro Display XDR — instead of the monitor's native 6144x3456, the quirk disappears and macOS can drive the monitor with full 30-bit color. From that same thread, one poster suggests using a particular model of USB-C to HDMI adapter that can be flashed with custom firmware to allow the monitor to run at full resolution with 30-bit color over HDMI, working around the problem by opting out of DisplayPort Alt Mode, which the quirk seems tied to.</p> To be clear, this is an Apple problem, not a Dell problem. One might surmise that Dell is aware of the issue given the monitor's Mac-inclined target audience however, which makes the lack of mention of it anywhere in marketing materials or documentation feel somewhat dishonest. Additionally, while 24-bit color is sufficient for the overwhelming majority of desktop usage, it's difficult to excuse not getting full functionality at this price.</p> At this point I'd accumulated a couple of weeks of usage on the Ultrasharp, with newness starting to wear off and more subtle flaws becoming apparent. The antiglare coating I hoped I'd eventually be able to tune out was causing a form of eye strain I hadn't previously experienced. Around the monitor's edges, the picture was slightly darkened. The signature "glow" that IPS panels such as this one are known for was more obvious than on my other IPS monitors, being visible even when images with middling darks were displayed.</p> Noticing these papercuts was the straw that broke the camel's back. I pulled up the account page on Dell's website and initiated a return.</p> In Summary</h3> The Dell Ultrasharp U3224KB is a much-needed entrant in the market that comes so close, but fails to stick the landing. Its biggest flaws are seemingly the result of carelessness rather than problems inherent to the technology it's built with: its antiglare coating could instead resemble that of numerous other matte finish monitors on the market instead of being so overbearing and its webcam's woes are almost certainly down to badly tuned firmware, for example.</p> While the experience would have been a bit smoother had I been an exclusive user of Windows or Linux (giving me 30-bit color out of the box), I'm doubtful that I would kept the monitor even in that scenario. There's simply too much about the U3224KB that isn't up to par for its price tag to make any sense. Some of its issues could potentially be fixed with a firmware update, but with the deadline on returns fast approaching, that's not a gamble I wanted to take.</p> At the risk of speaking outside of my field of expertise ("I'm a programmer, Spock, not a hardware engineer!"), my advice to Dell would be the following: next time, leave it in the oven a little longer. Test extensively with a wide range of real world users, gather their feedback, and act on it. Get the details right.</em> In this price range, there is little room for slipping up on execution. But then again, maybe I'm totally wrong and companies will be buying these by the crateload for their designers regardless.</p> Addendum</h3> After submitting the return request, I was back at square one, except this time with frayed patience.</p> This led me to order the VESA mount version of the Studio Display the same day, which I'm now using to type this blog post. Its value to price ratio is still not amazing, but coming away from the U3224KB it seems a little better than it did before.</p> The Studio Display's specs aren't anything to write home about, but it delivers on the finer bits: its antiglare coating curbs reflections well, its colors and brightness are excellent, its picture has no magic glitter effect, its IPS glow is comparatively negligible, its backlight has some of the best uniformity I've seen, its webcam is perfectly usable (it doesn't turn me into Thanos, at least), and its speakers are dramatically better. I plug it in and it works. It's supremely boring, and as it turns out that's exactly what I want in a monitor.</p> Hello World! 2023-02-27T16:25:05-08:00 It's been a long time coming, but I've finally gotten around to getting a blog set up! Getting started on blogging been on my to-do list for many years by now, but things never quite lined up. Lack of time or energy, nothing to write about, life demanding attention elsewhere — it was always something</em>. This has changed in the past several months though, and so here we are!</p> There’s more posts in the pipeline, but for now I’ll talk a little about how the blog is set up.</p> It’s built with the static site generator Zola</a>, which is similar to Jekyll</a> and Hugo</a>, but is written in Rust (as opposed to Ruby and Go, respectively). The original plan was to use Hugo, but it doesn’t support custom syntax themes (or if it does, I couldn’t figure out how), and so I switched to Zola which makes this very easy; just point it to a `.tmTheme</code> file like is used by TextMate and Sublime Text in its config.toml</code> file and boom, code blocks have custom highlighting.</p>` As for why I chose a static site generator over something like WordPress or Ghost, mainly I wanted something simple and extremely low maintenance. In the past I’ve been responsible for Wordpress blogs and did not find the experience particularly enjoyable… the ecosystem surrounding Wordpress is amazing, but it had me putting more energy than I’d like into keeping out the relentless stream of bots poking at the seemingly endless list of vulnerabilities in Wordpress and its plugins in hopes of being able to inject ads or invisible links to assimilate the blog into their armies of linkfarm zombie blogs.</p> `While managed hosting mostly fixes these issues, the other reason for going static generator route is the greater degree control it affords and how it keeps content relatively disentangled from the platform. Lots of packages can read Markdown files, which makes moving to another generator simple. There’s no export step, so migrating is mainly copying a bunch of text files over and maybe making some easily automatable tweaks to the frontmatter sections at their tops.</p>` `The page theme used is a fork of` `nodep</a>, a theme designed to be extremely lightweight that I ran across while searching Github for Zola themes. The fork is called nodep-x</a> and it’s a work in progress.</p>` `For the syntax highlighting theme, I’ve selected Railscasts Extended</a>, which is based on the Railscasts TextMate theme used by Ryan Bates in his Ruby on Rails focused screencast Railscasts</a> (aaand now I’m feeling old). This theme has been what my editors have been configured with for over a decade at this point, mainly because I find it easy on the eyes and it’s been ported to just about everything.</p>` `The hosting for all of this is provided by Netlify</a>. Github Pages would’ve worked fine too probably, but Netlify has some extra features for the same price (free).</p>` `Anyway, that’s about it for this blog’s first post. If you’d like to follow along, a link to my Atom/RSS feed as well as my Mastodon profile can be found on the main page. Until next time!</p>`

wells.dev

Creating an Automator Action in 2023

2023-06-29T00:00:00+00:00

In the previous blog post</a>, why and how I created an updated version of Xcode 10's Automator action template was outlined. This post will cover using the template in Xcode 14.3+ to create an Automator action and integrate it into a host app.

First, download the updated template from its project page on GitHub</a> (if you haven't read the preceding blog post, the short version of why this is necessary is because Apple stopped including it in Xcode at some point, so to create Automator actions in newer versions of Xcode the template must be procured elsewhere). Unzip the template and copy it to ~/Library/Developer/Xcode/Templates/Project Templates/Mac/Other</code>, creating any missing folders along the way.

Restart Xcode if it's open, then depending on your needs do one of the following:


To create a standalone action, select File > New > Project…</strong></li>
To create an action that's bundled with a host app, select your project in the Project Navigator and then in the Project Details sidebar, click the plus icon</li>
</ul>
From there, select "macOS" in the sheet, scroll down to the "Other" section and select "Automator Action". Configure the action to your needs and click "Finish".</p>
You should now have a blank Automator action and can start writing code.</p>
A few oddities to note:</p>

Some of the Info.plist</code> fields shown in the General tab of the action's project page (action name, primary application, summary, etc) will be ignored by Automator if the InfoPlist.strings</code> internationalization file that's created by default is present. If you only plan to support a single language, delete InfoPlist.strings</code> and Automator will fall back on the information in Info.plist</code>.</li>
Xcode doesn't offer a "Frameworks, Libraries, and Embedded Content" section in the General tab of action project pages like it does for normal apps. If you want to use a library or framework with your action, you'll need to switch to the "Build Phases" tab, expand or add the "Link Binary With Libraries" phase, and add the framework or library you need there.</li>
For actions that belong to a host app, in order for Automator to detect the action and make it available without the user installing it manually, you'll need to add a "Copy Files" phase to the host app</em> and copy your built action to the destination of "Products Directory" with subpath ${CONTENTS_FOLDER_PATH}/Library/Automator</code>. This will copy the action into the host app's bundle under /Contents/Library/Automator</code>.</li>
</ul>

The Case of the Missing Xcode Template 2023-06-29T00:00:00+00:00 Over the course of the past few months, I've been slowly wrapping up the development of a little Mac utility and preparing it for release. Part of that process is implementing support for the various forms of automation possible on macOS. Adding AppleScript support and a shortcut for Shortcuts was reasonably simple with a little bit of googling. One might expect that the process of adding an action for Automator, the automation system added in OS X 10.5 and spiritual ancestor of Shortcuts would be similar and according to the tutorials I could find, it is — but there turned out to be a bit of a problem. Following the instructions of online tutorials, it should be possible to select "Automator Action" from the sheet presented when adding a new target to an existing project or when creating a new project in Xcode, but this option is absent in Xcode 14.3. As it turns out, the Automator action template was removed some time ago. I suppose Apple thinks everybody should be focusing on writing shortcuts instead, but I wanted to support Automator since this utility supports versions of macOS back to 10.13 High Sierra, which debuted in 2017 when Shortcuts was still a third party iOS app named Workflow and had only just been acquired by Apple. So I signed into the Apple developer portal and downloaded a copy Xcode 10.3, dating back to 2019, which I figured would have the template, and it did! Great, so all I need to do is copy the template to the appropriate folder, restart Xcode, and I should be able to create Automator actions, right? Well, kinda. While the template did indeed show up in the new project sheet as it should, its icon didn't match the style adopted by recent versions of Xcode, it didn't offer a choice of language to create the project with (locked to Objective-C), and after creating the project Xcode couldn't find the action's Info.plist</code> file. There's apparently a version of the template that supports Swift that was made by an ex-Apple engineer, but I wasn't able to find it, so I set out to build my own. Overall, the process wasn't too difficult, and that can largely be credited to a (blog post on Use Your Loaf</a> and a GitHub gist</a> documenting the innards of Xcode templates. Probably the most annoying part was the debug loop, which looked something like [tweak template] → [restart Xcode] → [create project using template] → rinse and repeat. The updated template can be found on its project page on GitHub</a> and is open for pull requests. If you'd like to read a little bit about how to use it and the bumps you might encounter in doing so, take a look at my other post Creating an Automator Action in 2023</a>. Dell's Ultrasharp 6k 32": Squandered Potential 2023-06-27T00:00:00+00:00 Apologies in advance for not including photos; it didn't occur to me that I might write a blog post about this monitor until it was too late. Still getting used to this blogging thing. The Problem</h3> Recently, I've come into the market for a monitor upgrade. The centerpiece of my hybrid personal/WFH desk setup, an Apple Thunderbolt Display, has been in service for 8 years now. It still works great and has performed well, but as its age increases so do its chances of accruing image defects or failing, and so the time has come for it to pass the torch and retire to the role of secondary monitor. At first blush, shopping for a new monitor seems like it should be easier than ever, with an incredible number of options boasting impressive specs of all sorts. In some cases, this is true. Gamers in particular are in great shape — whether you're playing FPS games and need blisteringly high refresh rates or are more of the type who relishes in the beautiful environments of slower open world games and want top-class contrast and color, there's a monitor for you. Unfortunately, the situation isn't as rosy for Mac users, especially those doing pixel-perfect graphics and development work. In the years since 2015 when my Thunderbolt Display was manufactured, much has changed. Apple exited the monitor business by discontinuing the Thunderbolt Display, went all-in on high DPI across their entire product line, and then re-entered the monitor market with two high DPI monitors. These changes have left their mark on macOS, which has become increasingly dependent on high DPI displays to look good. The past several major releases of macOS even disabled the RGB subpixel antialiasing</a> required to make text appear smooth and legible on more traditional displays. Today, Apple clearly intends for Macs to be used with high DPI displays. This shouldn't be much of a problem with the dozens of 4k monitors on the market now, right? Not quite. This Bjango review of the Apple Studio Display</a> has a section that takes an in-depth look at why 4k monitors, at least those at the more desk-friendly sizes of 27"-32", are suboptimal for macOS and why 5k/6k monitors are preferred. The short version is that the way macOS scales its UI does not lend itself to sharpness and clarity on 4k displays. For the average user this isn't too much of a problem (aside from those with exceptional eyesight), but as mentioned a couple paragraphs back it's not something you want if you're with doing graphics work, app development, or anything else where individual pixels count. I'm a dev who does a good deal of graphics work, so I fall into the latter bucket. So we're narrowed down to 5k and 6k monitors at 27" and 32", respectively. What are our options? Name</th> Size</th> Resolution</th> Price</th> Released</th></tr></thead> LG UltraFine 5k</td> 27"</td> 5120x2880 (5k)</td> $1300 USD</td> 2016</td></tr> Apple Pro Display XDR</td> 32"</td> 6106x3384 (6k)</td> $6000 USD</td> 2019</td></tr> Apple Studio Display</td> 27"</td> 5120x2880 (5k)</td> $1600 USD</td> 2022</td></tr> </tbody></table> The table above represented the options for off-the-shelf name brand models available to Mac users until very recently, and they all have problems. Despite its price, the UltraFine 5k has cultivated a reputation for substandard build quality, strange technical issues, and poor customer service and warranty support from LG.</li> The Pro Display XDR is eye-wateringly expensive at $6000, has no webcam or speakers, and its local dimming technology that justified its price in 2019 is now heavily outclassed by that found in the displays of the 14"/16" MBP and 12.9" iPad Pro.</li> The Studio Display has no inputs other than a single somewhat dated Thunderbolt 3 connection and its port selection consists of only 3 USB-C 10GB/s ports, making it underwhelming at $1599.</li> </ul> No matter which you select, you're trading something off and probably paying more than you'd like. The Solution (?)</h3> Considering the situation, when news of a 6k 32" monitor from Dell broke, I was intrigued. On paper, it look great: 32" size (31.5" viewable)</li> IPS Black panel</li> 6144x3456 resolution</li> 223 pixels per inch</li> 1.07 billion colors</li> 2000:1 contrast ratio</li> 450 cd/m² brightness</li> 99% DCI-P3, 100% Rec 709, 100 sRGB color</li> Built-in 4k webcam</li> 14W stereo speakers</li> Thunderbolt 4 w/140W charging, Mini DisplayPort 2.1, and HDMI inputs</li> 4x USB 3.2G2, 2x USB-C 3.2G2, 2.5GbE ethernet, downstream Thunderbolt 4 ports</li> Built-in KVM</li> VESA mount compatible</li> </ul> Looking at these specs, it feels fairly certain that professional and prosumer Mac users — the same crowd who'd consider purchasing one of the three monitors in the table above — is one of the primary audiences that Dell is targeting with this product. Thunderbolt is still a rare sight among desktop PCs and is almost entirely absent from AMD-based laptops, and most Windows using pros would likely prefer one of the numerous more affordable 4k monitors mentioned in the last section. Also lending to this idea is how Dell is offering a Mac version of its display manager app intended for use with this monitor, which is unusual for a company competing head-to-head with Apple in the desktop and laptop computer market. It also feels a lot like the often-wished-for "little brother" of the Pro Display XDR that keeps the 32" size and 6k resolution, but drops the fancy backlighting in favor of something more traditional to bring its cost down. Priced at $3200US, the Ultrasharp 6k 32" is still quite expensive, but for users who don't need the XDR's blistering maximum brightness or support for HDR, it looks like a reasonable value relative to the XDR. Its massive "forehead" comprised of speakers and a webcam make it something of an eyesore compared to an Apple display, but in my opinion it's not that much worse than the LG Ultrasharp 5k with its large top bezel or the now-discontinued 27" iMac with its chunky bezels and even more gigantic "chin". When the monitor became available for purchase on the Dell web store a few weeks ago for $700 below MSRP, I ordered right away with the thought that such a large discount wouldn't be seen again any time soon. After sitting in a pending state for a couple of days it shipped and it came in a few days later. The Reality</h3> Unpacking and setup of the Ultrasharp U3224KB was easy. It comes in a box that's "suitcase style" that has a handle and opens on its side, as Dell has been using for their monitors for some time. The included stand seemed decent, but I didn't test it since I mounted the monitor on a desk clamp arm instead. Build quality is fine, but its back feels notably hollow and plasticy. This doesn't matter too much since the back of a monitor isn't something that's touched frequently, but feels somewhat incongruent with its price. Its buttons and joystick are decent, if perhaps a touch too noisy with their clicks. After plugging it into an M1 Max MBP, its picture showed up after a short but notable delay. While testing the monitor with various content, I noticed something odd: parts of the screen displaying light content were overlaid with a chromatic "glitter" effect. The lighter the color, the more visible this "glitter" was, being most evident on white parts of the screen, and though backing away to normal usage distances reduced its intensity, it was still visible enough to be distracting. I'd heard in the past that some Dell monitors suffered this issue as a result of aggressive anti-glare matte coating, but had never seen it in person. It was disappointing to see, but I thought might be something I just needed to acclimate myself to. In retrospect, this was the first sign of trouble. The virtual real estate offered by the Ultrasharp's 6144x3456 resolution is a noticeable upgrade from the typical 27" 2560x1440 and its 2x counterpart 5120x2880 and fits IDEs like Xcode more comfortably. This was welcome, because things can easily get cramped with all of the editor panes, sidebars, and inspectors open at any given time. Its color is quite good, though a bit less deep compared to glossy Apple displays due to matte coating. Contrast is also good, but to my eye the improved contrast ratio this display's IPS Black panel offers over more traditional IPS panels wasn't readily visible. Despite its high pixel density its sharpness is a bit disappointing which probably another casualty of the heavy matte coating, which makes for a subtle "haze" or softening effect that wouldn't be as noticeable on a lower DPI monitor. Already, I'm feeling some ambivalence creep in. Next up was testing the webcam. The image it delivers, though as detailed as one might expect of a 4k webcam, has major issues with skin tones, turning my face an odd shade of purple or orange depending on if my high CRI desk lamp is turned on or not. It also had trouble handling the lighting environment of a bedroom on a sunny afternoon, badly blowing out highlights. Dell's display manager utility offers some knobs to tweak, but unfortunately nothing to help the webcam with its struggles with lighting and skintones. Its speakers are fine, but not nearly as nice as this monitor's price might suggest. To my ears devices as old as the Thunderbolt Display and as compact as an iPad Pro sound better, which is a bit incredible considering the oversized visual footprint of the Ultrasharp's speakers. They're probably designed primarily with conference calls in mind which is reinforced by the presence of capacitative call control buttons that light up when your hand approaches them on the bottom left bezel, and they're perfectly usable for that, but for media purposes one would be better served by picking up some $50-$100 external speakers or even just leaving your MacBook open and using its internal speakers. By now, I'm beginning to question if makes sense to keep this monitor. While testing it with my Windows PC with the monitor's Mini DisplayPort input, something caught my attention. In the little info panel that shows up when the monitor acquires a signal, it was reporting that it was running with 30-bit color when plugged into the PC and 24-bit when plugged into a Mac. Strange. My first thought was that it was a quirk of the Thunderbolt connection, but this was proven incorrect when plugging my Mac into its DisplayPort input by way of my Dock with a DisplayPort output produced the same result. Some googling later, I came across a thread on the MacRumors forums</a> where other buyers of the U3224KB had found that there's a quirk with M1 and M2 Macs that limits DisplayPort link throughput of monitors connected via Thunderbolt, reducing colors to 24-bit. In the thread it was discovered that if users make use of third party utilities to force a resolution of 6016x3384 — the same as used by the Pro Display XDR — instead of the monitor's native 6144x3456, the quirk disappears and macOS can drive the monitor with full 30-bit color. From that same thread, one poster suggests using a particular model of USB-C to HDMI adapter that can be flashed with custom firmware to allow the monitor to run at full resolution with 30-bit color over HDMI, working around the problem by opting out of DisplayPort Alt Mode, which the quirk seems tied to. To be clear, this is an Apple problem, not a Dell problem. One might surmise that Dell is aware of the issue given the monitor's Mac-inclined target audience however, which makes the lack of mention of it anywhere in marketing materials or documentation feel somewhat dishonest. Additionally, while 24-bit color is sufficient for the overwhelming majority of desktop usage, it's difficult to excuse not getting full functionality at this price. At this point I'd accumulated a couple of weeks of usage on the Ultrasharp, with newness starting to wear off and more subtle flaws becoming apparent. The antiglare coating I hoped I'd eventually be able to tune out was causing a form of eye strain I hadn't previously experienced. Around the monitor's edges, the picture was slightly darkened. The signature "glow" that IPS panels such as this one are known for was more obvious than on my other IPS monitors, being visible even when images with middling darks were displayed. Noticing these papercuts was the straw that broke the camel's back. I pulled up the account page on Dell's website and initiated a return. In Summary</h3> The Dell Ultrasharp U3224KB is a much-needed entrant in the market that comes so close, but fails to stick the landing. Its biggest flaws are seemingly the result of carelessness rather than problems inherent to the technology it's built with: its antiglare coating could instead resemble that of numerous other matte finish monitors on the market instead of being so overbearing and its webcam's woes are almost certainly down to badly tuned firmware, for example. While the experience would have been a bit smoother had I been an exclusive user of Windows or Linux (giving me 30-bit color out of the box), I'm doubtful that I would kept the monitor even in that scenario. There's simply too much about the U3224KB that isn't up to par for its price tag to make any sense. Some of its issues could potentially be fixed with a firmware update, but with the deadline on returns fast approaching, that's not a gamble I wanted to take. At the risk of speaking outside of my field of expertise ("I'm a programmer, Spock, not a hardware engineer!"), my advice to Dell would be the following: next time, leave it in the oven a little longer. Test extensively with a wide range of real world users, gather their feedback, and act on it. Get the details right. In this price range, there is little room for slipping up on execution. But then again, maybe I'm totally wrong and companies will be buying these by the crateload for their designers regardless. Addendum</h3> After submitting the return request, I was back at square one, except this time with frayed patience. This led me to order the VESA mount version of the Studio Display the same day, which I'm now using to type this blog post. Its value to price ratio is still not amazing, but coming away from the U3224KB it seems a little better than it did before. The Studio Display's specs aren't anything to write home about, but it delivers on the finer bits: its antiglare coating curbs reflections well, its colors and brightness are excellent, its picture has no magic glitter effect, its IPS glow is comparatively negligible, its backlight has some of the best uniformity I've seen, its webcam is perfectly usable (it doesn't turn me into Thanos, at least), and its speakers are dramatically better. I plug it in and it works. It's supremely boring, and as it turns out that's exactly what I want in a monitor. Hello World! 2023-02-27T16:25:05-08:00 It's been a long time coming, but I've finally gotten around to getting a blog set up! Getting started on blogging been on my to-do list for many years by now, but things never quite lined up. Lack of time or energy, nothing to write about, life demanding attention elsewhere — it was always something. This has changed in the past several months though, and so here we are! There’s more posts in the pipeline, but for now I’ll talk a little about how the blog is set up. It’s built with the static site generator Zola</a>, which is similar to Jekyll</a> and Hugo</a>, but is written in Rust (as opposed to Ruby and Go, respectively). The original plan was to use Hugo, but it doesn’t support custom syntax themes (or if it does, I couldn’t figure out how), and so I switched to Zola which makes this very easy; just point it to a .tmTheme</code> file like is used by TextMate and Sublime Text in its config.toml</code> file and boom, code blocks have custom highlighting. As for why I chose a static site generator over something like WordPress or Ghost, mainly I wanted something simple and extremely low maintenance. In the past I’ve been responsible for Wordpress blogs and did not find the experience particularly enjoyable… the ecosystem surrounding Wordpress is amazing, but it had me putting more energy than I’d like into keeping out the relentless stream of bots poking at the seemingly endless list of vulnerabilities in Wordpress and its plugins in hopes of being able to inject ads or invisible links to assimilate the blog into their armies of linkfarm zombie blogs. While managed hosting mostly fixes these issues, the other reason for going static generator route is the greater degree control it affords and how it keeps content relatively disentangled from the platform. Lots of packages can read Markdown files, which makes moving to another generator simple. There’s no export step, so migrating is mainly copying a bunch of text files over and maybe making some easily automatable tweaks to the frontmatter sections at their tops. The page theme used is a fork of nodep</a>, a theme designed to be extremely lightweight that I ran across while searching Github for Zola themes. The fork is called nodep-x</a> and it’s a work in progress. For the syntax highlighting theme, I’ve selected Railscasts Extended</a>, which is based on the Railscasts TextMate theme used by Ryan Bates in his Ruby on Rails focused screencast Railscasts</a> (aaand now I’m feeling old). This theme has been what my editors have been configured with for over a decade at this point, mainly because I find it easy on the eyes and it’s been ported to just about everything. The hosting for all of this is provided by Netlify</a>. Github Pages would’ve worked fine too probably, but Netlify has some extra features for the same price (free). Anyway, that’s about it for this blog’s first post. If you’d like to follow along, a link to my Atom/RSS feed as well as my Mastodon profile can be found on the main page. Until next time!