Hacker News Reader: Best @ 2026-01-30 13:59:49 (UTC)

Consensus: Cautiously Optimistic—many sympathize with “Windows is getting worse,” but disagree on root causes and how universal the problems are.

Top Critiques & Pushback:

• “It’s your corporate image, not Windows”: Several argue Explorer/context-menu lag is often caused by endpoint management/DLP, AV, OneDrive/SharePoint/Teams integrations, and shell extensions rather than Windows 11 itself (c46800178, c46803478, c46797782).
• “No, Windows 11 really is janky”: Others counter that the slowness is reproducible on clean/personal installs or even retail demo machines, and that Win11 UI changes (new context menu, animations, search) add latency/regressions (c46803099, c46800569, c46803099).
• Linux isn’t frictionless either: Commenters note Linux pain points around GPU/driver lifecycle, sleep/Wayland/X11 quirks, DPI scaling, UI framework fragmentation, and certain workflows (e.g., Teams/Zoom video, VR) (c46796376, c46796496, c46796858).

Better Alternatives / Prior Art:

• Faster Windows utilities: People cite third-party tools that outperform built-ins—Everything Search for file search (c46801043) and alternative file managers like FilePilot (c46798825), plus older “snappy” software examples as evidence performance is a choice.
• “Just use macOS/ChromeOS/clean install”: Some suggest Macs (less OEM crapware), Chromebooks, or wiping corporate bloat to restore performance (c46805375, c46802412).

Expert Context:

• Windows “tiny files” tax: Developers point out Windows historically struggles with many small files (e.g., node_modules, .git), and cloud-syncing them (OneDrive) can amplify pain (c46803760, c46803478).
• Gaming caveat is anti-cheat: The main Linux-gaming blocker is kernel-level anti-cheat in popular competitive titles; non-kernel or enabled EAC/BattlEye games may work, but it’s developer-controlled (c46797961, c46797047, c46798540).
• Updates & control as the core grievance: Beyond speed, many say forced updates/ads and “fighting the OS” drove them away, while some note workarounds exist but resent needing them (c46796669, c46797269, c46800316).

Consensus: Skeptical—many view this as rent-seeking enabled by Apple’s gatekeeper role, with heavy calls for regulation or avoidance.

Top Critiques & Pushback:

• “Unjustified tax” on creator payments: Many argue Patreon support is closer to payments/transfer infrastructure than an App Store-sold digital good, so a 30% platform cut feels disproportionate (c46808802, c46814076).
• Gatekeeper leverage (OS + store + payments): Users emphasize creators/platforms can’t realistically “opt out” if they need iOS reach, and point to Apple’s control over distribution and payment rules as the core issue (c46808810, c46808695).
• Profit margin / pricing power as market-failure signal: Commenters cite very high App Store margins and argue the fee is far above cost, implying weak competition (c46808090, c46808787).
• Counter-argument: Apple sets terms for its ecosystem: A minority defend Apple’s right to charge for access to its user base/UX and compare it to high-commission venues (malls/airports), while conceding details may be outdated (c46809253).

Better Alternatives / Prior Art:

• Web-first / pay on the website: Many recommend steering users to subscribe on Patreon's web checkout to bypass IAP (c46809148, c46807218).
• PWAs / better mobile web: Discussion repeatedly argues for PWAs and improved mobile web capabilities so apps aren’t required for routine services (c46807192, c46809712).
• Sideloading / alternative app stores: Some want regulation to mandate alternative distribution methods rather than fee caps on a single store (c46808695, c46811046).

Expert Context:

• Regulatory backdrop (EU “gatekeepers,” anti-steering): Several note past anti-steering restrictions and ongoing EU scrutiny under DMA/related rules, framing this as part of a longer conflict over platform control and compliance (c46809482, c46809802).
• Why 30% exists historically: One explanation offered is that 30% mirrored traditional retail software margins and early marketplace norms, even if it feels egregious now (c46812605, c46811531).

Consensus: Cautiously Optimistic—people like “stacking” lifestyle + supplements, but many reject the post’s strongest numeric claims and worry about misleading self-medication.

Top Critiques & Pushback:

