Two Machines, Two Philosophies
My desk has a problem. Well, it has two computers on it, which is probably the problem.
One is an Apple Mac Mini M4 with 24GB of unified memory — small, silent, efficient, and profoundly competent. The other is an HP Z620 tower workstation running a Xeon E5-2690 v2, 64GB of DDR3 ECC RAM, and Debian with XFCE. It sounds like a small jet taking off when the fans spin up, and it happily eats 200 watts under load. I call it the Z620.
Both are my machines. Both run my development workloads. They could not be less alike, and using them both has given me a strangely clear view of what actually matters in a day-to-day development rig.
The Machines
The Mac Mini M4 is Apple's current compact desktop. 24GB of unified memory, a 10-core CPU with 4 performance cores and 6 efficiency cores, a 10-core GPU, and a 16-core neural engine. It sips power — 30 watts under typical load. It runs macOS. It is utterly silent at idle. Storage is 256GB of internal NVMe, supplemented by a 256GB Thunderbolt 4 NVMe drive sitting next to it.
The Z620 is a tower workstation from HP's professional line, built around Intel's Ivy Bridge-EP architecture. The Xeon E5-2690 v2 runs at 3GHz base with a 3.3GHz turbo, 10 cores, 20 threads, and DDR3 ECC REG RAM. Mine has 64GB, a modest NVMe boot drive, and a Quadro K2000 for a GPU. Total internal storage comes to roughly 3TB across multiple drives. It runs Debian 12 with XFCE. It is never silent under load.
The Mac Mini M4 costs around £900 as configured. The Z620 cost me £200 for the bare chassis plus RAM, SSDs, and additional PCIe NVMe storage on top — call it £400–500 all in. These are not the same class of purchase, and I will be honest about that — but they are the two machines I reach for every day, so the comparison is valid in the way that matters to me: practical, daily use.
Development Workloads
For typical development work — writing code, running local servers, working with containers, compiling TypeScript or Rust — the Mac Mini M4 is simply faster, full stop. The M4's single-threaded performance is roughly three to four times that of the Xeon E5-2690 v2. [Source] Tasks that take the Z620 30 seconds feel nearly instant on the Mac Mini.
Compilation is where this gap becomes most obvious. A full TypeScript project that builds in 8 seconds on the Mac Mini takes 25–30 seconds on the Z620. The Xeon has more cores — 20 threads versus the M4's 12 threads — so parallel compilation tasks narrow the gap somewhat. But most day-to-day compilation is single-threaded or lightly threaded, and the M4 dominates.
Container workloads are more nuanced. Docker on the Z620 is fast — the NVMe drive means image pulls are quick, and the many cores help with parallel operations. On the Mac Mini, Docker on macOS runs a Linux VM under the hood, which adds overhead. For running the same containers locally, the experience is comparable, though the Z620's memory headroom means I can run more containers simultaneously without swapping.
Memory and What It Means
The Mac Mini has 24GB of unified memory. This is shared between CPU, GPU, and neural engine. It is extraordinarily fast — the CPU and GPU both access the same memory pool without the latency of copying between separate memory spaces. The 256GB internal SSD plus a 256GB Thunderbolt 4 NVMe drive gives me enough fast storage for active projects, though I have to be more deliberate about what lives where compared to the Z620.
The Z620 has 64GB of DDR3 ECC registered RAM. It is slower than modern DDR4 or DDR5, but the ECC protection means bit flips from cosmic rays or aging hardware are corrected rather than causing mysterious crashes. For long-running server workloads, this matters. For development work, it is mostly peace of mind. The 3TB of internal storage means I never think about disk space — everything lives on the machine, no external drives needed.
24GB on the Mac Mini is enough for my development workflows — several VSCode instances, dozens of browser tabs, Docker Desktop, and a local database. 64GB on the Z620 is arguably excessive for what I do with it, but it means I never think about memory. I could run a full virtual machine alongside everything else and not flinch.
Noise, Heat, and Desk Presence
The Mac Mini is effectively silent. It has a single fan that rarely spins above idle unless I am running a sustained heavy workload. It is warm to the touch but never hot. It sits next to my monitor like a small, polite houseguest.
The Z620 sounds like it is trying to take off. The twin fans in the PSU and the rear exhaust fan are loud under load — 45–55dB at peak. This is not a machine you want in a quiet office. Mine sits beside my desk, and even so, the fan noise is noticeable when it spins up. Under light loads it is quiet enough, but compiling a large project will get the fans going hard.
Heat is proportional to power draw. The Z620 burns through 150–200 watts under full load. The Mac Mini idles at under 10 watts and peaks around 30 watts. Over a year of daily use, the difference in electricity costs is notable — probably £80–100 in the UK, depending on tariffs.
If you share a room with this machine, noise and heat matter. The Mac Mini is a pleasure to live with. The Z620 is a compromise you make because you want that much power on your desk and you have a door you can close.
Operating Systems and Ecosystem
macOS on the Mac Mini means access to the Apple ecosystem — Homebrew, native development toolchains, a properly Unixy foundation, and the kind of UI polish that makes using a computer feel less like a chore. It also means iMessage, Handoff, AirDrop, and the small conveniences that Apple gets right.
Debian with XFCE on the Z620 is a more spartan experience. It boots to a lean, functional desktop. Everything is configurable. Nothing is hidden behind abstraction layers you cannot penetrate. If you want to understand how your system works at a fundamental level, Linux makes that possible. The Z620 is also a far more capable Linux box than it is a macOS box — more RAM expandability, more PCIe slots, more CPU socket options.
I use both daily. macOS for the work that benefits from the ecosystem; Linux for the work that benefits from the raw power and configurability. The Z620 also runs my containerised services — it is effectively a quiet, always-on home server that happens to also be my development workstation when I need it.
Single-Threaded Performance — Where It Counts
Most developer tooling is still single-threaded or lightly threaded. grep, sed, awk, most language interpreters, and many build tools do not parallelise well. For these tasks, single-threaded CPU performance is the key metric.
The M4's performance cores hit around 4,000–4,500 PassMark single-threaded scores. [Source] The Xeon E5-2690 v2 sits at around 1,800–2,000. [Source] This is not a contest — the M4 wins by a factor of two to two-and-a-half in the workload that matters most for daily development.
The Z620's advantage is cores. 10 cores, 20 threads. For workloads that genuinely parallelise — video encoding, large compilations with make -j$(nproc), running many Docker containers simultaneously — the thread count matters. But these are not the majority of my development interactions.
What I Reach For
The honest answer is: most days, the Mac Mini. The performance advantage for the things I do constantly — writing code, running local dev servers, opening a browser with 50 tabs — is significant enough that the Z620 feels sluggish by comparison.
The Z620 earns its place for different reasons. It has more RAM, more internal storage, which makes it better for running multiple heavy workloads simultaneously. It runs my always-on services. It is louder and less pleasant to be near, but it is also more expandable and more repairable. When I need to run something that will peg the CPU for an hour, I go to the Z620 and close the door.
There is a lesson in here that has nothing to do with Apple versus Intel, or x86 versus ARM. The machine that wins on paper is not always the machine you reach for. Context matters enormously — desk placement, noise tolerance, the specific workload, whether you are in a rush or not. Both of these machines earn their desk space. The Mac Mini is better for most things. The Z620 is better for some things, and more honest about what it is.
If I could only have one, it would be the Mac Mini — not because the Z620 is bad, but because the M4's single-threaded performance makes daily development feel genuinely fast. The Z620 is a workstation from a previous era that still has its moments. The Mac Mini M4 is from the current era and it shows in every interaction.
