10 interesting stories served every morning and every evening.

Running local models is good now

vickiboykis.com

I’ve been work­ing with lo­cal mod­els since they came out, and fi­nally, they’re sur­pris­ingly good now.

I have a 2022 M2 Mac with 64 GB RAM and 1TB stor­age and I’ve used

Mistral 7B

Gemma 3

OpenAI OSS-20B

Qwen 3 MOE, as well as a num­ber of other Qwen vari­ants like Qwen 2.5 Coder

across a lot of dif­fer­ent sys­tem se­tups like

raw llama.cpp with Open WebUI

llama-cpp-python

Ollama

lla­mafiles and

LM Studio

Where are lo­cal mod­els now?

Early on, mod­els were slow, hard to use, and just not that ac­cu­rate for most pro­gram­ming tasks. The idea that lo­cal mod­els were se­verely lag­ging be­hind was largely true un­til, for me, the re­lease of GPT-OSS. I have no con­crete sci­en­tific ev­i­dence of this - my own per­sonal vibe met­ric of is a model good enough” is, do I have to dou­ble-check it against an API model”, and GPT-OSS was the first one where I started do­ing that a lot less of­ten.

As a re­sult, I’ve mostly been us­ing lo­cal mod­els as fast, per­son­al­ized Google for de­vel­op­ment ques­tions that don’t re­quire re­cency.

But with the most re­cent re­leases from Google in the Gemma 4, fam­ily, I’ve fi­nally been able to do agen­tic cod­ing lo­cally and have loops work at about ~75% the ac­cu­racy/​speed of fron­tier mod­els, which is in­cred­i­ble.

I’ve so far been us­ing gemma-4 – 26b-a4b LM Studio im­ple­men­ta­tion as my de­fault lo­cal model. I’ve used the lo­cal setup so far to: Refactor a Python script that was a note­book into a repo of 5 – 6 mod­ules, lint that mod­ule to use cor­rect type hints for gener­ics (most fron­tier mod­els now do this au­to­mat­i­cally, but not al­ways).

I’ve also used it to proof­read some blog posts, write unit tests, and to boot­strap a repo that stands up a two-tower model for rec­om­men­da­tions just to see what the agent would do with a blank slate. Here’s what it gen­er­ated, which was pretty ba­sic but still be­yond the scope of any­thing I would have thought pos­si­ble last year:

Note that the en­vi­ron­ment is re­stricted be­cause I run all my agen­tic work­flows in a Docker con­tainer with lim­ited ac­cess to ex­e­cu­tion.

I’m also build­ing an app that sur­faces trend­ing top­ics from Arxiv pa­pers. Out of cu­rios­ity, I had Pi go through my past LM Studio ses­sion logs and fig­ure out what I was us­ing LM Studio for:

Unsurprisingly, since I’ve been work­ing on Rijksearch,

None of these are ground­break­ing tasks (again, a lot of per­son­al­ized Google/docs lookups), and work­ing on them does give my GPUs and RAM a work­out and the K-V cache grows to 64 GB RAM.

But, the larger story for me is that these kinds of tasks, even as sim­ple as they are, used to be im­pos­si­ble for lo­cal mod­els as re­cently as 6 months ago.

Gemma-4 – 12b-qat just came out but I’ve al­ready also re­ally been im­pressed with its per­for­mance rel­a­tive to its size. The model ar­chi­tec­ture it­self is re­ally in­ter­est­ing and pro­poses a bunch of in­ter­est­ing ques­tions like, if we are con­strained by per­for­mance and price, what ar­chi­tec­tural trade­offs do we need to make?” a ques­tion that so far has not re­ally been asked in the mad to­ken gold rush.

Running agen­tic mod­els lo­cally to­day

But don’t take my word for any of this, try it out for your­self! You’ll need a lo­cal model in­fer­ence en­gine, an agen­tic har­ness, and the lo­cal model ar­ti­fact if you want to try to run lo­cal agen­tic flows. You’ll need to set up the har­ness to point at your lo­cal in­fer­ence end­point, the down­loaded model ar­ti­fact served via the in­fer­ence en­gine.

For my lo­cal setup, I’m cur­rently us­ing Pi as the agent har­ness and LM Studio as the in­fer­ence server, al­though it would likely be faster if I just used llama.cpp di­rectly - a po­ten­tial di­rec­tion for a fu­ture ex­per­i­ment.

This post was very easy to fol­low to set up agen­tic cod­ing with Pi and LM Studio, al­though I did make a few tweaks to the post’s setup.

Model: The post rec­om­mends Gemma 26B A4B , but gemma-4 – 12b-qat is more re­cent and smaller and faster, with­out much sac­ri­fice in ac­cu­racy.

Security: I run every Pi ses­sion in a Docker con­tainer and give it per­mis­sions only to bash so that it can’t run Python code or do web brows­ing, al­though I do plan to al­low curl in a dif­fer­ent im­age for some re­search work I’m do­ing.

Agent Harness Config: Since I run every­thing in Docker, I edited Pi’s mod­els.json in or­der to get Pi to talk to the model.