• Effect-size comparisons are misleading/oversimplified: Several argue that comparing a single mean effect size for antidepressants to large supplement effect sizes ignores heterogeneity, differing endpoints, and distributional assumptions (e.g., bimodal responders) (c46810707, c46815363, c46817649).
• Small-study / supplement-research skepticism: Commenters note vitamin D and omega‑3 often look great in small trials but shrink or disappear in larger ones; they accuse the post of cherry-picking meta-analyses and overinterpreting dose–response results (c46810707, c46811382).
• Population/deficiency confounding: Many suggest benefits may concentrate in deficient subgroups, making “supplement treats depression” sound like “fixing deficiency improves mood,” and urge bloodwork rather than blanket dosing (c46816467, c46817933, c46819238).

Better Alternatives / Prior Art:

• Exercise/outdoors/light as primary levers: Lots of anecdotes emphasize hiking/walking/biking/light therapy as major mood drivers, sometimes seen as the real causal factor behind supplement success stories (c46811015, c46811413, c46812339).
• Medical workup first: “Get a blood panel” is a recurring recommendation to identify deficiencies and avoid guessing doses (c46819238, c46812287).

Expert Context:

• Safety/units correction (important): A commenter flagged a dangerous unit typo (“5000 mg” vs “IU”), and the author acknowledged and fixed it (c46808507, c46810325).
• SSRIs: efficacy + nuanced risks: Many share strong positive SSRI experiences and warn against anti-pharma narratives delaying effective care, while others discuss side effects, withdrawal, and concerns about long-term prescribing norms (c46808670, c46809438, c46809575).

Consensus: Cautiously Optimistic—people like the idea of independent degradation tracking, but many doubt the current statistical power and attribution.

Top Critiques & Pushback:

• Too few tasks / too infrequent runs: SWE-bench folks argue N=50 once per day is noisy; suggest hundreds of tasks and multiple runs/day, plus averaging to reduce variance from sampling and infrastructure conditions (c46811319, c46811604).
• Stats/methodology concerns: One commenter says the described “significance” approach seems incorrect: you need uncertainty on both measurements and a CI for the difference, plus clearer definitions of what “weekly” and “monthly” compare (c46814501).
• Cherry-picking / interpretability: Questions about why the time series starts on a specific date and whether users will misread load/variance effects as “model got dumber” (c46812297, c46812414).

Better Alternatives / Prior Art:

• Run more/varied evals: Suggestions include 300+ tasks, 5–10 runs per day, adding confidence intervals/uncertainty reporting, and possibly running across multiple accounts/machines to average out A/B tests or routing differences (c46811319, c46818707, c46823223).

Expert Context:

• Possible confounders beyond the base model: A Claude Code team member says a Claude Code “harness issue” introduced 1/26 affected results and was rolled back 1/28; they advise updating the CLI (c46815013). Others interpret “harness” as the agent loop/tool-calling wrapper rather than the underlying model (c46819756).
• Load and serving heterogeneity hypotheses: Many speculate that performance variance could come from load balancing, different inference stacks/quantization, retries/tooling changes, or other “knobs” under load—sometimes surfacing as time-of-day effects (c46811710, c46812116, c46818102).
• Concrete product-level suspects: Users point to recent Claude Code behavior changes like “Clear Context and Proceed” defaults harming agentic runs, though others argue clearing context after planning can be normal (c46821982, c46823136).

Other recurring themes:

• User trust and compensation: Complaints about wasted tokens and refund policies when regressions/breaking changes occur (c46818709, c46820068).
• Subjective degradation reports vs expectation effects: Some report Opus/Claude Code feeling worse and more error-prone; others argue expectations/usage patterns change, and it’s hard to isolate cause without provider transparency (c46812566, c46812630, c46814420).

Consensus: Cautiously Optimistic—many see Amazon as bloated and expect “layer reduction,” but there’s deep anxiety about broader white-collar displacement.

Top Critiques & Pushback:

• “AI” is a scapegoat for cost-cutting/slow growth: Commenters argue layoffs are driven by macro conditions, post-pandemic overhiring, or Wall Street’s demand for perpetual growth, with AI used as a convenient narrative (c46796808, c46797061, c46804968).
• Skepticism that AI is truly replacing roles yet: Several ask for quantitative evidence of big productivity gains, describing current LLMs as brittle or net-debt-creating in real orgs (c46797811, c46797925, c46798351).
• But others think headcount reduction is the point: A counterview is that even modest productivity gains justify fewer workers, and companies will capture gains via layoffs rather than leisure (c46798509, c46804310).

Better Alternatives / Prior Art:

