Nolan's Odyssey
20 November, 2026Finally got to watch Nolan’s Odyssey after much delay. Kind of funny, because the last two years have been full of Odyssey otherwise.
- Read Benjamin The Odyssey through Gillian Cross’s children’s book.
- Finished Dan Simmons’s Ilium and Olympos, which shove the characters of the Iliad and Odyssey straight into sci-fi.
- That led directly to Tennyson’s Ulysses, which is quite good. “It little profits that an idle king…”
- More amusingly, The Rest Is History podcast covered it in two fun parts. Clearly Odysseus’s crew were all Australians.
Changes I liked
- Fewer gods. Totally sensible for realism.
- Circe. More grotesque than seductive. A fun reinterpretation.
- Lotus-Eaters and Calypso combined. Good compression. The movie was already three hours long.
- Streamlined cast. Cutting the Phaeacians, Nestor, and Laertes saves time without losing much.
- Never seeing Agamemnon’s face. Nice touch.
Changes I didn’t like
- No “Nobody” trick with the Cyclops. Classic Odysseus: cleverness undermined by pride.
- No Aeolus or bag of winds. A fun adventure lost. Maybe a missed opportunity for some comedy.
- No dead Achilles. Especially disappointing given Nolan’s emphasis on the costs of war. Achilles’s ghost explicitly rejects the glory of dying in battle.
- Telemachus diminished. Less capable and independent than in Homer.
- No Penelope banter or olive-tree bed trick. We lose the wonderful sense that Penelope is Odysseus’s intellectual equal.
- Sailing west. After ten years desperately trying to get home, Odysseus immediately leaves again? My wife: “Why would he get on another boat?!”
Ambivalent
- Odysseus’s PTSD. Making the Trojan War something he regrets didn’t really stick with me, but maybe that says more about me than Homer. The whole “we are the Sea Peoples” angle seemed a bit much.
Commentscomputer prices
17 November, 2026Intel
Type Item Price CPU Intel Core i5-14400 2.5 GHz 10-Core Processor $179.99 @ Amazon Motherboard Asus B760M-AYW WIFI D4 II Micro ATX LGA1700 Motherboard $89.99 @ Newegg Memory Patriot Viper Steel 16 GB (1 x 16 GB) DDR4-3200 CL16 Memory $114.99 @ Amazon Storage Samsung 980 500 GB M.2-2280 PCIe 3.0 X4 NVME Solid State Drive $79.99 @ Samsung Case Antec NX200M MicroATX Mid Tower Case $42.99 @ Amazon Power Supply Thermaltake Smart 600 W 80+ Certified ATX Power Supply $46.99 @ B&H Prices include shipping, taxes, rebates, and discounts Total $554.94 Generated by PCPartPicker 2026-11-17 11:49 EST-0500 Amd
CommentsType Item Price CPU AMD Ryzen 7 5700G 3.8 GHz 8-Core Processor $206.00 @ Amazon Motherboard ASRock A520M Pro4 Micro ATX AM4 Motherboard $69.98 @ Amazon Memory Patriot Viper Steel 16 GB (1 x 16 GB) DDR4-3200 CL16 Memory $114.99 @ Amazon Storage Samsung 980 500 GB M.2-2280 PCIe 3.0 X4 NVME Solid State Drive $79.99 @ Samsung Case Fractal Design Core 1100 MicroATX Mini Tower Case $49.99 @ B&H Power Supply Thermaltake Smart 600 W 80+ Certified ATX Power Supply $46.99 @ B&H Prices include shipping, taxes, rebates, and discounts Total $567.94 Generated by PCPartPicker 2026-11-17 11:51 EST-0500 DB/SQL history since college
3 November, 2026This is the endpoint of a late nitght discussion with chatgpt about the evolution of sql since I was in the industry with fun links at the end. Not my own writing.
Twenty Years of Database Wars: How SQL Survived NoSQL
From Oracle and MySQL to Bigtable, MongoDB, and PostgreSQL’s unexpected dominance.
In 2005, the database world seemed relatively settled. Relational databases dominated, SQL was the universal language, and choosing a database largely meant choosing between expensive commercial products and increasingly capable open-source alternatives.
Twenty years later, we’ve witnessed an explosion of new database architectures, the rise of NoSQL, globally distributed transactions, and the emergence of cloud-native storage. Yet the biggest winner might be a database that was already nearly a decade old in 2005: PostgreSQL.
How did we get here?
2000–2005: Open Source Challenges the Database Giants
For decades, enterprise databases were dominated by Oracle, IBM DB2, and Microsoft SQL Server. These were sophisticated systems, but commercial licensing could be extraordinarily expensive.
The internet changed the economics. MySQL, first released in 1995, became a foundation of the LAMP stack (Linux, Apache, MySQL, PHP). It was free, relatively simple to administer, and fast enough for the websites being built by an emerging generation of developers.
PostgreSQL, released under that name in 1996, offered a more ambitious alternative, emphasizing SQL standards, advanced data types, transactions, and extensibility. SQLite, released in 2000, demonstrated that an entire transactional SQL engine could be embedded in an application without a database server.
By 2005, open-source relational databases had become credible alternatives to commercial products. SQL’s dominance seemed secure.
But trouble was brewing at Google and Amazon.
2005–2010: Google and Amazon Reinvent Storage
As Google scaled its services across thousands of servers, traditional relational databases presented difficulties. Scaling writes generally meant buying bigger machines or manually partitioning data across independent database servers.
Google’s 2006 Bigtable paper described a different architecture: an enormous, sparse, sorted map distributed across machines, automatically dividing data into manageable ranges called tablets.
Bigtable abandoned relational queries and general-purpose transactions in favor of scalability and predictable performance.
Amazon’s 2007 Dynamo paper approached the problem differently. Its distributed key-value system prioritized availability, allowing operations to continue through server failures and network partitions, with conflicts resolved when necessary.
These papers inspired an entire generation of databases. Apache HBase followed Bigtable’s model. Cassandra combined Bigtable-like data structures with Dynamo-inspired distribution. Riak explored highly available key-value storage.
The underlying challenge wasn’t that SQL was fundamentally wrong. It was that the prevailing implementations of relational databases weren’t designed to distribute writes automatically across hundreds of machines.
Nevertheless, the emerging movement became known as NoSQL.
2009–2015: The NoSQL Gold Rush
MongoDB, introduced in 2009, brought NoSQL to ordinary application developers.
Instead of managing relational tables, developers stored JSON-like documents. Schemas could evolve without traditional migrations, and application objects mapped naturally to database records.
MongoDB’s appeal was as much about developer productivity as scalability. During this period, JSON APIs, JavaScript frameworks, and rapidly changing web applications made document databases particularly attractive.
Other systems flourished. Redis made in-memory key-value storage ubiquitous. CouchDB offered document replication. Cassandra promised distributed write scalability. Amazon launched DynamoDB in 2012 as a managed NoSQL service, while Microsoft’s Azure DocumentDB, later Cosmos DB, expanded the cloud database market.
For a while, it seemed relational databases might become legacy technology.
But NoSQL came with tradeoffs.
Applications frequently needed relationships between records, transactions spanning multiple objects, and queries that hadn’t been anticipated when the data model was designed. Without joins or sufficiently expressive transactions, developers often reimplemented database functionality in application code.
And the promised simplicity of schema-free development could become difficult to maintain as applications matured.
Meanwhile, relational databases weren’t standing still.
2012–2020: SQL Strikes Back
Two developments helped change the direction of database technology.
The first was Google’s Spanner, described in a landmark 2012 paper. Spanner demonstrated that globally distributed databases could provide strong transactional guarantees rather than requiring applications to accept eventual consistency.
This helped inspire a new generation of distributed SQL systems, including CockroachDB, TiDB, and YugabyteDB.
These systems borrowed heavily from NoSQL architectures—automatic partitioning, distributed replication, and consensus protocols—but retained SQL and transactions.
The second, perhaps more consequential development for everyday developers, happened inside PostgreSQL.
In 2014, PostgreSQL 9.4 introduced JSONB, allowing efficient, indexable storage of JSON documents alongside traditional relational data.
Suddenly, developers didn’t necessarily have to choose between a document database and a relational database. PostgreSQL could provide both.
PostgreSQL also benefited from an unusually extensible architecture. PostGIS made it a powerful geospatial database. TimescaleDB expanded its usefulness for time-series workloads. Citus introduced distributed sharding capabilities.
Rather than being displaced by specialized databases, PostgreSQL increasingly absorbed their functionality.
2020–2026: PostgreSQL Becomes the Default
By the 2020s, PostgreSQL had become the preferred general-purpose database for an enormous range of new applications.
In the 2026 Stack Overflow Developer Survey, 57.9% of respondents reported working with PostgreSQL, versus 35.1% for MySQL and 19.0% for MongoDB. These are developer usage figures, not measures of database installations or revenue, but they illustrate the change in sentiment.
Several factors explain PostgreSQL’s success.
First, it is genuinely capable. Its query optimizer, transactional guarantees, indexing options, and extensibility make it a strong default for most applications.
Second, its ecosystem has become enormous. Nearly every cloud provider offers managed PostgreSQL, virtually every development framework supports it, and companies can change hosting providers without necessarily changing databases.
Third, PostgreSQL continues to assimilate competing technologies. The emergence of pgvector brought vector similarity search into ordinary SQL applications, allowing developers to experiment with AI workloads without adopting another database.
But PostgreSQL’s popularity conceals some architectural weaknesses.
It still generally depends on a single writable primary. Read replicas can distribute queries, but distributing writes requires sharding, extensions, or independently managed database instances. Its MVCC implementation also creates dead tuples that must be cleaned up through VACUUM.
For individual applications, modern hardware is powerful enough that these limitations may never matter. For platforms hosting hundreds of applications, shared write bottlenecks and resource contention are less attractive.
The rise of PostgreSQL-compatible distributed databases suggests that developers increasingly value PostgreSQL’s interface and ecosystem independently of its underlying storage architecture.
The Next Chapter: Distributed SQL, Analytics, and Separation of Storage
While PostgreSQL was winning developer mindshare, several other important developments were unfolding.
Distributed SQL systems such as CockroachDB, YugabyteDB, TiDB, and Google’s Spanner attempt to preserve SQL and strong transactions while distributing data and write ownership across machines. Their architectures are attractive, although distributed coordination brings latency, operational complexity, and cost.
Analytical databases have followed a different path. Snowflake, BigQuery, ClickHouse, and DuckDB demonstrate the advantages of column-oriented storage and specialized execution engines. DuckDB is particularly interesting because it brings high-performance analytical SQL to a single embedded process, much as SQLite did for transactions.
Storage and compute are separating. Cloud-native architectures increasingly place durable data in shared or object-based storage while allowing compute resources to scale independently. Systems such as Neon and Amazon Aurora illustrate different approaches to decoupling database compute from storage.
Open-source licensing is becoming a battleground. Companies including MongoDB, Elastic, Redis, and Cockroach Labs have moved important products away from conventional permissive open-source licensing. PostgreSQL’s permissive license and independent development community have consequently become competitive advantages of their own.
And there’s a surprising continuity underneath all these changes: many modern databases, including distributed and analytical systems, still expose SQL.
Did SQL Win?
The last twenty years of database development weren’t simply a story of SQL defeating NoSQL.
NoSQL solved real problems. Bigtable and Dynamo fundamentally changed how distributed storage systems are designed. Cassandra, MongoDB, DynamoDB, and Cosmos DB continue to serve workloads for which their architectures make sense.
But NoSQL also revealed just how valuable relational queries and transactions were. Developers discovered that eliminating database complexity frequently meant moving that complexity into applications.
PostgreSQL’s resurgence illustrates another lesson: a mature, extensible platform can outlast specialized competitors by incorporating their best features.
The next generation of databases may distribute writes automatically, separate compute from storage, or use entirely different storage engines. But many will still speak SQL—and an increasing number will speak PostgreSQL’s dialect of it.
Perhaps the real winner of the database wars wasn’t PostgreSQL itself, but the relational abstraction it helped preserve.
Further reading
- Michael Stonebraker and Andy Pavlo, What Goes Around Comes Around… And Around…, 2024.
- Fay Chang et al., Bigtable: A Distributed Storage System for Structured Data, 2006.
- Giuseppe DeCandia et al., Dynamo: Amazon’s Highly Available Key-value Store, 2007.
- James C. Corbett et al., Spanner: Google’s Globally-Distributed Database, 2012.
- Andy Pavlo and Bohan Zhang, The Part of PostgreSQL We Hate the Most, 2023.
- Stack Overflow Developer Survey 2026 — Databases.
OLDER
- 22 Oct Nuc based k8s cluster
- 15 Oct Smith Brothers Locality
- 02 Oct Bootalicious
- 01 Oct Fresh Home Hop Cascade Pale Ale
- 18 Sep Bandera 2026
- 08 Sep Whole Cow
- 04 Sep Humpback mountain
- 04 Sep I-90 Summits: Bellevue to Snoqualmie Pass
- 04 Sep Tallapus and Ollalie
- 27 Aug Gem Lake 2026
- 22 Aug hyprbuntu
- 20 Aug Lake Crescent 2026
- 07 Aug 2026 Granite
- 23 Jul rainer paradise 2026
- 13 Jul Putrid Pete
- 07 Jul Wine Pairing for the People
- 06 Jul West Tiger 1 July
- 25 Jun Prosser
- 21 Jun Mt. Catherine
- 13 Jun Snow Lake 2026
- 11 Jun McClellan Butte 2026
- 27 May Cross Roads Food court
- 22 May Granite Creek
- 18 May Salt Fat Acid Heat Highlights
- 16 May Kitchen supplies
- 12 May Thoughts on the New Coding
- 10 May Mt Washington 2026
- 03 May Mailbox 2026
- 30 Apr Mt Si 2026
- 19 Apr brew gear shakedown
- 12 Mar Berkshire post Buffet
- 11 Mar Grocery Stores in major metros
- 21 Feb Whistler 2026
- 20 Feb Linux desktop
- 06 Feb First Week: No MSFT
- 24 Jan careme beta testing
- 23 Oct slog is neat
- 21 Oct 2026 hikes
- 10 Oct Test doubles in golang
- 05 Oct Last hike
- 24 Aug summer whistler
- 18 Aug wireguard kubernetes
- 15 Aug kids are alright
- 09 Aug Chanterelle and Corn Chowder with Basil
- 08 Aug herbfarm
- 02 Aug Cocoa-Cajun Flank Steak Marinade
- 26 Jul enchantments
- 12 Jul dirty harry's balcony
- 05 Jul mailbox
- 10 Jun bandera fathers day 2025
- 29 May beer
- 28 May memorial day
- 13 Apr baseball
- 11 Apr maui
- 02 Mar Ski 2025 (Alpental and Summit East)
- 01 Mar Habenero Red Cabbage Coleslaw
- 15 Feb Palm springs
- 17 Jan Chats vs Channels
- 25 Dec Cancun
- 20 Dec Release Bets
- 25 Nov Vashon
- 16 Nov Kubecon SLC 2024
- 28 Oct Last Hike of 2024
- 01 Sep Labor Day
- 19 Aug Mt. St. Helens
- 04 Aug Bandera/Seafair
- 21 Jul Counter Programming
- 16 Jul Bets and Debts
- 01 Jul Chelan/Leavenworth
- 15 Jun Trout lake
- 03 May Derby Fun 2024
- 21 Apr Houston
- 15 Apr Evictions KEP
- 30 Mar Last Day of Skiing
- 02 Mar Cosmos db and sql
- 25 Feb Whistler
- 02 Feb utils packages
- 29 Dec Christmas Cruise
- 17 Dec december tiger
- 17 Dec gpts
- 07 Oct mt granite 2
- 14 Sep Art institue of chicago
- 13 Sep Snow Lake
- 29 Aug lake cresent
- 20 Aug granite mountain
- 16 Aug prosser/red mountain
- 15 Aug lake cresent plan
- 06 Aug rimrock
- 15 Jul mt washington
- 06 Jul Chelan and 4th of July
- 17 Jun rainy fathers day
- 07 Jun memeorial day hiking
- 24 May IPA Stack Rank
- 15 May Eritrea Partry
- 07 May west tiger 2 shit show
- 03 May 2023 derby
- 23 Apr Sage Hot Italian Sausge Pasta
- 23 Apr single dad weekend with the boys
- 23 Apr Tri tip marinade.
- 16 Apr Yakima spring break
- 16 Mar Concert formulas
- 14 Mar General Electric
- 14 Mar No Direction Home
- 23 Feb irrational beliefs
- 15 Feb Oahu West side february
- 21 Jan Bad User Flows
- 20 Jan miss universe costumes
- 09 Dec chatgpt designs kured.
- 19 Nov wierd dream
- 22 Oct Kulturekampf
- 08 Aug Benji Pack list
- 17 Jun Microsoft Teams ui is broken
- 11 Jan New PC build
- 05 Jan Pan Sauce
- 28 Oct Rodgers covid
- 28 Oct Vaccine Maximalism
- 26 Oct Project shed
- 15 Aug Summer stout
- 09 Jul Windows Arm
- 06 Jul Balloon Buns
- 20 May Corporate Training
- 27 Mar Betty Crocker Chocolate Chip Cookies
- 07 Feb Distributed Twitter.
- 01 Feb Backwards ESB Kit
- 10 Jan Wrestling stories.
- 08 Jan Bourbon
- 12 Dec Ranger accesories
- 01 Oct Sad Country Drinking songs
- 01 Oct Straight to Jubel
- 05 Sep Conversations with Benji
- 29 Jul Xml is a Joke
- 04 Jul Garage brewery improvments
- 30 Jun Reiben Betrunken Lowe II
- 23 Jun Citrabomination
- 26 May Beer pickles
- 26 May Carne Asada Street Tacos
- 25 May Life Lost
- 16 May Won't do what you tell me IPA
- 03 May Cheesy Shrimp and Grits
- 03 May This time is different
- 29 Mar Corona Testing in a distributed republic.
- 09 Mar Morbid Corona Bet
- 26 Feb Fullers ESBish
- 17 Feb GigaPilsner
- 17 Feb Lego Collection
- 14 Feb Reset Pull Request signoff
- 31 Jan Bitcoin Selfdriving Bet
- 14 Jan Golang thoughts
- 05 Jan Why Skiing
- 23 Dec Bolognese
- 05 Dec Oatmeal Stout
- 03 Nov To Test Drive.
- 24 Aug Cheif Curmudgeon
- 24 Aug Dusseldorf Alt
- 30 Jun A CI/CD we can believe in
- 25 Jun Productivity
- 13 Jun Classic Pine
- 11 Apr Horse Power per Dollar
- 30 Mar Darkly Mild
- 30 Mar West Wheat
- 17 Mar China Future
- 04 Mar Chicken Noodle Soup
- 04 Mar Injera (Tibsi)
- 04 Mar Street Corn
- 01 Mar 747 rail gun
- 14 Feb A man for all seasons
- 13 Feb Ramayana and women
- 08 Feb Wintana Wine
- 26 Jan Flying Kolsch
- 10 Jan Netlify and blog thoughts
- 01 Jan Lip reading
- 27 Dec Pivo Clone (christmas justice)
- 17 Dec Brewing water
- 07 Dec Rasberry Brew
- 29 Nov Ur Marzen
- 23 Nov Things we should tax.
- 18 Nov Brewie Repair
- 18 Nov Panaoramas
- 20 Oct Liberty Belles
- 15 Sep The Wreck Porter
- 11 Aug California Dunkel
- 04 Jul No Hard Feelings ESB
- 10 Jun Franks wheat
- 02 Jun Brewie Review
- 28 May Choosing Life
- 27 May Pence and Mens Lizard brains.
- 22 May Lesser Known Romans
- 26 Apr Cowboy Morality
- 22 Apr Diogenes. Original Troll
- 21 Apr Finish the wonderland
- 12 Apr Real Blockchain
- 11 Apr I-90 Summits
- 10 Apr PCT Pack list
- 09 Apr Zelda
- 08 Apr sci-fi stack rank
- 07 Apr Why a blog?
- 01 Apr Catholic Libertarianism
- 11 Feb My Father
- 01 Jan American Dunkelweizen
- 01 Jan Bust me bagpipes scotch.
- 01 Jan Exiled Scot
- 01 Jan Harry Henderson's Oak Aged Stout
- 01 Jan Hoptarded
- 01 Jan Ignoble India pale ale
- 01 Jan Low Brau
- 01 Jan Low Brau 2.
- 01 Jan Old Crotchety
- 01 Jan Old Hooker
- 01 Jan Original Sin Stout
- 01 Jan Riesen betrunken reden Lion
- 01 Jan Riesen betrunken reden Lion (2011-10-05 version)
- 01 Jan Samoan Pale Ale.
- 01 Jan Straight Jubel
- 01 Jan Straight Jubel (2011-11-23 version)
- 01 Jan Unfiltered Liberty
- 01 Jan Willy's IPA
- 01 Jan Wintana's Winter Wonder beer.
- 05 Sep Honeymoon
- 25 Dec Why we goto church
- 01 Jan About
- 01 Jan album
- 01 Jan Derby Fun
- 01 Jan Derby Fun 2
- 01 Jan Derby Fun 2022
- 01 Jan Dunkel Schokolad
- 01 Jan Grapefruit Fish
- 01 Jan Less Code
- 01 Jan My Interview question
- 01 Jan Norse fun
- 01 Jan why I'm leaving microsoft

feed