惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
Spread Privacy
Spread Privacy
T
The Exploit Database - CXSecurity.com
Simon Willison's Weblog
Simon Willison's Weblog
P
Privacy & Cybersecurity Law Blog
L
LINUX DO - 热门话题
T
Threat Research - Cisco Blogs
T
Tenable Blog
TaoSecurity Blog
TaoSecurity Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
AI
AI
P
Proofpoint News Feed
A
About on SuperTechFans
P
Privacy International News Feed
月光博客
月光博客
雷峰网
雷峰网
S
Secure Thoughts
博客园 - 叶小钗
博客园 - 聂微东
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Project Zero
Project Zero
The Cloudflare Blog
SecWiki News
SecWiki News
The Hacker News
The Hacker News
V
Vulnerabilities – Threatpost
罗磊的独立博客
A
Arctic Wolf
阮一峰的网络日志
阮一峰的网络日志
Know Your Adversary
Know Your Adversary
酷 壳 – CoolShell
酷 壳 – CoolShell
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
Troy Hunt's Blog
The Last Watchdog
The Last Watchdog
Schneier on Security
Schneier on Security
小众软件
小众软件
有赞技术团队
有赞技术团队
博客园 - 司徒正美
T
Tailwind CSS Blog
量子位
C
Cybersecurity and Infrastructure Security Agency CISA
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Hugging Face - Blog
Hugging Face - Blog
人人都是产品经理
人人都是产品经理
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
S
Security @ Cisco Blogs
大猫的无限游戏
大猫的无限游戏
S
SegmentFault 最新的问题
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
L
Lohrmann on Cybersecurity

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The Magic Behind the Screen
Arthur · 2026-06-16 · via DEV Community

Mercedes-Benz, the drive.com.au reporting by Matt Adams informed us on May 3, has committed to bringing back physical buttons in its upcoming GLC and C-Class models. The company joins Audi, Volkswagen, Mazda, and a steadily lengthening list of carmakers admitting that the era of touch-everything dashboards was, in retrospect, a mistake. The story arrived at the front page of Hacker News shortly after publication, where it accumulated 797 points and 452 comments, the bulk of them written by people who would like to say they told you so and have, with some patience, been telling you so for ten years.

The Mercedes announcement is structured as a customer-led correction. "Customers told us two years ago," the company's sales chief Mathias Geisen told Autocar's James Attwood on April 27, "'guys, nice idea, but it just doesn't work for us', so we changed that and made it more analogue." It is a reasonable thing to say. It is also a much smaller thing than the situation it describes.

What was actually told

There is, in the public reporting around this announcement, a small piece of context that Mercedes' framing folds away. Customers were not the only party telling the company that touch-everything dashboards did not work. The European New Car Assessment Programme — Euro NCAP, the body whose five-star safety ratings drive a non-trivial fraction of the European new-car market — announced in November 2025 that its 2026 testing protocol would assess Human-Machine Interface design including "the availability of physical buttons for commonly used functions, which consumer feedback suggests can reduce distraction." Vehicles scoring highest, the protocol indicates, will be ones that demonstrate accessible physical controls. The reigning informal industry rule of thumb — that you cannot sell a car in Europe without a five-star Euro NCAP rating, or at least cannot sell it at the price point Mercedes wants to sell at — gives the announcement direct commercial weight.

Several HN commenters, working from a shared awareness of how this kind of announcement actually gets made, pointed out the parallel pressure from China, where new vehicle regulations are reportedly requiring physical controls for some functions over the same window. Some did not bother being polite about the framing: "Is is Mercedes-Benz deciding to bring back buttons," one commenter put it, "or is it that the EU's NCAP safety rating mandated that they bring back buttons, and they are spinning it as a voluntary decision?"

The customer-feedback story is the one Mercedes wants on the press release. It is also the one Mercedes can offer without having to publicly concede that the previous design was actively dangerous, which is the part of the story Euro NCAP's 2026 protocol exists to encode. "It just doesn't work for us" is the version of the user complaint that fits inside a company-led narrative arc. The Euro NCAP version — that the highest-rated vehicles must now demonstrate physical buttons for commonly used functions, because consumer feedback indicates this reduces distraction — is the regulatory version. They are describing the same physical fact.

The sentence that explains everything