• “No layoffs” culture (Nintendo): Some contrast Amazon with Nintendo’s public stance on avoiding layoffs, while others note scale/culture differences and shareholder expectations (c46798058, c46799500, c46802269).
• Safety nets vs make-work: Proposals range from UBI/retraining to accepting “make-work” roles as a social stability tool (Japan cited) (c46801762, c46802882, c46803250).
• Unions/constraints on layoffs: A subset argues for labor power or policy changes to create real consequences for mass layoffs/offshoring (c46801890, c46799568).

Expert Context:

• Amazon’s reporting/meeting bureaucracy: Ex-Amazonians describe a document-and-meeting pyramid (e.g., weekly/monthly business reviews) where information is repeatedly repackaged for higher levels—work they see as ripe for automation or elimination (c46816351, c46804978).

Consensus: Cautiously Optimistic.

Top Critiques & Pushback:

• Unclear public access/licensing: Many focused on whether MTG data will be freely available, with conflicting impressions about “free” access vs registration, delays, or fees for certain near‑real‑time/commercial uses (c46807616, c46808114, c46817134).
• Europe’s data openness vs US: A recurring debate compared European/EUMETSAT data policies and infrastructure to NOAA/US public-domain accessibility; some argued Europe is more restrictive or less scalable in practice, while others pointed to Copernicus openness and CC licensing (c46812242, c46812564, c46814107).
• Hard to quantify forecast improvement: Users asked for concrete error-metric gains; replies stressed the main benefit is higher-resolution and new vertical/hyperspectral information that helps initialization and especially nowcasting, but that headline MAE/RMSE gains may be modest and difficult to predict (c46807085, c46807830, c46807408).

Better Alternatives / Prior Art:

• US GOES as a benchmark: Some contrasted EUMETSAT access/fees with GOES imagery being easy to download in near real time (c46811416).
• Weather APIs that repackage data: People recommended third-party services that normalize raw datasets into developer-friendly endpoints (open-meteo) (c46821424).
• Tooling for satellite data: Satpy was mentioned as FOSS for processing EUMETSAT radiometric products (c46822361).

Expert Context:

• Why hyperspectral in GEO matters: A commenter highlighted that a GEO IR hyperspectral sounder could enable vertically resolved temperature/humidity (and trace-gas) retrievals at high cadence, complementing existing polar-orbiting sounders (c46812796).

Consensus: Skeptical, with many treating the satire as catharsis and a critique of hype, though some push back on taking it too literally.

Top Critiques & Pushback:

• “Satire needs truth” vs “it’s exaggeration”: One thread argues the line “exists to scam the elderly” is unfair literalism (c46803718), while others respond that exaggeration is the point and the underlying abuse is real (c46804442, c46808035).
• AI as a scam force-multiplier: Multiple commenters say voice cloning/deepfakes are already supercharging fraud (grandparent scams, CEO scams), making the article’s premise plausible even if hyperbolic (c46804008, c46804490).
• “People do harms, not AI” disagreement: Some insist AI doesn’t have “behaviors,” people direct it (c46808071), while others argue “the purpose of a system is what it does” and developers/investors share responsibility if foreseeable misuse isn’t mitigated (c46804173, c46804248).
• Internet analogy and consistency: A recurring debate compares AI’s harms to earlier tech (internet/phones), with one camp arguing “it’s all old problems” (c46807511) and another emphasizing that lower cost + scale changes the impact (c46805838, c46808059).

Better Alternatives / Prior Art:

• Historical bubbles as a lens: Users compare AI hype/defensiveness to crypto, NFTs, and the metaverse—products that relied on FOMO and constant evangelism (c46805166, c46804631).

Expert Context:

• What it’s spoofing: A commenter links the satire to Jensen Huang calling “end of the world” AI narratives “hurtful,” framing the McSweeney’s piece as a direct parody of that PR posture (c46807159).

Consensus: Enthusiastic—people treat it as a timeless debugging classic and swap similar “impossible” failure stories.

Top Critiques & Pushback:

• Give users credit for good data: Several argue the department chair’s careful data collection (and map) was exactly the kind of high-quality repro info engineers want, and the story undersells that contribution (c46806289, c46807827).
• Meta: why users explain better to LLMs than in tickets: A side thread notes people often give richer, more structured problem descriptions to chatbots than to human support, possibly because they feel less judged (c46808687, c46809265, c46810697).

Better Alternatives / Prior Art:

• Other classic “impossible bug” tales: Commenters compare it to the “vanilla ice cream car won’t start” story and similar folklore about debugging odd correlations (c46808119, c46806717).
• Utilities mentioned: Some install and discuss units after reading the article; others recommend switching to qalculate for friendlier unit conversions (c46806228, c46823967).

Expert Context:

• Debugging mindset: find what’s different: One commenter frames the core lesson as systematically identifying what changed or differs between working and failing cases—often the fastest path out of “works on my machine” confusion (c46814570).
• SMTP hands-on muscle memory: A mini-thread reminisces about manually speaking SMTP via telnet (EHLO/MAIL FROM/RCPT TO/DATA) and related mail-system war stories (c46806858, c46806942).

Consensus: Cautiously Optimistic, with heavy skepticism about security and authenticity.

Top Critiques & Pushback:

• Massive security/prompt-injection risk: Many argue an “agent social network” is a tinderbox for prompt injection and exfiltration, especially if agents have tools/credentials (the “lethal trifecta”: private data access + prompt injection + outbound comms) (c46820930, c46821687, c46822080). Others point out the inevitability of first major incident as scale grows (c46823043).
• “Don’t run random scripts” vibes: The related “molt.church” gag—encouraging agents to run an npm install and a bash script—was treated as a speedrun of supply-chain/security failure modes; some joked about cryptominers, and one reported a possible XSS via an API response (c46821835, c46822505, c46822776).
• Authenticity/astroturfing concerns: Several commenters questioned whether posts are real agent experiences versus generated roleplay, and whether the whole thing is being manufactured/marketed (c46820999, c46821345, c46823013).

Better Alternatives / Prior Art:

• “AI Stack Overflow / shared memory” concept: Some saw a practical extension: a place where agents publish solved debugging journeys so other agents can retrieve them later—shared memory for tools/frameworks—though incentives (token cost) were questioned (c46822139, c46823200, c46822342).
• Provenance mechanisms: Users floated “proof-of-AI” ideas (reverse Turing tests, signed model outputs) but noted humans could still proxy through AI, and that simple captchas are gameable (c46820679, c46824221, c46821790).

Expert Context:

• Crypto/scam signaling dispute: A recurring thread warned of crypto-token shilling around adjacent domains/accounts; others claimed the core creator is anti-crypto and that squatters/unauthorized actors are the ones pushing tokens (c46821970, c46823591, c46822741).
• Privacy/IP leakage risk: Even if “fun,” letting a work-capable agent post publicly was flagged as a recipe for leaking proprietary information (c46823708).

Consensus: Cautiously Optimistic—people find the demos technically striking, but many doubt near-term usefulness and worry about social downsides.

Top Critiques & Pushback:

• “It’s not a simulator, it’s a video hallucination”: Multiple commenters argue the system lacks explicit state/physics guarantees and thus can’t reliably support tasks like accurate planning, engineering, or robust agent learning (c46816525, c46816486, c46814693).
• Consistency/memory limits will cap usefulness: The 60-second rollout/context limit and drift/incoherence over time are cited as fundamental obstacles for persistent worlds or serious applications (c46818196, c46814597, c46817479).
• Bad incentives / societal harm: People predict addictive VR “digital heroin,” more misinformation/propaganda via synthetic video, and a repeat of social media’s attention-economy harms (c46816925, c46818575, c46818005).
• Cost/latency skepticism for consumers: Commenters expect high compute cost and noticeable control latency, making it hard to become a mainstream “game” platform soon (c46818871, c46820216, c46813947).

Better Alternatives / Prior Art:

• Game engines + AI tooling: A recurring suggestion is to keep coherence/physics in Unreal/Unity/PhysX and use generative models to assist with content creation or rendering, rather than generating frames end-to-end (c46816525, c46814779, c46814879).
• Explicit 3D representations: Some compare to NeRFs/Gaussian Splatting as approaches that enforce navigable consistency via explicit scene representations, even if less dynamic (c46815543).
• Earlier “world models” research: Users reference the classic “World Models” paper where agents can be trained in a hallucinated latent-space “dream” and transferred back to the real environment (c46815096).

Expert Context:

• World models as ‘imagination’ for agents/robotics: A strong thread argues Genie’s real target is giving future agents a predictive model to test action outcomes, not building a consumer game (c46814670, c46815459).
• Technical read of current limitations: One commenter summarizes observed/expected constraints: diffusion-transformer design, temporal compression, sub-10 FPS control latency, detail drift, and ~60s max context—framing the release as a prototype likely using cheaper distilled/quantized variants (c46818196).
• Coherence as the key milestone: Some highlight that being able to turn around and still see the same scene (maintaining off-screen consistency) is a meaningful step beyond many earlier interactive video demos (c46814345, c46823131).