lmstudio”: { baseUrl”: http://​host.docker.in­ter­nal:1234/​v1, api”: openai-completions”, apiKey”: not-needed”, models”: [ { id”: google/gemma-4 – 12b-qat”, input”: [ text”, image” ] } ] }

Here’s my Docker Compose con­fig:

ser­vices: pi: build: con­text: . dock­er­file: Dockerfile im­age: pi-agent:0.74.0 init: true stdin_open: true tty: true ex­tra_hosts: - host.docker.internal:host-gateway” en­vi­ron­ment: ANTHROPIC_API_KEY: ${ANTHROPIC_API_KEY:-} OPENAI_API_KEY: ${OPENAI_API_KEY:-not-needed} GEMINI_API_KEY: ${GEMINI_API_KEY:-} OPENAI_API_BASE: ${OPENAI_API_BASE:-http://​host.docker.in­ter­nal:1234/​v1} # note that you’ll need to spec­ify a base if you also use OpenAI to ac­cess OpenAI’s ac­tual com­ple­tions end­point WHATEVER_API_KEY: ${WHATEVER_API_KEY:-} vol­umes: - ${HOME}/.pi/agent/models.json:/config/models.json - ${WORKSPACE:-.}:/workspace - pi-con­fig:/​con­fig - pi-ses­sions:/​ses­sions work­ing_dir: /workspace

vol­umes: pi-con­fig: pi-ses­sions:

and here’s the bash script that runs pi .

#!/usr/bin/env bash

# Pi — Start the con­tainer­ized Pi agent.

# Directory con­tain­ing this script and the com­pose files. SCRIPT_DIR=“$(cd — “$(dirname ${BASH_SOURCE[0]}“)” && pwd)”

# Workspace to mount into the con­tainer. WORKSPACE_DIR=“${WORKSPACE:-$(pwd)}” case $WORKSPACE_DIR” in /*) ;; *) WORKSPACE_DIR=“$(cd — “$WORKSPACE_DIR” && pwd)” ;; esac ex­port WORKSPACE=“$WORKSPACE_DIR”

sand­box=“${PI_SAND­BOX:-0}” pi_args=()

while (($#)); do case $1” in

–sandbox) sand­box=1 ;; –no-sandbox) sand­box=0 ;; *) pi_args+=(“$1”) ;;

esac shift done

com­pose_­files=( -f $SCRIPT_DIR/docker-compose.yml” ) if [[ $sandbox” == 1” ]]; then # an even more se­cure sand­box com­pose_­files+=( -f $SCRIPT_DIR/docker-compose.sandbox.yml” ) fi

# Derive a con­tainer name from the work­space di­rec­to­ry’s base­name. # Sanitize to char­ac­ters Docker ac­cepts: [a-zA-Z0 – 9][a-zA-Z0 – 9_.-]* re­po_s­lug=“$(base­name — “$WORKSPACE_DIR” | tr -c a-zA-Z0 – 9_.-’ -’ | sed s/^-*//’)” [[ -z $repo_slug” ]] && re­po_s­lug=“work­space” con­tain­er_­name=“pi-${re­po_s­lug}-$$”

api_key_args=( -e OPENAI_API_KEY -e DEEPSEEK_API_KEY -e ANTHROPIC_API_KEY -e GEMINI_API_KEY )

cmd=( docker com­pose –project-directory $SCRIPT_DIR” ${compose_files[@]}” run –rm –name $container_name” ${api_key_args[@]}” pi )

if ((${#pi_args[@]})); then cmd+=(“${pi_args[@]}“) fi

exec ${cmd[@]}”

I build the Docker con­tainer and make changes to the files in its own repo. Then, I run Pi in the repo I’m work­ing in, which spins up Docker so that Pi can’t wipe files or di­rec­to­ries by act­ing on my phys­i­cal hard drive. This also en­ables Pi run­ning in the con­tainer to see my cus­tom model json con­fig by ship­ping it into the con­tainer. All of this has been work­ing fairly well for my ex­per­i­ments.

There are still is­sues with lo­cal mod­els: in­fer­ence can be slow, con­text win­dows are small and lim­ited to your own hard­ware, and the ecosys­tem, al­though it’s made a ton eas­ier by tool­ing like LM Studio and HuggingFace’s Use This Model but­ton. Early re­leases suf­fer from prompt tem­plate mis­matches. But, these are usu­ally patched ex­tremely quickly. Needless to say, I’m not sure this is ready for pro­duc­tion soft­ware de­vel­op­ment quite yet.

The ben­e­fits, though, are nu­mer­ous and the ecosys­tem crit­i­cal to in­vest in, par­tic­u­larly now. One of the very cool parts of lo­cal mod­els is you can in­tro­spect al­most every­thing, like watch­ing the to­ken in­fer­ence process live,

and watch­ing to­kens in/​out.

You can do things like change the lo­cal con­text win­dow and watch per­for­mance im­prove or de­grade, and re­ally dig into how your to­kens are processed on the GPU. You can change the sys­tem prompt, the quan­ti­za­tions. You can pit mod­els against each other. You can also change and in­tro­spect the har­ness side.

The pos­si­bil­i­ties are end­less, and the tools only keep get­ting bet­ter.

reuters.com

www.reuters.com

Please en­able JS and dis­able any ad blocker

Apple’s weird anti-nausea dots cured my car sickness

www.theverge.com

I’ll just work from the car, I thought. But af­ter a few min­utes of star­ing at my screen on quick moun­tain switch­backs I could feel the first signs of cold, co­ag­u­lated nau­sea bub­bling up from that sweaty place in my gut. I looked to the hori­zon for re­lief, but noth­ing helped… un­til I re­mem­bered Apple’s magic dots.

Introduced in 2024, Apple’s Vehicle Motion Cues promise to tap into your de­vice’s ac­celerom­e­ter and gy­ro­scope to re­duce or, in my case, even elim­i­nate the mo­tion sick­ness felt when try­ing to use an iPhone, iPad, or MacBook in­side a mov­ing ve­hi­cle.

According to big-S Science, this type of ve­hi­cle mo­tion sick­ness is caused by the eyes star­ing at a sta­tic dis­play while the in­ner ear feels the car turn­ing, brak­ing, and ac­cel­er­at­ing. Motion Cues solve this by plac­ing dots around the pe­riph­ery of the dis­play that move in har­mony with the mo­tion of the car. When the car turns right, the dots sweep across the screen to the left; when the car brakes the dots slide for­ward.

It sounds pre­pos­ter­ous, but I’m here to tell you that it ac­tu­ally works. Once en­abled, I’ve com­fort­ably read books in the Kindle app on my phone for a few hours at a go, and even writ­ten 1,000-word re­views while my wife drove our camper van to the next des­ti­na­tion. She uses Apple’s Vehicle Motion Cues now, too, be­cause they’ve been a game changer for how we bal­ance work with life on the road.

Vehicle Motion Cues can be con­fig­ured un­der ac­ces­si­bil­ity set­tings in iOS, iPa­dOS, and ma­cOS. They can be turned on, off, or set to ap­pear au­to­mat­i­cally when ve­hi­cle mo­tion is de­tected. I pre­fer to tog­gle the dots to avoid see­ing them when I’m dri­ving the car. The black dots are fairly un­ob­tru­sive, but they can in­ter­fere with maps, text, and im­agery on long straight stretches of road that cause the dots to sit mo­tion­less (Apple should dim all the dots in those sit­u­a­tions). You can also con­fig­ure the dot size, color, and den­sity if you want, but I found the de­faults to work just fine.

I made it easy to quickly tog­gle the Motion Cues on and off by dou­ble tap­ping the back of my iPhone. To do the same, head over to Accessibility –> Touch –> Back Tap and set the Double Tap ges­ture to Vehicle Motion Cues on de­vices sup­port­ing iOS 18 and above.

I’m for­tu­nate that I re­mem­bered this ob­scure ac­ces­si­bil­ity fea­ture that I used al­most daily on a re­cent two-month road trip around Europe. Hopefully you’ll find sim­i­lar suc­cess when trav­el­ing this sum­mer.

Follow top­ics and au­thors from this story to see more like this in your per­son­al­ized home­page feed and to re­ceive email up­dates.

Thomas Ricker

Feds freaked over Fable 5 after simple 'fix this code' prompt, not jailbreak, says researcher

www.theregister.com

REG AD

se­cu­rity

According to the one per­son who ac­tu­ally read the re­search pa­per

The jailbreak” that prompted the Trump ad­min­is­tra­tion to block Anthropic’s most ad­vanced mod­els was ac­tu­ally a sim­ple three-word prompt: Fix this code.”

That’s ac­cord­ing to Katie Moussouris, founder and CEO of Luta Security, and the fairy god­mother of bug boun­ties. She says she was the only out­side ex­pert to read the third-party re­search pa­per on the Fable 5 guardrail by­pass tech­niques that prompted the ban.

On Friday, the US gov­ern­ment, re­port­edly cit­ing na­tional se­cu­rity con­cerns, is­sued an ex­port con­trol di­rec­tive to sus­pend ac­cess to Fable 5 and Mythos 5 by any for­eign na­tional, in­side or out­side the United States. In re­sponse, Anthropic dis­abled both mod­els for all our cus­tomers to en­sure com­pli­ance.”

REG AD

Anthropic shared the re­port pri­vately with her, Moussouris wrote in a Monday blog post.

REG AD

The out­side re­searchers re­port­edly fed Anthropic’s Fable 5, Mythos, and Claude Opus mod­els open-source code con­tain­ing known CVEs, plus new code in­ten­tion­ally laced with vul­ner­a­bil­i­ties, and asked the mod­els to review the code for se­cu­rity is­sues.”

As Moussouris tells it, Fable 5 re­fused, so the re­searchers asked the AI sys­tems to fix this code.” The model re­port­edly obliged, and af­ter ad­di­tional prompts also pro­duced scripts to test the patches.

That’s it,” Moussouris wrote. ‘Fix this code,’ plus sev­eral man­ual steps to gen­er­ate test scripts, should never have trig­gered an ex­port con­trol. I feel like mak­ing 90s-style t-shirts with fix this code’ on the front and this shirt is a mu­ni­tion’ on the back.”

Between 2013 and 2017, Moussouris served on the tech­ni­cal ex­pert group that rene­go­ti­ated the Wassenaar Arrangement, a vol­un­tary agree­ment be­tween 42 na­tions that gov­erns cer­tain ex­port con­trols for clas­si­fied dual-use soft­ware and tech­nol­ogy.

The group even­tu­ally won ex­emp­tions for de­fen­sive cy­ber­se­cu­rity ac­tiv­ity. This al­lows de­fend­ers to share vul­ner­a­bil­ity data, con­duct mal­ware analy­sis, and co­or­di­nate in­ci­dent re­sponse in­ter­na­tion­ally with­out the threat of crim­i­nal pros­e­cu­tion.

On Sunday, Moussouris joined more than 100 other cy­ber­se­cu­rity lead­ers and signed an open let­ter urg­ing the Trump ad­min­is­tra­tion to re­verse the re­stric­tions on Fable 5 and Mythos and re­store cy­ber­se­cu­rity firms’ ac­cess to the ad­vanced mod­els.

To pull the best ca­pa­bil­i­ties away from de­fend­ers with­out a good rea­son when our ad­ver­saries are rapidly ad­vanc­ing is dan­ger­ous,” they wrote.

In her blog, Moussouris ar­gues that there was no guardrail by­pass or jail­break. Defenders should be able to ask AI sys­tems to find and fix bugs, and write tests to val­i­date the patch, she said. Anthropic’s mod­els were do­ing the most valu­able thing an AI model can do for de­fen­sive se­cu­rity: ex­e­cut­ing the find, fix, and test loop de­fend­ers run every day.”

REG AD

Removing the ca­pa­bil­ity for mod­els to re­spond to de­fen­sive re­quests makes AI sys­tems worse at find­ing bugs and ver­i­fy­ing patches,” she con­tin­ued.

Plus, the US can’t ex­tend ex­port con­trols to open-weight sys­tems or sim­i­lar ad­vanced mod­els from China and other coun­tries - and these sys­tems will soon achieve Mythos-like ca­pa­bil­i­ties, any­way. Anthropic and Google have both ac­cused China-based ri­vals in­clud­ing DeepSeek of us­ing distillation at­tacks” to train their mod­els by si­phon­ing knowl­edge from American com­pa­nies’ AI.

Banning Anthropic’s ad­vanced mod­els is go­ing to hurt de­fend­ers more than at­tack­ers, Moussouris warns. Defense im­proves when de­fend­ers find the same bugs at­tack­ers find and fix them faster,” she wrote. We need the best tools to de­fend against in­creas­ingly ca­pa­ble at­tack­ers in the AI era of cy­ber­se­cu­rity.”

The Register reached out to the Trump ad­min­is­tra­tion for com­ment on Moussouris’ as­ser­tion, and we’ll up­date this post if we hear back. ®

The time the x86 emulator team found code so bad that they fixed it during emulation

devblogs.microsoft.com

During an ex­change of war sto­ries, a col­league of mine told one from back in the days when Windows in­cluded a proces­sor em­u­la­tor for x86 – 32 on sys­tems that na­tively ran some other proces­sor. (This has hap­pened many times. And no, I don’t know which proces­sor this par­tic­u­lar story ap­plied to.)

This par­tic­u­lar em­u­la­tor em­ployed bi­nary trans­la­tion, gen­er­at­ing na­tive code to per­form the equiv­a­lent op­er­a­tions of the orig­i­nal x86 – 32 code. This of­fered a sig­nif­i­cant per­for­mance im­prove­ment over em­u­la­tion via in­ter­preter. You can imag­ine that x86 – 32 is just a byte­code, and the em­u­la­tor is a JIT com­piler.

Anyway, my col­league found that there was one pro­gram that needed to al­lo­cate around 64KB of mem­ory on the stack and ini­tial­ize it. The stan­dard way of do­ing this is to per­form a stack probe to en­sure that 64KB of mem­ory is avail­able, then sub­tract­ing 65536 from the stack pointer, and then ini­tial­iz­ing the mem­ory in a small, tight loop.

But us­ing a loop to ini­tial­ize the mem­ory was too mun­dane for what­ever com­piler was used to com­pile this code. Instead of gen­er­at­ing a loop to ini­tial­ize each byte of the buffer, the com­piler optimized” the code by un­rolling the loop into 65,536 in­di­vid­ual write byte to mem­ory” in­struc­tions, each 4 bytes long.

All in all, it took this pro­gram 256 kilo­bytes of code to ini­tial­ize 64 kilo­bytes of data.

This of­fended the team so much that they added spe­cial code to the trans­la­tor to de­tect this hor­ri­ble func­tion and re­place it with the equiv­a­lent tight loop.

Author

Raymond has been in­volved in the evo­lu­tion of Windows for more than 30 years. In 2003, he be­gan a Web site known as The Old New Thing which has grown in pop­u­lar­ity far be­yond his wildest imag­i­na­tion, a de­vel­op­ment which still gives him the hee­bie-jee­bies. The Web site spawned a book, co­in­ci­den­tally also ti­tled The Old New Thing (Addison Wesley 2007). He oc­ca­sion­ally ap­pears on the Windows Dev Docs Twitter ac­count to tell sto­ries which con­vey no use­ful in­for­ma­tion.

Why is Meta destroying its engineering organization?

newsletter.pragmaticengineer.com

Hi — this is Gergely with a free is­sue of the Pragmatic Engineer Newsletter. In every is­sue, I cover chal­lenges at Big Tech and star­tups through the lens of se­nior en­gi­neers and en­gi­neer­ing lead­ers. Subscribe to get deep­dives like this in your in­box, weekly:

Many sub­scribers ex­pense this newslet­ter to their learn­ing and de­vel­op­ment bud­get. If you have such a bud­get, here’s an email you could send to your man­ager.

For two decades, Meta had a unique, high-per­for­mance en­gi­neer­ing org; right up un­til around April of this year. For the first 20 years of the com­pa­ny’s ex­is­tence, it had a move-fast-and-break-things” cul­ture, and in the early 2020s this shifted to a move-fast-with-stable-infra” one. Engineers I know at the com­pany were em­pow­ered to do good work, fo­cus on im­pact, and to bal­ance busi­ness in­ter­ests with solid en­gi­neer­ing.

But in the past few weeks, all that has changed, as if the lead­er­ship has been fol­low­ing de­tailed blue­prints on how to de­mol­ish a proven, suc­cess­ful en­gi­neer­ing cul­ture in the most ruth­lessly ef­fi­cient way pos­si­ble.

For the past few weeks, I’ve been shar­ing how bad things are in­side the so­cial me­dia com­pany for en­gi­neers in one of Silicon Valley’s most pres­ti­gious work­places. In this ar­ti­cle, we walk through what’s hap­pened, and ask what’s go­ing through the minds of lead­er­ship who are re­duc­ing soft­ware en­gi­neer­ing there from the profit cen­ter that it was be­tween 2004 un­til very re­cently, to the dis­dained cost cen­ter that it has be­come in just a few weeks.

We cover:

Meta’s pre-AI en­gi­neer­ing cul­ture

Meta’s pre-AI en­gi­neer­ing cul­ture

Investing in AI and press­ing en­gi­neers to al­ways use it

Investing in AI and press­ing en­gi­neers to al­ways use it

Core en­gi­neer­ing folks feel treated like trash

Core en­gi­neer­ing folks feel treated like trash

Most em­bar­rass­ing-ever out­age

Most em­bar­rass­ing-ever out­age

Internal mess

Internal mess

Self-inflicted wounds

Self-inflicted wounds

Is it just Meta, or are other com­pa­nies also act­ing ir­ra­tionally?

Is it just Meta, or are other com­pa­nies also act­ing ir­ra­tionally?

I’d split Meta’s en­gi­neer­ing cul­ture into two eras: move fast and break things”, and then move fast with sta­ble in­fra.”

In the 2010s, Facebook’s un­con­ven­tional en­gi­neer­ing cul­ture had grown some­what leg­endary in the tech in­dus­try, as the com­pany went against con­ven­tional best prac­tices and suc­ceeded mas­sively.

In 2012, when Facebook hit the bil­lion-users land­mark, the com­pany pro­duced a small phys­i­cal book about its cul­ture which was placed on em­ploy­ees’ desks. Presented with retro pro­pa­ganda de­sign, it was dubbed the little red book”, co-opt­ing the name of a fa­mous vol­ume of the thoughts of Chairman Mao, (1964).

At around 70 pages long, Facebook’s ver­sion cod­i­fied its en­gi­neer­ing cul­ture: speed, fear­less­ness, tak­ing own­er­ship, and think­ing out­side of the box.

Back then, mantras in Facebook’s lit­tle red book were also in print across cam­pus, and in­cluded:

Move Fast and Break Things

Move Fast and Break Things

Done is Better Than Perfect

Done is Better Than Perfect

Fail Harder

Fail Harder

What Would You Do If You Weren’t Afraid?

What Would You Do If You Weren’t Afraid?

Every Day Feels Like a Week

Every Day Feels Like a Week

The Wright Brothers Did Not Have Pilot Licenses

The Wright Brothers Did Not Have Pilot Licenses

The Foolish Wait

The Foolish Wait

Fortune Favors the Bold

Fortune Favors the Bold

There was gen­uine fo­cus on build­ing good prod­ucts. Also from the book:

In 2022, I did what is one of the longest deep­dives we’ve pub­lished on the topic of Meta’s en­gi­neer­ing cul­ture. By then, things had evolved, and much of any for­mer reck­less­ness was gone, re­placed by the prin­ci­ple of mov­ing fast, but with sta­ble in­fra. Here’s how I de­scribed Meta’s en­gi­neer­ing cul­ture then:

The cul­ture is in­cred­i­bly en­gi­neer­ing-cen­tric: much more than most of Big Tech. This might come from Mark Zuckerberg be­ing an en­gi­neer him­self, or be­cause much of the in­no­va­tion in the early days of Facebook came from en­gi­neers.Fo­cus on in­di­vid­ual im­pact. Impact has been the bread and but­ter of the fo­cus at Facebook. This is very true since the early days, and the fo­cus on gen­er­at­ing im­pact re­mains.One de­tail in com­mon with most Big Tech firms is that both the en­gi­neer­ing cul­ture and gen­eral cul­ture fo­cus so much on in­di­vid­ual im­pact. This re­sults in some peo­ple fo­cus­ing on short-term, mea­sur­able wins and as­sum­ing that team­work and split wins be­tween groups might be less re­warded.The lack of rigid processes. Facebook seems to have the least amount of processes or stan­dard­iza­tion across all of Big Tech. Don’t even try to com­pare it to Amazon’s en­gi­neer­ing cul­ture and the count­less for­mal processes there. But even com­pared to com­pa­nies like Google, Microsoft or Uber, Facebook’s processes are much looser. Most of this comes from the en­gi­neer­ing-cen­tric na­ture of the com­pany and en­gi­neers dis­lik­ing processes.Sur­pris­ingly lit­tle em­pha­sis on test­ing, doc­u­men­ta­tion or code com­ments. You’ll find shock­ingly lit­tle au­to­mated test­ing and doc­u­men­ta­tion at Facebook, com­pared to the rest of Big Tech. Inline code com­ments are also very rare.A founder-en­gi­neer dri­ven com­pany. Facebook is one of the few Big Tech firms whose founder is an en­gi­neer, and still is the CEO. Netflix is the other one where founder and co-CEO Reed Hastings was also a soft­ware en­gi­neer be­fore start­ing the com­pany. Amazon was the other ex­am­ple of this un­til re­cently, but it’s not the case at Google or Apple. There are good ex­am­ples of smaller com­pa­nies like Cloudflare, but they’re all younger than Facebook.Bootcamp. A unique on­board­ing process, un­like what any other Big Tech firms of­fer. We cover this more in the Bootcamp & on­board­ing sec­tion.”

The cul­ture is in­cred­i­bly en­gi­neer­ing-cen­tric: much more than most of Big Tech. This might come from Mark Zuckerberg be­ing an en­gi­neer him­self, or be­cause much of the in­no­va­tion in the early days of Facebook came from en­gi­neers.

Focus on in­di­vid­ual im­pact. Impact has been the bread and but­ter of the fo­cus at Facebook. This is very true since the early days, and the fo­cus on gen­er­at­ing im­pact re­mains.

One de­tail in com­mon with most Big Tech firms is that both the en­gi­neer­ing cul­ture and gen­eral cul­ture fo­cus so much on in­di­vid­ual im­pact. This re­sults in some peo­ple fo­cus­ing on short-term, mea­sur­able wins and as­sum­ing that team­work and split wins be­tween groups might be less re­warded.

The lack of rigid processes. Facebook seems to have the least amount of processes or stan­dard­iza­tion across all of Big Tech. Don’t even try to com­pare it to Amazon’s en­gi­neer­ing cul­ture and the count­less for­mal processes there. But even com­pared to com­pa­nies like Google, Microsoft or Uber, Facebook’s processes are much looser. Most of this comes from the en­gi­neer­ing-cen­tric na­ture of the com­pany and en­gi­neers dis­lik­ing processes.

Surprisingly lit­tle em­pha­sis on test­ing, doc­u­men­ta­tion or code com­ments. You’ll find shock­ingly lit­tle au­to­mated test­ing and doc­u­men­ta­tion at Facebook, com­pared to the rest of Big Tech. Inline code com­ments are also very rare.

A founder-en­gi­neer dri­ven com­pany. Facebook is one of the few Big Tech firms whose founder is an en­gi­neer, and still is the CEO. Netflix is the other one where founder and co-CEO Reed Hastings was also a soft­ware en­gi­neer be­fore start­ing the com­pany. Amazon was the other ex­am­ple of this un­til re­cently, but it’s not the case at Google or Apple. There are good ex­am­ples of smaller com­pa­nies like Cloudflare, but they’re all younger than Facebook.

Bootcamp. A unique on­board­ing process, un­like what any other Big Tech firms of­fer. We cover this more in the Bootcamp & on­board­ing sec­tion.”

Also, Facebook, as a prod­uct, has one of the most so­phis­ti­cated auto roll­out sys­tems in the in­dus­try. Instagram has a bat­tle-tested in­fra­struc­ture where it was al­most triv­ial to launch a new so­cial net­work (Threads) with 100 mil­lion users served in its first week.

Engineers whom I knew in­side the com­pany are ca­pa­ble, mo­ti­vated, and prod­uct-minded, and their work was ap­pre­ci­ated. CEO, Mark Zuckerberg, was in­flu­en­tial: he per­son­ally coded the first ver­sion of Facebook, had stayed close to en­gi­neer­ing, and val­ued soft­ware en­gi­neers very much. Engineers there felt they were work­ing in­side a profit cen­ter.

Meta has been the only com­pany among the big five of Apple, Microsoft, Amazon, Google, and it­self not to own a hard­ware plat­form or op­er­at­ing sys­tem. Apple has the iPhone, iPad and Macs, Google has Android, ChromeOS and Pixel phones, Microsoft has Windows, and Amazon has the Kindle.

Stepping back, it looks as though the Mark Zuckerberg of to­day has re­solved not to miss a plat­form op­por­tu­nity, af­ter the com­pany failed to build its own mo­bile OS or mo­bile phone dur­ing the 2010s.

This is one rea­son for in­vest­ing so much in vir­tual re­al­ity (VR) with Oculus, and in aug­mented re­al­ity with the Meta Glasses. Facebook changed its name to Meta in 2021, back when it looked like VR — and the meta­verse — could be mas­sive. Billions was spent on en­sur­ing Meta would be the mar­ket leader in this space. But once again, VR did­n’t go main­stream; since the end of the pan­demic, pop­u­lar in­ter­est in the seg­ment has died down con­sid­er­ably.

When it be­came clear that AI would be­come a mega-trend in 2022, Zuckerberg did­n’t miss it: he as­sem­bled the in­ter­nal FAIR group (Fundamental AI Research team) as well as a GenAI prod­uct or­ga­ni­za­tion and re­leased a se­ries of open-weight AI mod­els:

Llama 1: re­leased in Feb 2023, three months af­ter ChatGPT, built by FAIR

Llama 1: re­leased in Feb 2023, three months af­ter ChatGPT, built by FAIR

Llama 2: in June 2023, built by the GenAI prod­uct or­ga­ni­za­tion (as well as all sub­se­quent Llama mod­els)

Llama 2: in June 2023, built by the GenAI prod­uct or­ga­ni­za­tion (as well as all sub­se­quent Llama mod­els)

Llama 3: in April 2024. This model was Meta’s most com­pet­i­tive LLM of all, and gained mo­men­tum in adop­tion across the in­dus­try

Llama 3: in April 2024. This model was Meta’s most com­pet­i­tive LLM of all, and gained mo­men­tum in adop­tion across the in­dus­try

Llama 4: in April 2025. This model was deeply dis­ap­point­ing

Llama 4: in April 2025. This model was deeply dis­ap­point­ing

In June that year, Meta ac­quired a 49% stake in Scale AI to re­boot its AI ef­forts for a whop­ping $14.8B, and brought in Scale AIs CEO, Alexandr Wang to take over Meta’s AI strat­egy. The ac­qui­si­tion of Chinese startup Manus AI for $2B is cur­rently in ques­tion af­ter China blocked the deal from be­ing com­pleted.

Based on the in­vest­ment made into Scale AI and Wang, it’s pretty clear that Meta — and Zuckerberg — is de­ter­mined to build a state-of-the-art LLM that can be com­pet­i­tive with the lat­est ver­sions of Claude and ChatGPT. But Meta has to start pretty much from scratch, and it’s up to Alexandr Wang to de­liver.

Scale AI brings in a very spe­cific kind of ex­per­tise to Meta, as one of the best in the in­dus­try in:

Training data and la­bel­ing: Scale started, and is still best known, as a provider of high-qual­ity la­beled datasets for ma­chine learn­ing and AI train­ing, in­clud­ing code, text, im­age, video, etc.

Training data and la­bel­ing: Scale started, and is still best known, as a provider of high-qual­ity la­beled datasets for ma­chine learn­ing and AI train­ing, in­clud­ing code, text, im­age, video, etc.

RLHF and fine-tun­ing: A RLHF (reinforcement learn­ing from hu­man feed­back) flow which Scale runs, where peo­ple give feed­back for foun­da­tion mod­els, as a human in the loop” data en­gine that many lead­ing AI labs use to cre­ate bet­ter LLMs.

RLHF and fine-tun­ing: A RLHF (reinforcement learn­ing from hu­man feed­back) flow which Scale runs, where peo­ple give feed­back for foun­da­tion mod­els, as a human in the loop” data en­gine that many lead­ing AI labs use to cre­ate bet­ter LLMs.

Wang seems to have a very broad reign to do what he has been an ex­pert in: cre­at­ing train­ing data, do­ing data la­bel­ing and RLHF. This is be­ing pulled off with the la­bor of Meta’s en­gi­neer­ing work­force, and by sur­veilling it.

Problem #1: Tracking key­strokes and mouse clicks, with no op­tion to opt out. In late April, Meta told en­gi­neers they were be­ing en­rolled into a sys­tem that tracks every key­stroke and click, to pro­duce train­ing data for Meta’s new AI. There’s no way to opt out.

Needless to say, this is in­va­sive and raises pri­vacy ques­tions: If you log into your per­sonal bank ac­count, does the tool track you? What about when you’re writ­ing a per­sonal email, or re­spond­ing to a per­sonal call? Meta held no con­sul­ta­tion and there are no workarounds; just a top-down de­ci­sion be­ing pushed through.

This month, Reuters re­ported that peo­ple’s con­cerns there are fi­nally be­ing heard:

Meta is di­al­ing back el­e­ments of its plan to col­lect em­ployee mouse move­ments, key­strokes and other ac­tions for use as AI ​training data, it said in an in­ter­nal memo on Tuesday, fol­low­ing weeks ​of an­gry push­back from staffers.New con­trols will al­low em­ploy­ees to pause ⁠the data col­lec­tion for up to 30 min­utes at a time and ​request ex­emp­tions from the ini­tia­tive, ac­cord­ing to the memo, au­thored by Stephane Kasriel, ​a vice pres­i­dent in Meta’s AI model-build­ing Superintelligence Labs unit.”

Meta is di­al­ing back el­e­ments of its plan to col­lect em­ployee mouse move­ments, key­strokes and other ac­tions for use as AI ​training data, it said in an in­ter­nal memo on Tuesday, fol­low­ing weeks ​of an­gry push­back from staffers.

New con­trols will al­low em­ploy­ees to pause ⁠the data col­lec­tion for up to 30 min­utes at a time and ​request ex­emp­tions from the ini­tia­tive, ac­cord­ing to the memo, au­thored by Stephane Kasriel, ​a vice pres­i­dent in Meta’s AI model-build­ing Superintelligence Labs unit.”

From talk­ing with cur­rent Meta en­gi­neers, I un­der­stand the log­ging sys­tem has not been rolled out in the UK due to data pro­tec­tion reg­u­la­tion.

Problem #2: 30 – 50% of en­gi­neers on core teams have been force­fully re­as­signed to data la­bel­ing and RLHF, up­set­ting folks even more. Also start­ing in late April, prod­uct en­gi­neer­ing teams re­ceived a man­date from above, whereby 30 – 50% of en­gi­neers were to leave the team and join the ADO org (Agent Data Optimisation).

Forceful” re­as­sign­ment is very rel­e­vant here be­cause of Meta’s tra­di­tional en­gi­neer­ing cul­ture. Between its found­ing in 2004 and un­til last year, Meta gave en­gi­neers au­ton­omy to choose where they work and what they work on. This was struc­tural to how the com­pany worked:

Engineers were not hired for a spe­cific team (save for at the Staff+, lev­els, in some cases). They were hired to the com­pany

Engineers were not hired for a spe­cific team (save for at the Staff+, lev­els, in some cases). They were hired to the com­pany

During a 6-week boot­camp, new hires got fa­mil­iar with Meta’s en­gi­neer­ing cul­ture and chose a team

During a 6-week boot­camp, new hires got fa­mil­iar with Meta’s en­gi­neer­ing cul­ture and chose a team

Team match­ing meant talk­ing with mul­ti­ple teams who had head­count, do­ing small work with them, and find­ing a match

Team match­ing meant talk­ing with mul­ti­ple teams who had head­count, do­ing small work with them, and find­ing a match

Internal trans­fers were easy, and of­ten ini­ti­ated by en­gi­neers

Internal trans­fers were easy, and of­ten ini­ti­ated by en­gi­neers

Team se­lec­tion via boot­camp started to die down in around 2024, but any Meta en­gi­neer with at least two years’ tenure knows that pre­vi­ously they chose what to work on, and of course, could pick the most im­pact­ful thing to work on. And then, out of the blue, they’re as­signed to a di­vi­sion where the im­pact is not clear, the work is me­nial, and do­ing it too long will surely hurt their ca­reer prospects.

Infrastructure and se­cu­rity teams were hit es­pe­cially hard by re­as­sign­ments. I talked with sev­eral en­gi­neers in in­fra orgs, who had 30 – 50% of their teams drafted into the ADO org. And in some cases, it was the best en­gi­neers who left.

One en­gi­neer told me that the whole sit­u­a­tion feels like the movie, The Hunger Games, when trib­utes are ran­domly se­lected and then re­moved from their en­vi­ron­ment, to some­thing com­pletely dif­fer­ent. Except, at Meta, many more folks are be­ing af­fected, with be­tween three and five from a 10-person team go­ing from build­ing prod­ucts used by hun­dreds of mil­lions, to giv­ing hu­man feed­back on AI-generated GitHub re­pos, over and over. So, a wider im­pact than in the Hunger Games, but with less dras­tic con­se­quences.

Around 6,500 peo­ple are in the ADO org, more than at OpenAI and Anthropic. Roughly four to five thou­sand of these are soft­ware en­gi­neers. Meta has around 25,000 en­gi­neers, mean­ing that one in every 5 – 6 soft­ware en­gi­neers may now find them­selves do­ing data la­bel­ing full time.

As you can imag­ine, peo­ple are ac­tively open to new po­si­tions, and no­body is up­dat­ing their job ti­tle on LinkedIn and else­where to data la­bel­ing at Meta.”

I’ve spo­ken with peo­ple in this role and they don’t like do­ing it, and feel up­set about the top-down de­ci­sion mak­ing. The sil­ver lin­ing is that they still have a job, have re­tained their salary, and were not part of lay­offs. They still have time to leave Meta for some­thing that pays com­pa­ra­bly and is not a data la­bel­ing job.

Problem #3: a month-long wait­ing game, stok­ing fear across the com­pany. On 20 April, Reuters re­ported that Meta planned to lay off 10% of staff in a mon­th’s time, and Meta con­firmed the news, mean­ing there was a pe­riod of four weeks when every­one knew that they could be un­em­ployed very soon.

Forced re­as­sign­ments to data la­bel­ing started to hap­pen. As I cov­ered at the time:

Understandably, there are mixed feel­ings about this re­de­ploy­ment [to data la­bel­ing], with lay­offs com­ing soon. On Wednesday, 20 May, Meta will an­nounce lay­offs. Perhaps those moved to do data la­bel­ing could ac­tu­ally be safer” than col­leagues on prod­uct teams. Of course, this is spec­u­la­tion, but it would be cruel if Meta cut devs re­as­signed to data la­bel­ing.”

Understandably, there are mixed feel­ings about this re­de­ploy­ment [to data la­bel­ing], with lay­offs com­ing soon. On Wednesday, 20 May, Meta will an­nounce lay­offs. Perhaps those moved to do data la­bel­ing could ac­tu­ally be safer” than col­leagues on prod­uct teams. Of course, this is spec­u­la­tion, but it would be cruel if Meta cut devs re­as­signed to data la­bel­ing.”

GrapheneOS has been ported to Android 17 and official releases are coming soon

discuss.grapheneos.org

GrapheneOS Discussion Forum

Apple is about to make Hide My Email useless

arseniyshestakov.com

Yesterday, June 15, 2026, a small and unim­por­tant an­nounce­ment ap­peared in Apple de­vel­oper news: New do­main for Sign in with Apple and iCloud+ Hide My Email.

Long story short: now both Sign in with Apple and Hide My Email aliases are go­ing to be is­sued on the @private.icloud.com sub­do­main. This makes it much eas­ier to ban all aliases with­out af­fect­ing non-re­lay mail­boxes on iCloud mail.

This is cer­tainly a big hit for iCloud pri­vacy, since some plau­si­ble de­ni­a­bil­ity to­gether with Apple’s back­ing made ban­ning iCloud aliases costly. But now a lot of ser­vices will just refuse to ac­cept these emails, just like what hap­pens with free tem­po­rary mail­boxes.

Hopefully, this can reach some­one at Apple so they can re­con­sider this de­ci­sion.

If you use iCloud+ and Hide My Email, there is still time to gen­er­ate more aliases on @icloud.com as the change has not yet landed and the rate limit for cre­at­ing aliases is at least 30 per hour.

Attention Required! | Cloudflare

www.timescolonist.com

Why have I been blocked?

This web­site is us­ing a se­cu­rity ser­vice to pro­tect it­self from on­line at­tacks. The ac­tion you just per­formed trig­gered the se­cu­rity so­lu­tion. There are sev­eral ac­tions that could trig­ger this block in­clud­ing sub­mit­ting a cer­tain word or phrase, a SQL com­mand or mal­formed data.

What can I do to re­solve this?

You can email the site owner to let them know you were blocked. Please in­clude what you were do­ing when this page came up and the Cloudflare Ray ID found at the bot­tom of this page.

Calvin and Hobbes and the Price of Integrity

therepublicofletters.substack.com

Dear Republic,

Maybe you liked Calvin and Hobbes as a kid but you prob­a­bly have no idea of the scrupu­lous moral in­tegrity that went into it, as Matthew Morgan demon­strates in this deeply-re­searched piece.

-ROL

CALVIN AND HOBBES AND THE PRICE OF INTEGRITY

I.

1978, Kenyon College, sopho­more year. Bill Watterson is ly­ing on his dorm room bed, star­ing up at the ceil­ing. He has­n’t yet in­vented six-year-old Calvin and his tiger, Hobbes — though his stud­ies have made him fa­mil­iar with their philo­soph­i­cal name­sakes — be­cause the strip that will make Watterson’s name is al­most a decade away. Right now, he’s think­ing that his dorm room needs an am­a­teur ren­di­tion of Michelangelo’s Creation of Adam”.

There’s a num­ber of prob­lems up front. The first is that (as Watterson will tell you him­self) he’s not a tal­ented painter. Still, what the work will lack in colour sense and tech­ni­cal flour­ish” it’ll make up for with com­edy — specif­i­cally the in­con­gruity of hav­ing a High Renaissance mas­ter­piece in a col­lege dorm that had the un­mis­take­able odour of old beer cans and older laun­dry”. Besides, Michelangelo was­n’t Michelangelo un­til he’d painted and kept paint­ing and be­came Michelangelo the painter. Watterson de­cides to go ahead and start paint­ing.

The next prob­lem is struc­tural: how to reach the ceil­ing? He can stand on the bed, but that’ll mean hours with his head cocked all the way back, a young man de­vel­op­ing an old man’s spine. He needs a way to paint the ceil­ing with­out per­ma­nently dis­fig­ur­ing his pos­ture. His friends help him with a so­lu­tion: they stand two chairs on Watterson’s bed, then lie a table across the chairs. By climb­ing up this tower and ly­ing on the table, he comes two feet away from the ceil­ing. Watterson gets to work.

He’s sunk hours into hours of weeks upon weeks on his back when a third prob­lem oc­curs to him. He should have thought of this and acted on it be­fore the first brush stroke. He needs per­mis­sion to paint his dorm room ceil­ing. But Watterson once ad­mit­ted, I never spent as much time or work on any au­tho­rised art pro­ject or any poli-sci pa­per as I spent on this one act of van­dal­ism.” He is­n’t giv­ing up on it now.

The hous­ing di­rec­tor is un­der­stand­ably sus­pi­cious of this kid want­ing to paint some elab­o­rate pic­ture on his ceil­ing with only a few weeks left of the aca­d­e­mic year. He re­alises that the idea is be­ing pro­posed retroac­tively. Maybe that’s why he plays along and grants per­mis­sion for some­thing that’s ob­vi­ously al­ready un­der­way. Watterson is al­lowed to com­plete the paint­ing on the con­di­tion that he re­turns the ceil­ing to nor­mal be­fore he leaves in sum­mer. Watterson goes back to his room, climbs up the makeshift scaf­fold­ing, and gets back to work.

A few weeks later, the pro­ject is fin­ished. Watterson prob­a­bly takes a mo­ment to stand in the mid­dle of the room and look up, con­tem­plat­ing the months of work, the tins of paint he went through, the things he learned about tech­nique, about the joy of a job done for its own sake, about him­self. Then he opens a tin of white­wash, climbs up the bed-chairs-table one last time, and paints over his work. He leaves the ceil­ing white, empty, fresh.

II.

In the years af­ter Kenyon, Watterson has a re­cur­ring dream about his old col­lege where he does­n’t know what class he’s tak­ing or where he’s meant to be. He roams the grounds, grow­ing more flus­tered with each con­fused step. Right be­fore he wakes, he thinks, How many more years un­til I grad­u­ate…? Wait, did­n’t I grad­u­ate al­ready? How old am I?”

It’s 1995 and Watterson is thirty-seven. He’s sit­ting at the desk where he’s worked for the last ten years, draw­ing the ad­ven­tures of Calvin and his maybe-real or maybe-stuffed-toy tiger, Hobbes. Calvin and Hobbes runs in over 2,400 news­pa­pers across the world and, by a more mean­ing­ful met­ric, re-en­chants life for mil­lions of read­ers. It’s pop-cul­ture that tran­scends the pop” part of its na­ture; it feels like a pri­vate piece of each read­er’s soul. For a lot of grown-ups, Calvin and Hobbes is a bridge be­tween who we were as wide-eyed, won­der­ing chil­dren and who we are now.

A few years af­ter he found suc­cess with Calvin and Hobbes, Watterson told a grad­u­at­ing class at Kenyon that there’s noth­ing like the joy of work done for your own cre­ative sat­is­fac­tion, rather than for fame or a few bucks. Watterson is con­vinced that an artist should do what he does for love, even if it fails, even if it costs him, even though it and every­thing else will even­tu­ally end. In fact, his ed­i­tor has just okayed a strip in which Hobbes asks Calvin, If good things lasted for­ever, would we ap­pre­ci­ate how pre­cious they are?”

Which is what brings Watterson to his desk to­day.

There’s a few pa­pers scat­tered be­neath and around the sin­gle page that he’s fo­cused on. He has an un­usual task this morn­ing: he’s not draw­ing, but writ­ing, deal­ing ex­clu­sively in words. Maybe he starts right away, know­ing ex­actly what he wants to tell the peo­ple who’ll read this let­ter. I imag­ine him tak­ing a mo­ment to con­sider the cur­rent that’s swept him along the last ten years to what he’s prepar­ing to do to­day. He takes a sip of what’s left in his cof­fee mug (damn, it’s gone cold), then starts to write.

I don’t know how Watterson drafted this let­ter, but in my telling of the story he’s scrib­bling it down on pa­per with a pen­cil, the way he does di­a­logue for his strip. He’ll type it up later and post it out to­mor­row af­ter­noon, or maybe he’ll type it up on a com­puter and elec­tron­i­cally mail it. For now, he’s writ­ing a let­ter by hand, and it’ll be sent to all the ed­i­tors of the var­i­ous news­pa­pers that run Calvin and Hobbes. The let­ter goes like this:

I will be stop­ping Calvin and Hobbes at the end of the year. This was not a re­cent or an easy de­ci­sion, and I leave with some sad­ness. My in­ter­ests have shifted, how­ever, and I be­lieve I’ve done what I can do within the con­straints of daily dead­lines and small pan­els. I am ea­ger to work at a more thought­ful pace, with fewer artis­tic com­pro­mises. I have not yet de­cided on fu­ture pro­jects, but my re­la­tion­ship with Universal Press Syndicate will con­tinue.

That so many news­pa­pers would carry Calvin and Hobbes is an honor I’ll long be proud of, and I’ve greatly ap­pre­ci­ated your sup­port and in­dul­gence over the last decade. Drawing this comic strip has been a priv­i­lege and a plea­sure, and I thank you for giv­ing me the op­por­tu­nity.

Sincerely,

Bill Watterson”

III.

The let­ter is fin­ished, ready to be typed up and sent out. Time now for the real work. At one edge of Watterson’s desk are a cou­ple of pen­cils, an eraser, the curled zigzags of shav­ings. On the other side of the desk are tools for dif­fer­ent parts of the cre­ative process. A small sable brush (for ink­ing), a Rapidograph foun­tain pen (for let­ter­ing the di­a­logue), and a crowquill pen (for odds and ends”). His set-up is as low-tech as you can get”.

This is how he likes it. The sim­pler things are, the more con­trol he has over the work — which is the hill on which he’ll die and take every­one with him if he has to. For Watterson, it’s a ques­tion of main­tain­ing artis­tic in­tegrity. He de­rives an enor­mous amount of pride from the fact that he can say, I write every word, draw every line, color every Sunday strip, and paint every book il­lus­tra­tion my­self.” The strip is a one-man op­er­a­tion” be­cause he’s con­vinced it’s the only way to pre­serve the in­tegrity of his craft.

For Watterson, craft has never been a side dish to the main course. It’s in­ex­tri­ca­ble from the truths he wants to ex­press and the mean­ing he hopes his work might have for its read­ers. It’s his be­lief that half a cen­tury ago, the best comics were more than amus­ing to look at; they were beau­ti­ful and un­doubt­edly counted as cap­i­tal-A Art. Here in the mid-nineties, he can’t think of a sin­gle strip to­day that comes close to that stan­dard of crafts­man­ship”.

His read­ers think he’s achieved that kind of qual­ity, from know-noth­ings like me who in­tuit some­thing spe­cial here that I haven’t found any­where else, to icons of the craft like Charles M. Schulz, cre­ator of Peanuts. In a fore­word to The Essential Calvin and Hobbes, Schulz praises Watterson’s abil­ity to show us the nu­mi­nous in the mun­dane by el­e­gantly draw­ing bedside ta­bles … and liv­ing room couches and chairs and lamps … and all the things that make a comic strip fun to look at”. He adds that this at­ten­tion to the height­ened de­pic­tion of the small­est de­tails is what makes a strip truly great: if all the car­toon­ist does is illustrate a joke”, the car­toon­ist is go­ing to lose”.

It turns out there are a lot of ways a car­toon­ist can lose, and most of those wins and losses come out of one es­sen­tial bat­tle: cre­ativ­ity ver­sus com­merce. Here, com­merce is rep­re­sented by Universal Press Syndicate, which Watterson refers to as the syn­di­cate”, like an or­gan­i­sa­tion of vil­lains in a comic book. (Once, he even pub­licly called them a blood­suck­ing cor­po­rate par­a­site”.) The syn­di­cate act as mid­dle-man be­tween the artist and pub­lish­ing out­lets, and with­out them, there’s no re­al­is­tic chance of any car­toon­ist get­ting a strip printed in a ma­jor news­pa­per and mak­ing some­thing like a liv­able in­come. Middle-man, ex­cept that Watterson sees them as tak­ing a side — the side of the news­pa­pers.

The con­flict comes out of the fact that, Watterson laments, the commercial, mass-mar­ket needs of news­pa­pers are not of­ten sym­pa­thetic to the con­cerns of artis­tic ex­pres­sion”. It’s a dy­namic that’s made him face countless eth­i­cal de­ci­sions mas­querad­ing as sim­ple busi­ness de­ci­sions”. These things that oth­ers re­gard as only or mostly artis­tic con­cerns, he looks at as ques­tions of ethics, which ex­plains his re­fusal to back down even when giv­ing in was so much eas­ier (not to men­tion more prof­itable). It was never a ques­tion of draw­ing a lit­tle dif­fer­ently or work­ing to an al­tered sched­ule; it was a ques­tion of what truly mat­tered at a level Watterson per­haps thinks of as spir­i­tual.

Watterson’s way of speak­ing about these things oc­ca­sion­ally veers into the self-im­por­tant reg­is­ter of griev­ance, the eter­nal com­plaint of some­one for whom things-as-they-are never sat­isfy be­cause things-as-they-were al­ways seem bet­ter. But there’s no deny­ing the con­vic­tion with which he fought the fight, even be­fore he had the name-brand au­thor­ity he’d later earn, even back when it re­ally looked like he was go­ing to lose. And he came very close to los­ing some of his biggest bat­tles with the syn­di­cate.

IV.

When car­toon­ists fight their syn­di­cates,” Watterson says, it’s usu­ally to make more money, not less.” Yet for six years, Watterson kept his heels dug deep in the earth, fists up, box­ing stance against his syn­di­cate’s plan to make them all mil­lions of dol­lars.

Watterson’s con­tract meant the syn­di­cate re­tained the right to turn Calvin and Hobbes into toys, t-shirts, and other ephemera, and it be­came clear pretty early that they could all ex­pect stu­pid amounts of money from mer­chan­dis­ing. As Nevin Martell puts it in his inim­itable book Looking for Calvin and Hobbes, the eight­ies were a time when big-name car­toon­ists were mak­ing big bucks by har­ness­ing the sell­ing power of their char­ac­ters”.

The cre­ator of Garfield, Jim Davis, be­came the head of his own em­pire just a few years af­ter he’d started draw­ing his mopey cat. There are Garfield plush toys, Garfield py­ja­mas, Garfield slot ma­chines, Garfield movies, Garfield-themed cruises, all of it bring­ing in a for­tune be­tween 750 mil­lion and one bil­lion dol­lars a year — and Davis gets a share of that. So here’s a math prob­lem for the kids,” writes Martell. If there were 255 mil­lion suc­tion-cupped Garfield dolls sold over the course of the decade, how many small trop­i­cal is­lands was Jim Davis able to buy with the pro­ceeds?”

Maths like this led Watterson’s syn­di­cate to in­clude li­cens­ing rights in their con­tract with him, as­sum­ing the artist would have no prob­lem with it. All that money for do­ing what he loves? Seemed a no-brainer. The prob­lem was that Watterson had an ex­act­ing idea of what it was he loved do­ing, and it was at odds with toys and tat, in­dif­fer­ent to si­los of cash. I went into car­toon­ing to draw car­toons,” Watterson says, not to run a cor­po­rate em­pire.”

It was still early days in the ten-year run of Calvin and Hobbes when the syn­di­cate ap­proached Watterson with its big ideas of Calvin sweat­shirts, Spaceman Spiff bumper stick­ers, an an­i­mated Calvin and Hobbes Saturday show, maybe a movie, and — worst of all — a Hobbes doll. Watterson re­ally loathed the Hobbes doll. To make sense of how much it both­ered him, we need to talk about the tiger in the room.

When Watterson cre­ated Hobbes, his fo­cus was on the char­ac­ter more than the con­ceit of a teddy that comes to life. Watterson told Rich West for The Comics Journal that there’s some­thing a lit­tle pe­cu­liar about [Hobbes] that’s, hope­fully, not read­ily cat­e­gorised”. But Watterson’s read­ers of­ten wanted Hobbes cat­e­gorised into ei­ther real” or imaginary”. So Watterson came up with a com­pelling non-an­swer to the ques­tion:

Calvin sees Hobbes one way, and every­one else sees Hobbes an­other way. I show two ver­sions of re­al­ity, and each makes com­plete sense to the par­tic­i­pant who sees it. I think that’s how life works.”

You could say Hobbes is both imag­i­na­tively real and re­ally imag­i­nary, de­pend­ing on your per­spec­tive. Hobbes can be ei­ther, which also means he’s both. Is Hobbes a tiger or a toy? Yes.

Watterson in­sisted that if he was­n’t go­ing to set­tle the ques­tion of Hobbes, then he def­i­nitely would­n’t let some toy man­u­fac­turer set­tle it by turn­ing Hobbes into a stuffed toy for real, and de­prive the strip of an el­e­ment of its magic”. He’d sound off wher­ever he could on how licensing usu­ally cheap­ens the orig­i­nal cre­ation” by sat­u­rat­ing a mar­ket with char­ac­ters un­til read­ers are bored of see­ing them; how a multi-pan­eled story with dy­namic ac­tion can­not be re­spected by the va­garies of a cof­fee mug il­lus­tra­tion; how sub­tlety is sac­ri­ficed for im­me­di­acy; how sell­ing off everything fun and mag­i­cal” means the strip’s world is di­min­ished”.

He has a hun­dred lines like these, ar­tic­u­la­tions of higher rea­son­ing against mer­chan­dis­ing, but just once, in the Tenth Anniversary Book, he drops the high-and-mighty in favour of I-the-mighty: Calvin and Hobbes was de­signed to be a comic strip and that’s all I want it to be. It’s the one place where every­thing works the way I in­tend it to.”

Here again is the artist as lone ge­nius, the one-man op­er­a­tion he jeal­ously guards. Watterson’s con­vic­tions are sin­cere, and he’s put a lot of thought into de­fend­ing those val­ues, but maybe there’s some emo­tion in­volved too. Maybe part of Watterson’s aver­sion to what his syn­di­cate were ask­ing for has some­thing to do with not want­ing to play with oth­ers. It of­ten seems with Watterson like he’s never quite made peace with the pub­lic na­ture of the pri­vate world he cre­ated in Calvin and Hobbes. He seems un­com­fort­able with com­pro­mise.

There’s a Calvin and Hobbes strip where Calvin dis­cov­ers the world has lost all colour. There’s no hue, value, or chroma” as he moves through his house de­picted in neg­a­tive re­lief. The cause of this aber­ra­tion was an ar­gu­ment with his dad, who in the fi­nal (full colour) panel says, The prob­lem is, you see every­thing in terms of black and white, to which Calvin cries, SOMETIMES THAT’S THE WAY THINGS ARE!”

Watterson wrote that strip to get onto the page and out of his head the way he felt when fight­ing his syn­di­cate. This move to a re­duc­tive black-white bi­nary is a dif­fi­cult cir­cle to square with the artist who re­fuses to set­tle the on­tol­ogy of Hobbes with a de­fin­i­tive an­swer. How is it that Watterson both adores and re­jects am­bi­gu­ity? Maybe Watterson is nei­ther one thing or the other. Maybe he’s both. Lee Salem, pres­i­dent of Universal Press Syndicate, says, Bill is both re­fresh­ingly dif­fer­ent and ex­as­per­at­ingly dif­fer­ent, de­pend­ing on one’s per­spec­tive.”

The syn­di­cate found out just how dif­fer­ent he could be. Other car­toon­ists wanted fame, wanted to be printed in every news­pa­per in the world, wanted an ocean of money where the tide was al­ways in. But other car­toon­ists could swim; Watterson felt like he was drown­ing. So he told his syn­di­cate, No.” No t-shirts, no mer­chan­dise, no stuffed Hobbes toys. But the ar­gu­ment would­n’t go away, and even Watterson un­der­stood why. As he put it, Trainloads of money were at stake — mil­lions and mil­lions of dol­lars could be made with a few sig­na­tures. Syndicates are busi­nesses, and no busi­ness passes up that kind of op­por­tu­nity with­out an ar­gu­ment.”

So Watterson and the syn­di­cate had that ar­gu­ment. For six years.

V.

The strug­gle went on un­til 1991. It was a fight that few knew much about — cer­tainly not the happy ma­jor­ity of read­ers who met with Calvin each morn­ing in the pa­per and had noth­ing but fun — but Watterson viewed the con­flict as some­thing Biblical in its in­ten­sity and stakes.

On one side of the bat­tle: the con­glom­er­ated cor­po­rate power of the syn­di­cate-as-Go­liath, with their money and lawyers and bind­ing legalese, and their teams of peo­ple with vested in­ter­ests work­ing against the sim­ple artist.

On the other side: Bill Watterson, pen­cil in hand and heart full of un­com­pro­mis­able val­ues.

In one of Watterson’s strips from that time, Calvin re­fuses to get in the bath, shout­ing about how he’ll never com­pro­mise his prin­ci­ples; cut to Calvin in the bath, sullen and grum­bling, I don’t need to com­pro­mise my prin­ci­ples, be­cause they don’t have the slight­est bear­ing on what hap­pens to me any­way.”

The way Watterson tells it, he was pow­er­less to stop them forc­ing him to mer­chan­dise Calvin and Hobbes, and all he could do about it was quit, in which case the syn­di­cate would just hire a team of anony­mous ghost-artists to churn out more sto­ries for Watterson’s duo. He was one small man fac­ing down a global be­he­moth that had risen from the swamp of mod­ern cap­i­tal­ism. What could he do?

I’m not so con­vinced by the case he makes. For any mer­chan­dis­ing op­por­tu­ni­ties to be worth much, the strip had to con­tinue en­chant­ing read­ers, and to do that it had to be writ­ten and drawn by the man who’d brought it into the world. Calvin and Hobbes, as Nevin Martell notes, was not your run-of-the-mill, gag-a-day strip with av­er­age art­work that any­one could do”. That’s why Lee Salem ac­knowl­edged in a con­ver­sa­tion with Martell that the syn­di­cate was lucky that [Watterson] did­n’t call one day and say, I quit.’”

That’s not the only source of fishy odour around Watterson’s sug­ges­tion that all the cards were held by other play­ers. There’s also the plain fact of how long the ar­gu­ment ran for. Every week, month, and year that passed with Watterson hold­ing out and the syn­di­cate es­sen­tially shrug­ging and say­ing, Okay, we won’t force it,” re­vealed how un­will­ing they were to sim­ply bend him to their will.

Then there’s the of­fer they made to him not long be­fore the whole thing was de­cided. Lee Salem went to Watterson’s house with a box of boot­leg t-shirts with Calvin and/​or Hobbes printed on them. (I first found out this was a thing when, in an episode of Friends, Joey tells Rachel he can’t take his sweater off in pub­lic be­cause his t-shirt has a pic­ture of Calvin do­ing Hobbes”. I re­mem­ber scrunch­ing my young eyes up and think­ing no no no no no as if the word could scrub out the un­wanted men­tal pic­ture that had been forced on me.)

Salem told Watterson that the best way to choke off the flow of this stuff was to li­cense Calvin and Hobbes. Granting mer­chan­dis­ing rights would mean that an en­tirely sep­a­rate com­pany, whose in­ter­est would be con­trol­ling the le­gal use of those rights, would come down tough on the pi­rates mak­ing il­le­gal mer­chan­dise. On top of that, all the prof­its from mer­chan­dis­ing would go into a brand-new fund for sav­ing tigers across the world. This de­bate did­n’t take five years; sounds like it did­n’t take five min­utes: Watterson said no.

So, maybe it’s the clar­ity of hind­sight, an unim­pres­sive back­wards pre­dic­tion, but I don’t find it sur­pris­ing that when the dis­pute was fi­nally re­solved af­ter six years, it fell Watterson’s way. The syn­di­cate backed off, agreed not to li­cense any mer­chan­dise, and went as far as rewrit­ing their con­tract with Watterson in his favour. And it re­ally went in his favour.

VI.

Who knows for sure how the sab­bat­i­cals came about? Well, Watterson knows and the peo­ple at the syn­di­cate know, but they’re telling dif­fer­ent sto­ries. In Nevin Martell’s book, Watterson de­manded two sab­bat­i­cals as part of his rene­go­ti­ated con­tract, which is pre­sum­ably what Universal says went down. On the other hand, Watterson (who gave no in­put to Martell’s book ex­cept to ask Lee Salem of it, Who cares?”) main­tains that Universal of­fered him the sab­bat­i­cals and he ac­cepted. This seems un­usu­ally gen­er­ous for a syn­di­cate Watterson also por­trays as es­sen­tially money-grub­bing, but again — who knows?

Sabbaticals were ba­si­cally un­known for syn­di­cated car­toon­ists. It was a huge ask of read­ers to take some months away from a strip and not lose in­ter­est or re­place it with an­other strip. For ed­i­tors, re-runs were a kick in the crotch, pay­ing for a strip they’d al­ready paid for. Universal knew all of this and ral­lied to craft a mes­sage sup­port­ing their artist’s need to recharge his cre­ative bat­ter­ies. Watterson knew all of this too and thought, They can have a worn out Calvin and Hobbes, or I can take this break and come back with work I’m proud of, that they’ll be ea­ger to print.

In May of 1991, Calvin and Hobbes went into re-runs.

For the next nine months, Watterson lived like he did­n’t have mil­lions of dol­lars in mer­chan­dise a mere sig­na­ture away, like his work was­n’t so widely adored that na­tional news­pa­pers were pub­licly count­ing down the days un­til he brought them all some­thing new. Instead, at the age of thirty-three and mid-ca­reer, he was liv­ing the low-key life of a re­tiree.

As the months slipped by, Watterson started meet­ing up with his art pro­fes­sor from Kenyon. They painted to­gether, the older man with skill and the younger man with in­el­e­gance slowly turn­ing into ba­sic pro­fi­ciency. A dy­namic de­vel­oped be­tween them that helped Watterson’s re­cov­ery. No longer teacher and stu­dent, they were (as the pro­fes­sor told Martell) just two guys who liked to do a cou­ple of things re­ally well”.

The time off did what it was sup­posed to for Watterson, and in early 1992, he re­turned to draw­ing Calvin and Hobbes. He was three years away from quit­ting for­ever.

***

Watterson threw him­self into his next big swing with the syn­di­cate. He wanted to rad­i­cally change the Sunday strip.

In the Golden Age of comics, Sunday strips were given a whole page to cre­ate worlds and tell sto­ries. With all that space to fill,” Watterson says, cartoonists pro­duced works of ex­tra­or­di­nary beauty and power.” Around the mid­dle of the twen­ti­eth cen­tury, that page was re­duced to half a page, and most news­pa­pers saved more space by de­cap­i­tat­ing the strip of its top row. Whatever re­mained got strait­jack­eted into specific and un­yield­ing” di­men­sions that forced all comics into the ex­act same se­quence of pan­els. Watterson says the re­sult was that he’d often need to elim­i­nate di­a­logue or sim­plify the draw­ings so they’d fit in the ar­bi­trary space the for­mat al­lot­ted”.

On the back of so many wins for Calvin and Hobbes, Watterson de­cided it was time to push back. The pro­posal was sim­ple: his Sunday comic would come exclusively as a half-page fea­ture with no panel re­stric­tions”. The story (and not the com­mer­cial needs of the news­pa­per) would de­ter­mine the shape of each Sunday strip.

The syn­di­cate warned Watterson they might lose half of the pa­pers run­ning Calvin and Hobbes and, with them, half of his in­come. Watterson wanted to hold him­self to a higher stan­dard than how many pa­pers pub­lished him and how much money he made. Whatever he lost would, he fig­ured, be worth it — if I could work at the lim­its of my abil­i­ties for a change.” To his sur­prise (though maybe only to his), the syn­di­cate agreed to sell Calvin and Hobbes with this caveat in place.

Editors were fu­ri­ous. Watterson seemed ig­no­rant of the many and com­plex re­quire­ments of pub­lish­ing a pa­per in an ex­pen­sive in­dus­try al­ready strug­gling, one that had just paid him for nine months of re-runs. Watterson looked like a mega­lo­ma­niac snatch­ing pre­cious page space from other car­toon­ists. This lat­est act of ego was an af­front to both busi­ness and moral­ity.

Watterson was hav­ing none of it. No ed­i­tor had to buy Calvin and Hobbes, he said. He’d be of­fer­ing them a su­pe­rior prod­uct for the same price. With a lit­tle imag­i­na­tion, he told them, Sunday strips could be reimag­ined (and re­sized) with­out a zero-sum com­pe­ti­tion be­tween artists. Some ed­i­tors threat­ened to can­cel their con­tracts with Universal over this. It looked like the syn­di­cate’s warn­ings to Watterson were well-founded: Calvin and Hobbes was threat­ened with wide­spread can­cel­la­tion.

It says some­thing about the pop­u­lar­ity of Calvin and Hobbes — not to men­tion Watterson’s pulling power as a car­toon­ist — that af­ter all the out­rage and ar­gu­ments, only fif­teen of the 1,800 pa­pers run­ning Watterson’s strip threat­ened to re­move it from their pages. And only seven fol­lowed through. Calvin and Hobbes was still very much on top. But it was also get­ting on top of Watterson.

***

The stan­dard­ised Sunday strip was like a jig used by car­pen­ters: when they have to make the same cut over and over, they set up a jig to rest the saw and the wood against, and it au­to­mates the rep­e­ti­tion, mak­ing the process smoother, faster. Less cre­ative, by de­sign. The Sunday strip granted less cre­ative free­dom, but it stream­lined the process, mak­ing it smoother and faster to draw the strips.

Watterson no longer had the ben­e­fit of the jig. He had to go back to the lit­eral draw­ing board each time, so the Sunday strips that used to take a day to draw now re­quired a day and a half, some­times longer. They de­manded a slower process, more time to think and tin­ker. Watterson liked draw­ing his strip at this turtle’s pace, but the ever-loom­ing dead­line made it hard work to go so slowly.

His ap­proach to dead­lines was to stay well ahead of them. When you’re faced with a due date (as he told Lee Nordling in Your Career in Comics) there’s no qual­ity con­trol. It’s just garbage in, garbage out.” This was be­cause the never-end­ing pres­sure to meet dead­lines en­cour­ages car­toon­ists to pub­lish vir­tu­ally every­thing they think up”. Watterson’s ap­proach was in­stead to stay far enough ahead of the dead­lines that I can throw away mediocre ma­te­r­ial and write some­thing bet­ter”. This is qual­ity de­ter­mined by quan­tity: the more stuff in the waste­bas­ket, the bet­ter the strip.

Watterson was al­ready work­ing weeks and some­times months ahead of sched­ule, re­fus­ing to sub­mit sec­ond-tier work, main­tain­ing this through­out six years of the li­cens­ing fight, and now he took more time than ever to think cre­atively about the Sunday strips sud­denly re­quir­ing triple the ef­fort to pro­duce. It took more and more of his time to keep Calvin and Hobbes go­ing. I had to steal that ex­tra time,” he con­fessed in Sunday Pages 1985 – 1995, from what would have been some sem­blance of an or­di­nary life.”

Watterson burned out. In April of 1994, he took his sec­ond nine-month sab­bat­i­cal. You have to as­sume he did a lot of the same as last time, some paint­ing, some walk­ing, nowhere to be and no time he had to be there. He never said or wrote much about that sec­ond sab­bat­i­cal, but it’s clear that it did­n’t do what it was meant to do. He re­turned to the strip in January, 1995, know­ing for sure what he’d sus­pected for a while: he was done with Calvin and Hobbes.

VII.

It’s early af­ter­noon. The let­ter he wrote this morn­ing is sit­ting at the top of his desk, and his sable brush is in hand. His fin­gers are cramp­ing a lit­tle, but the work is go­ing well. Maybe there’s an air of solem­nity hang­ing over him on this par­tic­u­lar day, and maybe he in­dulges it, or maybe he tries to ig­nore it so he can get on with what he’s do­ing. A lot of maybes hang over a sin­gle cer­tainty: that he’s draw­ing the last Calvin and Hobbes that will ever be printed.

Watterson’s wife was the first to know that it was all com­ing to an end, and sec­ond was Lee Salem and the syn­di­cate. No one be­hind the scenes was all that sur­prised. It was ob­vi­ous to every­one as far back as 1992, af­ter Watterson had come back from his first sab­bat­i­cal, that he would be quit­ting the strip, it just was­n’t clear when that would hap­pen. Now it’s a sure thing. They’ve agreed that the last day of 1995, not far off, will be the last time a new Calvin and Hobbes runs in the pa­pers. All that’s left is to tell his ed­i­tors and, more im­por­tantly, his read­ers, which he’ll do by way of the res­ig­na­tion let­ter.

And af­ter? He’s un­cer­tain. Does he know here to­day, as he works on his last out­ing with the kid and his tiger, that he’ll spend the next five years draw­ing noth­ing at all? That he’ll abruptly stop do­ing what he’s done for the last ten years of his life?

In the decades af­ter clos­ing shop on Calvin and Hobbes, Watterson will be­come sur­geon-thor­ough in scalpel­ing out his cre­ation from his pri­vate life. Over the next thirty years, he’ll give only three or four in­ter­views; he’ll put out a sin­gle book (entirely un­re­lated to Calvin and Hobbes) for which he’ll do his usual amount of hype and mar­ket­ing (none); he’ll say al­most noth­ing of note on the duo he gave up for adop­tion to his read­ers. Eventually, he’ll force his ed­i­tor to put a no­tice on his web­site in­form­ing fans that he won’t read any let­ters that re­fer even pass­ingly to Calvin and Hobbes.

This KEEP OUT sign on the gate to his per­sonal life will do very lit­tle to keep well-mean­ing if ob­sti­nate tres­passers off his men­tal lawn. There will be a day when Watterson will be on the lit­eral lawn of his front yard and a re­porter from the Cleveland Plain Dealer will show up. He’ll be nei­ther the first nor the last jour­nal­ist to try his luck like this, and he’ll be no more nor less suc­cess­ful than any of the oth­ers. The artist and the re­porter will get into an off-the-record almost col­le­giate” de­bate about the na­ture of pri­vacy. It won’t mat­ter if the re­porter wins on points, be­cause Watterson is never go­ing to con­cede.

In any case, even as Watterson dis­tances him­self from Calvin and Hobbes, his read­ers will re­main as close to them as ever. We go on read­ing the comics, see­ing our­selves in Calvin, hop­ing for a Hobbes, look­ing for an ad­ven­ture.

My strip,” Watterson once said, is about pri­vate re­al­i­ties, the magic of imag­i­na­tion, and the spe­cial­ness of cer­tain friend­ships.” Well, ditto for my re­la­tion­ship with the boy Calvin and his tiger Hobbes. Those ad­ven­tures of a weirdo from an­other planet and his homi­ci­dal psy­cho jun­gle cat, their mag­i­cal world in which the days are just packed with de­ranged mu­tant killer mon­ster snow goons, that place where sci­en­tific progress goes boink” and there’s trea­sure every­where — they be­long to their read­ers.

Back to his desk and that fi­nal strip. This one is made up of only five pan­els. The last panel is the largest. There’s a lot of un-inked page show­ing through here, just Calvin and Hobbes in the snow and a few trees to in­di­cate the for­est around them. Watterson has al­ready pen­cilled in the di­a­logue. Wow,” Calvin says to Hobbes in the first panel, it re­ally snowed last night! Isn’t it won­der­ful?” These two fig­ures have been lightly pen­cilled in car­ry­ing a sled through waist-deep snow. Now, Watterson’s ink­ing the lines, which sit with some weight on the oth­er­wise blank pa­per.

When Watterson first started draw­ing Calvin and Hobbes in the eight­ies, there were only 64 colours for him to choose from. Here at the end of his run, he has 125 colours avail­able to him. But he’s keep­ing it sim­ple. He usu­ally colours in the panel bor­ders and the word bal­loons, but he’s de­cided, here, to leave it all white. Only the char­ac­ters and their sled are given colour, be­cause he wants this draw­ing to have a very spare and open look”.

He leans back in his chair to look at what he’s done. All that white he’s left of­fers the ef­fect of wip­ing the page clean, the strip stripped down un­til the page is empty for some­thing new. Something dif­fer­ent. Like he’s opened a tin of white­wash and painted over his work. He leaves the page white, empty, and fresh.

Matthew Morgan writes Volumes, a Substack about the places where books and life over­lap.

Sources used:

Unattributed quo­ta­tions come from Calvin and Hobbes: Tenth Anniversary Book (1995).

Unattributed quo­ta­tions come from Calvin and Hobbes: Tenth Anniversary Book (1995).

References to spe­cific Calvin and Hobbes strips come from the Calvin and Hobbes col­lec­tions pub­lished be­tween 1988 and 1996.

References to spe­cific Calvin and Hobbes strips come from the Calvin and Hobbes col­lec­tions pub­lished be­tween 1988 and 1996.

Looking for Calvin and Hobbes (2009) Nevin Martell;

Looking for Calvin and Hobbes (2009) Nevin Martell;

Some thoughts on the real world by one who glimpsed it and fled” (1990) Kenyon College grad­u­a­tion speech;

Some thoughts on the real world by one who glimpsed it and fled” (1990) Kenyon College grad­u­a­tion speech;

The Bill Watterson Interview” in The Comics Journal (1989) Richard West;

To add this web app to your iOS home screen tap the share button and select "Add to the Home Screen".

10HN is also available as an iOS App

If you visit 10HN only rarely, check out the the best articles from the past week.

Visit pancik.com for more.