The most quoted sentence from Geisen's Autocar interview — and the one that received, on HN, more sustained ridicule than the rest of the announcement combined — is the line in which he attempted to articulate Mercedes' continued faith in screens despite the partial reversal: "I'm a big believer in screens, because I really believe if you want to connect, you have to make the magic work behind the screen." It is worth pausing on this sentence, because it is the sentence that explains why the previous decade of automotive interior design happened.

The sentence does not parse well in any literal sense. "Magic work behind the screen" is an attempt to gesture at the domain in which a sales executive's instincts most natively operate, which is the domain of connecting with customers in a sales sense, where a phone-like interface is read as inherently aspirational and an analog one is read as inherently retrograde. One HN commenter, with the relief of someone who has been waiting for the right occasion to use a particular framing, observed that the sentence's parsing failure was the entire point: "I am a big believer in keeping “product people” away from UI design for dangerous machinery."

The framing is harsh, but the diagnosis is exactly correct. The sentence Geisen produced is not the sentence of someone designing a vehicle to be operated safely at speed. It is the sentence of someone designing a piece of hardware to feel, as a shopping experience, like a smartphone. The two design briefs produce different artifacts. The smartphone-first brief produces a 39.1-inch Hyperscreen covering the entire width of the dashboard. The safety-first brief produces a knob you can find with your hand without taking your eyes off the road. For a long stretch of the 2010s and 2020s, the auto industry chose the first brief. It is now being told by regulators, by customer surveys, by accident-and-injury data, and — only in the last twelve months — by its own sales numbers, that the second brief was the one it was supposed to be working from all along.

What the previous answer looked like

Multiple HN commenters, each independently, raised a fact about the dashboard-design problem that has the curious property of being old enough that it predates the entire industry detour: ISO 2575, the international standard governing the symbology of automobile dashboard indicator lamps, has been on the books since 1982. It is a forty-three-year-old document. Its function is to ensure that any driver, climbing into any car, can identify a critical condition without reading any text or making any cognitive effort beyond glancing at a known position on the dashboard.

The HCI literature on attention-management for high-stakes interfaces — pilots, surgeons, machine operators — has spent the same forty-three years discovering, in case after case, that the principles ISO 2575 encoded in 1982 are roughly correct. Tactile feedback is the form of feedback that a user can process while their visual attention is committed to something else. Muscle memory is the form of memory that survives the cognitive load of an actual emergency. Fixed positions are the form of layout that can be operated peripherally. None of these are deep findings. None of them have been overturned by anything subsequent. The auto industry, beginning around 2013, decided to operate as if they had been overturned by the iPhone.

What the auto industry actually did, when it removed the buttons, is a thing one HN commenter named directly: "screens over buttons is a cost cutting measure, not a first-principles design decision." The case is straightforward. A touchscreen is a single hardware part you can manufacture in volume, source from a small number of suppliers, decouple from the physical assembly of the dashboard, and update in software after the vehicle has shipped. A panel of physical controls is dozens of parts each requiring its own tooling, suppliers, electrical harnessing, fit-and-finish testing. Decoupling the UI from the hardware reduces production-pipeline complexity. It also means a UI team can ship updates years after the car has left the factory, which lets the marketing department promise "new features over the air" in a way that hardware-bound buttons cannot. The case for the touchscreen, on the supplier-side accounting, is real and quantifiable. The case for it on the driver-side accounting is the one that turned out not to hold up.

Both cases were running simultaneously. One was visible in spreadsheets. The other became visible only after the vehicles had been on the road long enough for the accident-and-injury data to accumulate, for the safety-rating bodies to absorb the pattern, and for the customer-research clinics to surface the "it just doesn't work for us" reports that Mercedes is now citing.

The settings-vs-controls distinction

A more constructive contribution to the HN thread came from a commenter who articulated, in a single move, the principled answer the industry should have arrived at without help: "Settings are great on a touchscreen. A wide variety of options, easily navigated to and explained. They suck on physical buttons, it ends up being like setting the time on a VCR. Controls on the other hand deserve physical buttons. Or levers. or dials/knobs/spinners. It should depend on muscle memory, and the type of control."

This is the right altitude at which to think about the design problem. The mistake the industry made, in the maximalist period, was conflating settings — preferences set once and rarely revisited, where a search-and-menu interface is genuinely superior — with controls, the physical actions a driver performs while operating the vehicle, where any visual interface is at best a degradation and at worst a hazard. The categories sort cleanly once you separate them:

Task Setting or control? Touchscreen ok? Why
Enter destination address into navigation Setting Yes Done while parked; the search-and-list affordance is genuinely superior to a 10-digit keypad
Customise dashboard wallpaper / colour theme Setting Yes Done once; revisiting is rare; cognitive cost of a menu is acceptable
Adjust fan speed when windshield is fogging Control No Done in motion; eyes must remain on road; muscle-memory + tactile feedback dominate
Adjust audio volume Control No Done in motion; the 1990s rotary knob was the right answer and remains the right answer
Toggle defroster, hazards, traction control Control No Time-critical; ISO 2575-class operation; must be findable without looking
Tune navigation map detail level / lane-guidance preferences Setting Yes Done occasionally; menu-search affordance fits
Skip music track Control Steering-wheel button Routine in-motion gesture; muscle memory is the entire interaction

The maximalist touchscreen treated all interactions as if they were settings. The auto industry's design vocabulary, for a decade, treated the categories as interchangeable. They are not.

What Mercedes is now doing — keeping the giant Hyperscreen, but adding back physical buttons in front of the dual wireless chargers and on the steering wheel — is, awkwardly, the architecture the settings-vs-controls distinction predicts. Settings stay on the screen. Controls — climate, volume, frequently-used cabin functions — return to surfaces a hand can find without the eye following. The implementation is partial; commenters with first-hand experience of the new VW ID-series and the post-facelift Mercedes A-Class noted that some of the newest models have replaced even the wheel-mounted physical buttons with capacitive-touch ones, which exhibits the same failure pattern at smaller scale. But the direction of travel is correct, finally, after a decade in which it was not.

The cost the industry didn't see in the spreadsheet

The thing the touchscreen detour cost, that the industry now has to figure out how to quietly amortize, is not primarily money. It is a decade of vehicles already on the road, owned by people who paid premium prices for them, that are worse to operate — on the testimony of the owners and reviewers who use them daily — than the cars those same people traded in. The industry-wide regression from analog to touch happened over a period long enough to ensure that an enormous installed base of touch-only vehicles will be on roads, and in resale markets, across the next vehicle-replacement cycle. The owners of those vehicles will not be retroactively given knobs. They will, instead, be given the experience of watching the next generation of cars advertise as a feature the absence of the design choice that defined their own.

There is no specific accounting line item for this kind of cost. The industry that produced it does not, on the available record, intend to apologize for it. The Mercedes announcement is structured to claim the reversal as evidence of the company's responsiveness to its customers, not as evidence that the previous decade's design language was a structural error. "We listened," is the language Mercedes wants in the headlines. "We were wrong, in a way that produced measurably worse outcomes for the people who paid us, for ten years" is not. The asymmetry is normal corporate speech. It is also the reason this kind of error tends to recur.

The auto industry will reverse this one over the next five years; the ID.Polo and the new C-Class will arrive with their physical buttons, the Euro NCAP ratings will adjust, the Chinese regulation will take effect, and the press cycle will declare the era of touch-everything dashboards officially over. What is harder to predict is what the next version of the same mistake looks like. The instinct that produced the maximalist touchscreen — the instinct that said make the car feel like a phone, because phones are the consumer-product surface customers are trained to want — has not been retired. It has only, momentarily, been overruled. The next opportunity it gets, in some adjacent product category whose safety profile is less easily measured by accident data and whose regulatory body is less vigilant than Euro NCAP, it will produce the same artifact again.

What stays

What stays from the Mercedes story, after the C-Class launch and the Euro NCAP rating cycle and the inevitable run of physical-buttons-are-back trend pieces, is the sentence Geisen produced when asked to explain the screens-and-buttons hybrid future. "I'm a big believer in screens, because I really believe if you want to connect, you have to make the magic work behind the screen." It is not a sentence about safety, attention, or the actual operation of a vehicle. It is a sentence about how a sales executive, who probably does not drive his own product in heavy weather at speed, models the customer's relationship to the dashboard. The sentence's parsing failure is the diagnostic; the decade of automotive interior design produced under its instinct is the symptom.

ISO 2575 has been on the books since 1982 and will remain so through whichever fashion cycle replaces this one. The mistake the industry made was assuming that the standard had been made obsolete by a new substrate, rather than recognizing that the standard was about the underlying physics of human attention, which the new substrate did not change. The buttons are coming back because they were never the part that needed to leave.

The magic, it turns out, doesn't actually have to work behind the screen. It mostly has to work under the driver's right hand, where it always did.