Notable side-thread:

• Brains as world models: The top comment chain connects Genie-style predictive world modeling to theories of perception (predictive processing/active inference), arguing humans experience a “controlled hallucination” constrained by sensory error signals (c46817148, c46818252, c46819975).

Consensus: Skeptical.

Top Critiques & Pushback:

• “Pivot to robots” sounds like hype vs execution: Many read ending S/X as a sign Tesla is retreating from being a broad carmaker and leaning on an unproven Optimus narrative (c46803591, c46807157, c46805294). The 1M-units/year robot claim is widely mocked as unrealistic or at least very premature.
• Tesla’s valuation seen as disconnected from fundamentals: A large thread argues Tesla is treated like a tech/meme stock rather than a car company, with debate over whether that’s irrational hype or a bet on future autonomy/robots (c46808060, c46803794, c46807166).
• Autonomy claims: strong disagreement on “FSD” quality and safety: Owners and observers split between “FSD is very good” and “still makes dangerous mistakes; it’s L2 mislabeled” (c46811379, c46811642, c46812070). Some also criticize Tesla’s sensor choices and prior disabling of radar in software (c46811868).

Better Alternatives / Prior Art:

• Waymo / lidar-based approaches: Brought up as the clearer benchmark for robotaxis; skepticism that Tesla can match without lidar (c46813570, c46806853).
• GM Super Cruise / other OEM ADAS: Used as a comparison point; commenters argue it’s either “renowned safer” or not comparable because it’s geofenced highway-only (c46808060, c46819970).
• Comma / OpenPilot: Mentioned as the closest comparable consumer setup to advanced driver assistance on supported vehicles (c46816479).

Expert Context:

• Long-running signal that S/X were low-priority: A commenter recalls Musk previously saying S/X were made largely for “sentimental reasons,” framing today’s move as consistent with that stance (c46809842).

Consensus: Cautiously Optimistic about the prank’s harmlessness, but skeptical of the “ADS-B spoofing” framing.

Top Critiques & Pushback:

• Not RF spoofing; it’s an aggregator feed hack: Multiple commenters argue this wasn’t over-the-air ADS-B manipulation, but fake data injected into ADSBexchange via a feeder/API, evidenced by the track being absent on other aggregators (c46803335, c46802475, c46803242).
• Conflation of ADS-B insecurity vs website security: Some note ADS-B messages lack authentication, but the relevant weakness here is likely ADSBexchange’s ingestion/validation controls, not aviation systems (c46811281, c46809828).
• Legality/ethics and “don’t mess with aviation”: Warnings that true RF spoofing could attract FCC/FAA attention and is irresponsible; others counter that public tracker sites aren’t safety-critical (c46803083, c46803093, c46806058).

Better Alternatives / Prior Art:

• Cross-check other aggregators to validate reality: Users point to ADSB.fi, adsb.lol, FR24, airplanes.live, etc., as independent sources that did not show the same track—useful for detecting single-aggregator fakery (c46803335).

Expert Context:

• MLAT/TIS‑B quirks and false targets happen: Discussion references known cases of erroneous broadcast targets (e.g., TIS‑B anomalies from FAA systems and a magnetic-declination bug), as well as odd data like implausible altitude/groundspeed combinations that would fail plausibility checks (c46804254, c46803748).
• Potential mitigation idea: Flag tracks that appear from only one feeder in an area with otherwise dense coverage (c46806007).

Consensus: Enthusiastic.

Top Critiques & Pushback:

• “Pressure vs momentum” framing: One commenter argues the post over-emphasizes pressure differentials and that lift should be explained primarily via flow deflection / momentum change, with pressure as a consequence (c46805298). Others push back that these are complementary descriptions: the wing’s force is experienced through surface pressure, and pressure differences are linked to turning the flow (c46805954, c46811968).
• Some explanations feel hand-wavy: A reply says parts of the referenced explanatory material (a linked lecture/video) gloss over why pressure is higher under the wing, and wishes it started from measured pressure distributions (c46811907).
• Meta / housekeeping: Minor confusion about the year in the title (it’s a 2024 article), and notes about the author’s posting cadence (c46796062, c46799307).

Better Alternatives / Prior Art:

