Deep Dive
The Setup: David Pierce's Vertical Tabs Argument
The debate kicks off with David Pierce's Verge article making the case for Chrome's newly-added vertical tabs feature. The Waveform crew immediately acknowledges that most of them are already pro-vertical tabs, having adopted them through Arc or other browsers. They position themselves to fact-check Pierce's reasoning about screen real estate. The core claim Pierce makes is that modern widescreen monitors waste precious vertical pixels when tabs sit horizontally at the top, while websites themselves are predominantly vertical in layout. This setup matters because it establishes the efficiency argument: horizontal tabs fight the natural proportions of contemporary displays.
The Pixel Count Showdown
One panelist conducts a precise measurement by screenshotting their browser in both configurations, importing into Photoshop, and calculating exact percentages. Horizontal tabs consume 3% of total browser window pixels; vertical tabs spike to 14%. This data seems to end the debate until defenders reframe the conversation around functional vs. wasted space. They argue the extra 11% vertical tabs consume is located in an area that would remain blank regardless — the left sidebar. Since websites center themselves and don't expand to fill lateral whitespace, occupying that horizontal real estate with tabs doesn't actually remove space from content. The analogy emerges: you wouldn't leave a bonus garage bay empty; you'd build something there since you have it.
The Two-Window Problem and Hiding Solution
The discussion fractures when someone points out that power users often split browsers side by side on widescreen monitors. Running two windows with vertical tabs creates a genuinely unusable layout: tabs, article, tabs, article becomes cramped. This is the strongest counterargument to vertical tabs. However, someone counters that Arc solves this through hidden tabs — swipe to reveal them like the macOS dock. The broader insight emerges: hiding tabs (whether in Arc or theoretically in Chrome) eliminates the entire space debate. Every website still scrolls vertically regardless of tab placement. If you hide tabs and maximize content, the efficiency gains of vertical layouts become irrelevant. The crew realizes the real solution isn't about orientation — it's about visibility.
Safari vs Chrome: The Unexpected Tangent
Ellis champions Safari for RAM efficiency and security, noting Private Relay provides constant protection. The counterargument is harsh: Safari lacks extensions and multiplatform support. Ellis concedes the extension limitation but emphasizes the RAM savings matter for heavy multitasking and running tools like Pro Tools alongside browsing. Chrome's memory footprint becomes the dealbreaker. However, Safari's ecosystem problem is real — it can't run on Linux or Android, forcing users who switch devices to abandon it. Arc also gets criticized for stagnation; it's been largely unmaintained and performance degrades over time. The takeaway isn't that one browser is objectively superior, but that ecosystem constraints (extensions, platforms, sync) matter more than any single feature.
The Habit Revelation
Near the end, the crew realizes the entire conversation exposes unconscious choice. One panelist uses keyboard shortcuts (Cmd+1 through Cmd+9) from 2011-era browsing habits. Another uses Safari primarily for its reading list feature despite other browsers offering similar functionality. Most admit they switched to Arc for vertical tabs but haven't evaluated alternatives in years. The recognition crystallizes: browser choice is almost entirely habitual inertia rather than rational optimization. Everyone's setup makes sense to them individually but looks bizarre to the group. This admission deflates the debate's stakes. The real conclusion isn't that vertical tabs are definitively better or worse — it's that you should use whatever you're already comfortable with, and if you want to optimize, hiding tabs and managing tab volume matters far more than orientation.