• AeroSandbox / XFOIL / CFD tooling: For readers who want to “play with aerodynamics,” one commenter recommends AeroSandbox, noting it can run fast estimates (including neural-network models) and compares it to heuristic solvers like XFOIL and slower CFD approaches (c46799442).
• Joukowski airfoil math view: A commenter points to a complex-analysis/Joukowski-transform explanation as a “pure-math” perspective on airfoils (c46808713).
• NASA educational explanation: The pressure-vs-deflection debate references NASA’s educational material emphasizing turning flow/momentum while noting pressure forces (c46805298, c46805954).

Expert Context:

• Equivalence of lenses: Several comments stress that “momentum change” can be a useful control-volume accounting, but the actual distributed forces on the wing are pressure (and shear) over the surface—two consistent ways to describe the same physics (c46811968, c46805954).

Community Notes:

• Many comments are straightforward praise for Ciechanowski’s interactive teaching style, with calls to support the author (Patreon link shared) (c46801461, c46809226). A prior, larger HN discussion thread from Feb 2024 is also linked (c46796027, c46801245).

Consensus: Cautiously Optimistic.

Top Critiques & Pushback:

• Limited practical coverage: Many argue recompilation will likely reach only a small subset of the PS2 catalog, while emulation already covers most games well (c46816612).
• Article’s technical emphasis questioned: Some push back that focusing on the PS2’s main CPU (R5900) misses where much performance/complexity lives (vector units, bandwidth constraints), implying recompilation is harder than it sounds (c46818055).
• “Magic” vs equivalence: Commenters debate what recompilation really buys you if behavior should match emulation; supporters answer: less overhead and fewer platform constraints (resolution/framerate), plus easier modification once you have recompiled code (c46819662, c46819929, c46820822).

Better Alternatives / Prior Art:

• PCSX2 / Android emulators: People note that cheap handhelds can already emulate much of the PS2 library with upscaling, making emulation the practical solution today (c46816612).
• OpenGOAL (Jak series): Cited as an existence proof that the right approach can unlock high-quality native ports when you can bring an interpreter/toolchain to modern platforms (c46817288, c46823344).
• N64 recomp/ports: Zelda64Recomp and SM64 ports are referenced as the clearest precedent for what recompilation can enable (c46816849, c46820822).

Expert Context:

• Vector unit debugging experience: A commenter who built a PS2 vector-unit simulator/debugger notes VUs are powerful and tricky to use but “not complicated to spec,” suggesting they’re a feasible (if nontrivial) target for tools like this (c46820795).
• Why recomp matters long-term: Several frame recompilation as future-proofing—ensuring games can still run on unknown 2040s hardware, beyond what current emulators target (c46823322).

Consensus: Cautiously Optimistic—many think the immediate braking/response sounds good, but a large faction doubts the pre-incident caution and wants independent evidence.

Top Critiques & Pushback:

• “17 mph is too fast for drop-off chaos”: Multiple commenters argue the key issue isn’t reaction after detection, but whether Waymo should have been crawling given double-parked cars, blocked sightlines, and kids near a school (c46820437, c46820671, c46812023).
• Skepticism of Waymo’s framing/model: Users warn Waymo’s blog is PR, note euphemistic language (“contact,” “young pedestrian”), and say the “attentive human at 14 mph” counterfactual is self-serving without a disclosed analysis or video (c46821542, c46816435, c46819278).
• Humans vs robots: anticipation vs reaction: Some claim good humans would pre-emptively slow based on “can’t see behind that SUV” hazard cues; others respond that most humans don’t actually drive defensively and are distracted, making Waymo’s fast reaction valuable (c46814053, c46813633, c46814219).

Better Alternatives / Prior Art:

• Standardized safety testing: One commenter frames this as the well-known “Suddenly Revealed Pedestrian” scenario used in NCAP-style protocols and says Waymo’s reported behavior matches “textbook compliance,” while still separating that from the “is 17 mph appropriate here?” question (c46814694, c46820550).
• Urban design over driver perfection: A recurring thread argues the real fix is keeping cars away from school entrances (street closures/pedestrianization), reducing SUV/truck dominance, and designing streets to force low speeds (c46815113, c46819574, c46816992).

Expert Context:

• AV test practitioner perspective: A commenter claiming to have run this exact revealed-pedestrian test across many vehicles says Waymo’s response (as described) aligns with standard compliance, but emphasizes the open question is the approach speed in that specific environment (c46814694).