Hacker News, Distilled

What changed in view counts

• Many creators report sharp drops in desktop view counts on a specific date, while ad revenue stayed flat and mobile views were unchanged.
• A widely cited GitHub issue indicates EasyPrivacy added a YouTube metrics endpoint (/api/stats/...) to its tracking blocklist; that endpoint is used to attribute views, so adblocked plays now often don’t increment the public counter.
• YouTube’s official note says ad blockers and “content blocking tools” can affect reported views, especially for channels whose audiences use them heavily.
• Several commenters are surprised YouTube relies on client‑side calls for public view counts instead of purely backend logging, calling it fragile and easily broken.

Effects on creators and revenue

• Creators say YouTube ad revenue hasn’t dropped in line with views, implying the missing views were from users who were never monetized anyway (adblock users).
• However, lower public view counts hurt:
  • Negotiating power and pricing for in‑video sponsorships.
  • Channel growth and recommendations, if the algorithm heavily weights views.
• Tech‑oriented channels (with high adblock usage) appear hardest‑hit; some worry this systematically disadvantages more technical or “FOSS‑y” audiences.
• There’s concern Premium users with adblockers may undercount as well, potentially reducing payout from subscriptions.

Ad blockers, tracking, and ethics

• One camp: blocking both ads and tracking (including view metrics) is exactly what privacy lists promise; if creators lose views, that’s a platform or business‑model problem, not the user’s.
• Another camp: viewers who block everything but keep using the service are “leeching”; the “moral” options are to pay (e.g., Premium) or stop using YouTube.
• Counter‑argument: the modern ad ecosystem is scam‑ and malware‑ridden; adblocking is basic self‑defense. Users are entitled to control what runs on their machines and what data is sent.

YouTube’s incentives and suspected strategy

• Some suspect YouTube is happy to let this play out because:
  • It turns creators against adblock users without YouTube directly attacking them.
  • Undercounted views devalue off‑platform sponsorships (from which YouTube earns nothing) relative to YouTube’s own ad products.
• Others think it’s more likely an uncoordinated mess: anti‑tracking lists shifted, internal teams didn’t realize, and YouTube’s creator comms are characteristically vague and late.

Recommendation quality and user behavior

• Many report watching less YouTube due to:
  • Aggressive pre‑rolls and anti‑adblock popups.
  • Poor recommendations, AI‑generated “slop,” ragebait, and Shorts.
• Others say recommendations are excellent if you rigorously avoid low‑quality content and use “don’t recommend” tools.
• Some users report replacing many “how‑to” videos with LLM answers and using alternative clients (NewPipe, Freetube, SmartTube, patched apps) to escape ads and Shorts.

Technical debates about counting views

• Server‑side counting via CDNs and segmented streams is seen as non‑trivial (buffering, skipping, bots, shared IPs), which partly explains client‑side view APIs.
• Critics respond that if YouTube can track watch history and Premium usage, it could design a more robust, less blockable view metric—if it wanted to.

Why browser-level DoH on Android?

• Many argue the main reason is privacy from the OS vendor (Android = Google). Users may prefer to trust a browser over the OS stack.
• Browser-level DoH reduces the number of parties that see DNS queries (no OS, VPN app, or OEM resolver in the path).
• Android’s DNS features are version- and vendor-dependent; not all devices or ROMs support DoH/DoT consistently.
• Firefox can offer clear UI controls for enabling/disabling DoH and choosing resolvers, which Android typically does not.
• Firefox uses a curated list of “trusted recursive resolvers” with contractual privacy guarantees, unlike opaque OS behavior.

Privacy, leaks, and limitations

• Several comments point out that DoH alone doesn’t hide which site you visit: IPs and TLS metadata still leak information.
• Others note that Firefox pairs DoH with Encrypted Client Hello (ECH), which together better conceal domains from on-path observers.
• Android VPN and “privacy” features have had DNS and connectivity-check leaks, making in-app DoH attractive for those who don’t trust the OS.

DoH providers, centralization, and trade-offs

• Suggested providers: Quad9, Mullvad, NextDNS, ffmuc, Wikimedia’s experimental service, self-hosted DoH (with caveats).
• Quad9 is praised for global coverage and strict IP-handling policies; Mullvad for privacy/ad-blocking but limited geography.
• Cloudflare’s short-term logging and sampled packet retention raise concerns for some; others see that as acceptable.
• Centralization is a major worry: defaulting to a few big DoH resolvers shifts visibility from ISPs to large global players.
• Techniques like splitting queries across multiple resolvers are discussed but may unintentionally leak more information per “site.”

Impact on local/self-hosted DNS

• Operators of home or custom DNS lose transparent control when browsers bypass DHCP-provided resolvers via hardcoded DoH.
• This breaks internal split-horizon DNS and local overrides unless clients are explicitly configured.
• RFC 9463 is mentioned as a mechanism to advertise DoH endpoints via DHCP, but tooling support is still lacking.

DoH vs DoT and technical details

• Android is noted as primarily supporting DoT, not DoH; Firefox chooses DoH because it blends into normal HTTPS (port 443) and circumvents ISPs that block third-party DNS.
• Some note that, since Firefox is a browser and the DoH spec’s lead author had browser background, HTTP tooling and expertise made DoH a natural fit.

Disabling or controlling DoH on networks

• Network operators wanting to block DoH face difficulty because it’s just TLS on port 443.
• Options mentioned: IP/SNI blocking of known DoH hosts, or full TLS interception and strict egress firewalls; both are imperfect or heavy-handed.

Firefox for Android UX and alternatives

• Opinions on Firefox Android performance are split: some report severe lag and poor background behavior; others find it fine even on older hardware.
• Many continue using it solely for full uBlock Origin support.
• Alternatives discussed: Brave, Orion (iOS), Lemur, Kiwi, Vivaldi, Samsung Browser with adblock extensions, and Edge Canary with extension support.
• Some prefer DNS-level adblocking (Pi-hole/AdGuard Home + VPN/Tailscale), while others say this is less effective than in-browser blocking.

Waymo–Lyft partnership & geographic expansion

• Commenters see this as Waymo’s first non-pilot commercial rollout with Lyft, and notable because it’s non‑exclusive: riders can use either the Waymo or Lyft app.
• Many view this as an “inflection point” in coverage: SF, SFO, Phoenix, LA, Austin, Atlanta, Nashville, Silicon Valley suburbs, plus testing or hiring in other US cities and Tokyo.
• Some locals (e.g., Atlanta, Nashville) report seeing rapid growth of Waymo vehicles and say they’re “no worse” than human drivers, sometimes safer or more comfortable.

Economics, costs, and remote operations

• One camp believes Waymo is approaching or at break‑even in dense markets: high utilization, higher per‑mile pricing than Uber, and falling lidar/hardware costs.
• Skeptics highlight expensive vehicles, hardware tariffs, ongoing R&D, and unknown spending on remote assistance and mapping; they doubt “few months” payback and expect multi‑year amortization.
• Back‑of‑envelope analysis suggests labor is largely fixed engineering cost, with relatively low marginal cost per additional vehicle. Remote assistance ratios are guessed between 1:10 and 1:100 cars.
• Waymo hints at “very positive” unit economics but doesn’t disclose numbers; some see this secrecy as competitive discipline, others as a sign they’re still not clearly profitable.

Uber/Lyft’s role and strategic risk

• Waymo benefits from ride‑hail platforms for instant distribution, overflow coverage by human drivers, and avoiding building all operations (support, payments, regulatory know‑how) itself.
• Platforms gain more “drivers” and can keep serving rides even if AV fleets are small at first.
• Several commenters argue Uber/Lyft are ultimately commoditized: they don’t own cars or core AV tech and could be reduced to low‑margin fleet management or licensed operators.
• Others see potential acquisitions (e.g., Lyft as a cheap channel) but question Lyft’s “moat” beyond operational knowledge and regulatory relationships.

Competition: Tesla, Zoox, others

• Some users are bullish on Tesla Robotaxi, citing early Bay Area rides and Tesla’s hardware scale; others ridicule it as years behind Waymo and primarily stock‑price theater.
• Zoox and Chinese players (Pony.ai, Baidu) are mentioned as serious long‑term competitors, though US market access for Chinese firms is doubted.

Societal impact, transit, and labor

• Strong thread debating whether autonomous taxis solve real problems versus just entrenching car‑centric cities.
• Critics argue trains, trams, and buses are more efficient for traffic, environment, and safety; AVs may worsen congestion via empty “deadhead” miles.
• Supporters counter that US public‑transit build‑out is politically and financially broken; AVs could pragmatically leapfrog those constraints and improve safety and comfort.
• Significant discussion of autonomous buses: technically easier and could enable higher frequency, but blocked by driver unions, security/cleanliness needs, and politics.
• Broader concerns: privatization failures, dual‑use (warfare) worries, and concentration of power in a trillion‑dollar mobility monopoly.

Ownership and user experience

• Many riders like driverless rides for safety, comfort, price, and not dealing with human drivers.
• Others dislike being surveilled or “rated” and prefer personal cars or rentals.
• Some hope for individually owned self‑driving cars eventually; others think ubiquitous robotaxis will make ownership a luxury or niche convenience (e.g., storage, family gear, home backup battery).

Import corruption & evidence

• The issue appears when importing from SD cards/cameras into macOS Photos, especially with Olympus/OM System RAW (ORF), but some report corruption with iPhone/iCloud-only workflows too.
• Checksums differ between source and imported files; binary diffs show large contiguous blocks (multiples of 512 bytes) being replaced, not just single-bit flips.
• The author says they swapped essentially all hardware (laptop, camera, etc.) and still reproduced the problem, pointing strongly at Photos/import software rather than hardware failure.
• Several users report milder artifacts (e.g., green lines, flipped images) but visually intact files; others have completely unreadable or partially overwritten images.

Suspected root cause

• Many commenters think it’s an import-pipeline bug in Photos: a concurrency or buffering issue in the extra work done on import (merging RAW+JPEG, previews, database writes, optional delete-on-import).
• The 512-byte granularity points some to a storage or filesystem-level corruption path; others still recommend RAM/disk tests and checking APFS block sizes.
• A minority argue it could be OM’s USB implementation or SD cards, but counterexamples from non-OM cameras and iPhones weaken that explanation.

Workflows, mitigation & backups

• Strong consensus: never use “delete after import” from the card/camera; only erase cards in-camera after verified backups.
• Recommended workflows:
  • Copy from SD to local disk first, then import into Photos/Lightroom/Darktable.
  • Keep multiple copies (local + NAS + cloud), keep SD cards until off-device backups exist, sometimes even treat SDs as write-once archives.
• Tools mentioned: Image Capture, Darktable, Lightroom, Digikam, PhotoSync, Immich, PhotoPrism, Landrop/LocalSend, osxphotos, PhotoRec/DiskDrill for recovery.

Apple software quality & bug handling

• Multiple anecdotes of data or metadata integrity issues across Apple apps (Photos, Image Capture, Music/iTunes, Notes, Reminders, iCloud Drive, Maps).
• Several describe iCloud Photos corrupting previously good images or making them unexportable.
• Reporting bugs via Feedback Assistant/Radar is widely described as frustrating: demands for “example projects,” long silences, low priority for long-shipped bugs, and triage overwhelmed by volume.
• Some ex-insiders and QA engineers note systemic underinvestment in testing and a culture that tolerates long-lived bugs unless they generate public backlash.

Trust, lock-in & alternatives

• Many no longer trust Apple Photos/iCloud as the sole repository for irreplaceable images, despite paying for iCloud tiers; they emphasize owning flat files and independent backups.
• Some keep Photos only as a front-end viewer and manage masters with open-source tools on local or self-hosted storage.
• A few downplay risk, noting years of trouble-free imports from other brands, suggesting the bug might be rare or source-specific.

Miscellaneous

• Several commenters find the “tenderlovemaking.com” domain amusing or problematic for work filters, sparking a side discussion about quirky tech-site names.

How BB(5) Was Determined

• Direct “run them all and see” is impossible because you can’t in general detect non-halting by brute force.
• The search space of 5-state Turing machines was first reduced using Tree Normal Form, from ~1.7×10¹³ raw machines to ~1.8×10⁸ “essentially different” ones (reachable states canonically ordered, symmetries reduced).
• Machines were then passed through a pipeline of deciders:
  • Simple loop detection (“loops”) plus short simulations handled the vast majority.
  • More sophisticated abstract-interpretation deciders (NGram CPS, RepWL, FAR, WFAR) proved non-halting for almost all remaining machines by over-approximating reachable configurations and showing none can reach a halting state.
  • Only 13 “sporadic” machines needed bespoke, hand-crafted non-halting proofs.
• The longest halting machine runs for 47,176,870 steps, establishing BB(5).

---

Brute Force vs Uncomputability

• Commenters stress that the Busy Beaver function as a whole is uncomputable, but specific small values (like BB(5)) can still be determined with enough structure and proof.
• There is no universal algorithm deciding halting for all Turing machines (halting problem), but for any fixed finite class (e.g., up to 5 states) a specialized decider can exist.
• Some argue that, in a broad sense, this is still “brute force”: enumerate machines and proofs within a formal system; others reply that the key work is in designing powerful deciders and proof strategies, not naive enumeration.

---

Limits of Proving Busy Beaver Values

• For any fixed, sound, recursively axiomatizable theory, there exists some N beyond which that theory cannot prove exact BB(N) values; this is a Busy-Beaver-flavored incompleteness phenomenon.
• One view: there is no absolute N beyond which BB(N) is unknowable “in principle”; you can always strengthen your axioms. Another view emphasizes that for every such theory, independence eventually occurs.
• Known results (cited in the thread) show certain large BB(k) values (e.g., around k≈745) are already independent of ZFC; the suspected “practical” barrier might be much smaller, possibly even low double digits.

---

Proof Assistants and Rocq

• All deciders and sporadic proofs were formalized in the Rocq (Coq) proof assistant.
• This ensures the full BB(5) classification is machine-checked: deciders are proved correct with respect to mathematical Turing machines, then applied to the entire search space.
• Verifying the resulting proof takes under an hour on a multi-core laptop; the exploratory search and development of deciders took far more computational and human effort.
• There is discussion of alternative assistants (e.g., Lean, Dafny), and of this work as part of a broader trend toward formalized, collaborative mathematics.

---

Online Collaboration and Related Communities

• The project is highlighted as a large, distributed, internet-native collaboration, closer to “formalized research” than distributed number-crunching.
• Comparisons are made to:
  • Classic distributed projects (DES/RSA challenges, distributed.net), whose original goals are now largely historical.
  • Modern formal-math collaborations in Lean using proof “blueprints”.
  • Niche online communities around Conway’s Game of Life and “googology” (very large numbers).

---

Implications and Practical Value

• Most participants see this as highly theoretical, with no direct applied payoff; benefits lie in:
  • Sharpened methods for reasoning about program behavior and partial halting-problem “taming” (e.g., static-analysis techniques, abstract interpretation).
  • Stress-testing and improving proof assistants and libraries.
  • Deepening understanding of the limits of formal systems and computability.
• Some push back on the idea of “purely useless” math, citing historical cases where seemingly abstract work later became foundational (e.g., number theory, Hardy’s work).
• Others characterize the achievement as more of a heroic, intricate classification effort than a new conceptual breakthrough—still “beautiful” and inspiring.

---

Connections to Collatz and BB(6)

• The 5-state champion is described (elsewhere, and referenced here) as computing a Collatz-like process; commenters note similar behavior in candidate 6-state “Antihydra” machines.
• This raises the idea that Collatz-style dynamics are a good blueprint for constructing long but terminating computations.
• BB(6) is discussed only via bounds and scale:
  • Published lower bounds already involve mind-boggling fast-growing constructions (towers/Knuth arrows repeated enormous numbers of times).
  • An exact BB(6) is believed far beyond what can be written down or feasibly proved, even if not yet formally ruled out.

Mass surveillance vs. crime prevention

• Many argue Chat Control is primarily mass surveillance, not a serious tool to catch criminals.
• Others say the intent is crime-fighting, but the effect is disproportionate: scanning everyone to find a tiny fraction of offenders.
• Statistical arguments highlight that, even with optimistic assumptions, false positives would massively outnumber true positives, overwhelming police and harming innocents.

False positives, classifiers, and real-world harm

• Some note you can tune detection systems to reduce false positives, but others counter that real deployments consistently err on the side of over-reporting.
• Examples are cited where automated CSAM detection flagged benign family or medical photos, nearly resulting in prosecutions.

From targeted wiretaps to permanent mass scanning

• Critics stress that traditional wiretaps required probable cause, court orders, were labor-intensive, and not retroactive.
• Chat Control is framed as “wiretapping everyone all the time,” automated, proactive, and capable of creating long-lived records.
• Breaking or bypassing end-to-end encryption is seen as introducing major security and economic risks.

Authoritarian drift and historical context

• German history (Third Reich, Stasi) is invoked as a warning; some express disbelief Germany is not leading opposition.
• Others argue that such powers will inevitably be used on everyone, and can easily be repurposed for political repression or “wrongthink.”

EU law, constitutions, and fundamental rights

• Debate over whether EU law can override national constitutions and privacy guarantees is intense and unresolved in the thread.
• The EU Charter’s privacy rights are noted as having broad law-enforcement carve‑outs, prompting doubts about their real protective value.

Democracy, accountability, and repeated pushes

• Many see repeated attempts to pass similar measures as “p‑hacking democracy” — keep trying until it passes.
• Others respond that politicians are elected and this is therefore formally democratic; if people cared, they’d vote differently.
• There’s frustration with the European Commission’s agenda-setting role and the difficulty of “voting out” key actors.

Country roles and precedents

• Denmark is repeatedly mentioned as a strong proponent; Germany’s wavering is seen as decisive for the Council blocking minority.
• The UK’s Online Safety Act is cited as a functional analogue: scanning is already law there, only paused as “not yet technically feasible.”

Proposal details and double standards

• A proposed exemption for state, military, and law‑enforcement accounts is viewed as a red flag: if the system is so safe, why exclude those most sensitive users?
• This is taken as evidence of both insecurity (new attack surface) and expectation of false positives that would be intolerable for officials.
• Limited 6‑month retention of flagged material is still seen as a dangerous “paper trail,” especially in future political turmoil.

Effectiveness and easy circumvention

• Many point out that serious criminals can trivially evade scanning (alternative apps, custom tools, extra encryption layers, encrypted archives).
• The likely outcome, in this view: ordinary citizens are surveilled; sophisticated offenders move elsewhere.

Broader surveillance‑state pessimism and EU skepticism

• Some believe the surveillance state is now inevitable, driven by both governments and large tech platforms.
• The controversy fuels rising Euroscepticism and even calls for exiting the EU, though others counter that without the EU, such laws might spread even faster at national level.

Responsibility: Companies vs Volunteers

• Strong disagreement over whether “the companies” or unpaid OSS maintainers are to blame.
• One camp argues Fortune 500s freely exploit volunteer work, giving little back beyond demands.
• Others counter that permissive licenses are effectively donations; using them as allowed isn’t “leeching,” and maintainers chose that model.
• Some say commercial users should at least be prepared to maintain, fork, or pay for support if they rely on a dependency.

Corporate Incentives and Contribution

• Several stories of companies informally promising OSS contributions for years but never funding them; OSS work is seen as “no time in the budget.”
• Others note many OSS contributors are actually paid employees (e.g., major languages, foundations); but there’s a very long tail of small critical libraries run by volunteers.
• Debate on whether corporate accounting and invoicing constraints really make funding volunteers “legally hard,” or if that’s just an excuse.

Licensing, Fairness, and “Leeches”

• Dispute over whether it’s fair to morally criticize big companies that profit heavily from MIT/BSD code without giving back.
• One side: permissive licensing implies you expect nothing; fairness arguments don’t change that.
• Other side: legality ≠ fairness; people naturally see it as bad manners to profit massively from someone’s work with zero reciprocity.
• Long subthread on non‑standard “not for big corps” licenses and whether they should still be called “open source” (strong pushback citing OSI definition).

NPM Culture and Ecosystem vs Others

• Multiple comments: the real problem is JS/NPM culture—huge dependency trees, micropackages, aggressive auto‑upgrades, weak standard library.
• Comparisons to Go, Maven, PyPI, crates.io, RubyGems:
  • Fewer tiny packages, better stdlibs, no postinstall, explicit upgrade commands, or signed packages (Ruby, PyPI).
  • Go’s “lowest compatible version” strategy praised for limiting surprise upgrades.
• Some argue NPM is simply a bigger, juicier target; others say its design and defaults are uniquely dangerous.

Technical Root Causes and Platform Issues

• Discussion on the web as a hostile app platform vs just “learn your tools better.”
• UI components (date pickers, accessible widgets) cited as reasons for heavy dependency use.
• Hardware security (TPM/Secure Enclave, secure boot) seen by some as unrelated; others say they’re mostly DRM tools, not a fix for NPM‑style attacks.

Mitigations and Best Practices (Today)

• Practical suggestions:
  • Use pnpm (disables most postinstall scripts by default, minimum‑age for new releases).
  • Use Renovate (or similar) with “cooldown” windows before adopting new versions.
  • Pin exact versions, rely on lockfiles, use npm ci, avoid auto‑updates; some vendoring and manual diff review on updates.
  • Sandbox package managers (bubblewrap on Linux, sandbox‑exec on macOS) or develop inside VMs/containers with secrets kept outside.
  • Generate SBOMs and track with tools like OWASP Dependency-Track; use npm audit and external scanners (e.g., safe‑chain).
• Recognized downsides: dialog fatigue, usability friction, impracticality of manually reviewing hundreds/thousands of transitive deps.

What NPM/Microsoft Could or Should Do

• Strong criticism that package signing/verification was requested as early as 2013 and effectively ignored for years.
• Others respond that NPM now has Trusted Publishing, provenance/attestations, and 2FA for top packages; claims that “nothing has been done” are disputed.
• Proposed platform‑level measures:
  • Mandatory (or much broader) phishing‑resistant 2FA (hardware/WebAuthn) for popular packages, possibly with cooldowns after credential changes.
  • Require code signing and treat stolen tokens differently from stolen signing keys.
  • Built‑in malware scanning of new releases with human review queues and “cooldown” for high‑impact packages.
  • Better default token scoping, expiry, and tooling to derive minimal permissions.

Broader Security Model

• Some argue endless arms‑race defenses are doomed; suggest “web of trust” style vouching, where third parties (including big companies) sign attestations that they’ve inspected specific versions and found no obvious malice.
• Others emphasize sandboxing and OS‑level isolation as the long‑term way to make inevitable supply‑chain compromises less catastrophic.

China’s Nvidia Ban and Strategic Signaling

• Commenters link the Alibaba chip news to China reportedly ordering tech firms to cancel Nvidia AI chip purchases.
• Interpreted as both:
  • A push to force investment into domestic hardware and non‑CUDA software stacks.
  • A nationalist / trade‑war move to stop funding foreign (including Taiwanese) defense and economies.
• Some note this changes the risk calculus inside Chinese firms: reliability of supply now outweighs historical distrust of domestic quality.

Alibaba’s Chip and China’s Hardware Position

• Thread consensus: Alibaba’s chip is roughly in A100/H20 class, ~one to two generations behind top Nvidia Blackwell parts, but still highly useful.
• Several argue Chinese chips don’t need to beat Nvidia’s best—only the restricted, cut‑down export models.
• Reports of DeepSeek struggling with Huawei chips show the ecosystem is still immature, but demand and margins create powerful incentives to fix issues.
• Some call the article/state narrative propaganda, pointing to missing details on interconnect and real compute; others see it as early but meaningful progress.

CUDA, Software Moats, and AMD

• Repeated theme: Nvidia’s dominance is more about ecosystem (CUDA, tools, familiarity) than unique silicon.
• In China, political pressure can “break” the CUDA moat by forcing migration; firms are building CUDA‑compatible or translated stacks.
• AMD is viewed as technically competitive (Instinct line, ROCm) but hampered by weaker software, drivers, and lack of aggressive ecosystem building; demand is limited by Nvidia’s lock‑in and TSMC capacity.
• Some argue the CUDA moat is overstated for deep‑learning inference (mostly matmuls), but others stress full‑stack training performance and tooling still heavily favor Nvidia.

Export Controls, Incentives, and Catch‑Up Dynamics

• Many frame US export bans as effectively subsidizing Chinese chip development by guaranteeing a captive domestic market and strong state backing.
• Debate over how much this really accelerates innovation: some say “catch‑up would happen anyway but faster now,” others note many sanctioned states never caught up due to weaker institutions.
• System‑level strategies matter: China can compensate for weaker single chips with sheer scale, cheaper power, advanced packaging, and networking.

AI Race, Markets, and AGI

• Some see even a short delay in Chinese AI capability as a major strategic win for US national security; others think delays are only “a few years” and not decisive.
• There is skepticism about AGI imminence and about an AI investment bubble; yet most agree Nvidia’s margins and dominance will attract more competitors, including Chinese vendors, hyperscalers’ custom chips, and service‑centric models.

Asus ACPI Bug and User Impact

• Discussion centers on a long‑standing ACPI firmware bug in Asus gaming laptops that causes periodic 10–30ms latency spikes, visible as UI stutter and audio crackle.
• Several owners of Zephyrus G14/G15 and other ROG models report nearly identical symptoms under both Windows and Linux, reinforcing that the issue is BIOS/ACPI, not OS.
• Some note it appears worst in “dGPU‑only/Ultimate” MUX mode, but others say latency problems show up more broadly, so the exact scope remains unclear.
• Workarounds people use: avoiding dGPU‑only mode, disabling boost, favoring hibernate over sleep, or effectively sidelining the dGPU.

Laptop Firmware and ACPI Dysfunction Across Brands

• Many commenters generalize the problem to modern laptops: Lenovo, Dell, HP, MSI, Surface, Clevo, Acer, and others are all cited with ACPI, power, GPU switching, sleep/wake and dock issues.
• Switchable graphics (iGPU+dGPU) are repeatedly described as fragile, especially with Thunderbolt/docks. Several users now avoid them entirely or choose iGPU‑only machines.
• There’s frustration that years of BIOS updates often “improve performance and security” on paper while never fixing core bugs.

Apple, Steam Deck, and Alternatives

• Some contrast this with MacBooks and the Steam Deck, saying their suspend/wake and overall integration are far more reliable.
• Others push back, listing Apple hardware and software failures (keyboards, throttling, audio glitches, monitor issues) to argue no vendor is flawless—Apple just has the unified incentive to fix its own stack.

Debugging, ACPI Patching, and Technical Debates

• The community is impressed by the author’s reverse‑engineering of AML and ACPI events; several say this is exactly the quality of work OEMs should be doing.
• People discuss overriding ACPI tables on Linux (initrd/DSDT override) and Windows (Microsoft ACPI table load APIs, custom bootloaders), but note signing, anti‑cheat, and bricking risks.
• One detailed commenter questions whether “sleep in an interrupt” is the true root cause, suggesting that System Management Mode and poorly designed GPU power transitions may dominate the latency.

LLMs and Trust in Technical Writing

• Multiple readers say the article’s prose is obviously LLM‑polished and find the style distracting or untrustworthy, worrying that generation may have mangled nuances.
• Others argue using an LLM for wording—especially for non‑native writers—is fine if the technical content and logs are verifiable, and that critics should point to concrete errors instead.

QA, Reviews, and Buying Advice

• Commenters are baffled that such a blatant four‑year bug escaped Asus QA and wasn’t flagged by major reviewers, who typically test throughput but not latency.
• There’s broad cynicism that consumer laptop firms prioritize marketing over engineering, expect users to accept glitches, and rarely respond meaningfully to deep technical bug reports.
• Many advise avoiding gaming laptops or Nvidia‑based switchable graphics entirely, favoring Macs, business‑line laptops, open‑friendly vendors (System76, Framework), or a desktop + Steam Deck combo instead.

Nostalgia & Legacy

• Many recall Midnight Commander (MC) as the spiritual successor to Norton Commander, alongside Volkov, FAR, Dos Navigator, XTree/PathMinder, etc.
• Several describe it as a “gateway drug” from DOS to Linux in the mid‑90s and are pleasantly surprised it’s still maintained in 2025.
• Some share war stories: recovering accidentally rm -rf’d dissertations on ext2 by browsing unlinked inodes via MC.

Current Use Cases

• Still a default install for many on servers, NAS devices, and remote shells; often the “secret weapon” on headless systems.
• Used on macOS (via Homebrew), Windows (including WSL), Unraid, and in containers; some even hook it into Kubernetes debug workflows.
• Common tasks: bulk file moves, SCP/FTP/SFTP over SSH or mounted remote FS, source-tree review (with “Lynx-like motion” + quick view), and simple editing via mcedit.

Features People Value

• Dual-pane navigation, keyboard-centric workflow, and history/bookmarks for fast directory jumps.
• Tight shell integration: Ctrl+O to drop to a shell in the current dir, Ctrl+X bindings, and an editable F2 user menu for custom multi-file actions (e.g., rsync, ffmpeg pipelines).
• Virtual FS support (FTP/SFTP/SSH URLs), background transfers, overwrite strategies, and an easy, approachable editor.

Keyboard, Ergonomics & “Old-School” Debates

• Strong muscle-memory from the original F-key and numpad layout; others find MC’s shortcuts unintuitive if they never used Norton Commander.
• Complaints about Tab being “stolen” from shell completion, Escape delays via terminal emulators, and configuration (colors, formats) being trial‑and‑error.
• Some want vim-style keybindings; MC now supports alternative keymaps (including vim/emacs examples).

Orthodox File Manager Concept

• Discussion around why these are called “Orthodox File Managers”: dual-pane, command-driven UIs where visible actions map to underlying commands.
• Long thread on the meaning of “orthodox” in Russian, English, and Greek and whether the term was organic or a “forced meme.”

Alternatives, Comparisons & Criticism

• Frequent comparisons to Total Commander, FAR/far2l, Krusader, Double Commander, ranger, nnn, yazi, Dired, Dolphin, Marta, Directory Opus, etc.
• Some say MC feels dated, lacks more advanced/parallel copy features, or is in “maintenance mode.”
• Others argue graphical file managers or pure shell tools are enough and question why OFMs still inspire such devotion.

Attention, Incentives, and “Recommendation Media”

• Several comments frame attention as a de facto currency: likes, views, shares, and followers function like money without any “central bank.”
• For‑profit platforms are seen as inevitably drifting toward engagement‑maximizing recommendation feeds, regardless of initial mission.
• Some argue you can have healthy for‑profit social media only if the “attention economy” is either demonetized or tightly regulated/re‑monetized with limits on how much attention can be given/received.

Regulation vs Personal Responsibility

• Many see meaningful reform as impossible without government intervention (e.g., bans on recommender feeds, restrictions on non‑personal accounts, school smartphone bans).
• Others object to paternalism, preferring education and parental responsibility, but are challenged that unpriced social harms justify regulation.
• Comparisons are drawn to newspaper regulation and libel law; some argue platforms shouldn’t be allowed to broadcast anything at scale with zero liability.

Desired Properties of Slow Social Media

• Common wishes:
  • Chronological feeds with a hard end (no infinite scroll).
  • Small, private groups; invite‑only or mutual following.
  • Caps on friends/followers and on posts per day; possibly mandatory “cost” in time or friction per post.
  • No or hidden like counts; limited or disabled forwarding; comments opt‑in.
• Some want to outlaw or severely limit algorithmic feeds and commercial/brand accounts, though others note that would kill mainstream appeal.

Existing and Historical Alternatives

• Many say the article is reinventing or echoing: LiveJournal, Tumblr, Path, Friendster, early Facebook, regional networks (e.g., iWiW, Tuenti), phpBB forums, BBSes.
• Current “slow” substitutes cited: WhatsApp/Signal/Telegram groups, iMessage and shared photo albums, Discord servers, Goodreads, Strava, BeReal, Slowly, niche fediverse platforms (Mastodon, Lemmy, Friendica), and experimental projects (Minus, Seven39, Peergos, Haven, micro.blog, mood.site, tootik, twtxt).
• A recurring pattern: services that embody these ideas either remain small, drift toward engagement features, or die when they fail to scale.

Network Effects, Protocols, and Small Federations

• Many emphasize network effects and distrust after Facebook/Twitter/Reddit as the main blockers; people won’t move where their friends aren’t.
• Open protocols (XMPP, Matrix, nostr, fediverse) are promoted as solutions, but criticized for UX friction and lack of critical mass; big companies have strong incentives to keep ecosystems closed.
• Some foresee a future of many small, private, possibly AI‑assisted networks tailored to families, clubs, or communities rather than one dominant global feed.

Weak Ties and Parasocial Concerns

• There is disagreement over following distant acquaintances: some value passive updates for rekindling or contextualizing relationships; others see it as parasocial voyeurism that displaces real interaction and fuels unhealthy comparison.
• Several note a cultural shift: normal people share less publicly; influencers and semi‑professionals dominate, while private group chats now carry most “real” social life.

Evolutionary / “other-loop” methods

• Several commenters see the approach as similar to evolutionary systems (e.g., AlphaEvolve): text prompts define a high-level search space, and “genetic” mixing plus selection explores it.
• This is framed as part of a broader trend: recent strong models reportedly use heavy “outer loop” search/verification beyond simple single-pass generation.
• A key open problem: how to define good fitness functions for prompt/program evolution without hand-crafted human scoring; naive attempts stall quickly.

Scaffolding, self-scaffolding, and ASTs

• Many argue LLMs are helpless on complex, multi-step tasks without rich scaffolding; models themselves are flexible but the scaffolds are brittle.
• Proposed direction: “scaffolding synthesis” where one agent designs task-specific scaffolding (plans, tools, state machines, ASTs), then another agent executes it, with feedback to refine the scaffold.
• Examples include compiling natural-language instructions or legal documents into AST-like structures, and existing tools (e.g., code+plan modes) are cited as early instances.

LLM weaknesses: memory, spatial reasoning, and vision

• Empirical reports: models perform badly on Sokoban-like puzzles, nonograms, mazes, and ARC-style tasks—forgetting rules they previously derived and repeating disproven deductions.
• Some attribute this mainly to poor long-range memory and reliance on lossy text context; others stress weak spatial/visual reasoning and current “bag-of-vision-tokens” frontends.
• There is debate whether vision or memory is the primary blocker; multiple comments insist models need compact internal, non-verbal representations of rules and state.

ARC-AGI’s role and modality issues

• Several see ARC-AGI as primarily a visual benchmark where humans have strong innate preprocessing; if puzzles were given as JSON, most people would first transform them into graphics.
• Others note that strong computer-vision modules exist but haven’t yet produced very high ARC-AGI scores when bolted onto LLMs.
• Some view this work as meaningful progress on one of the few benchmarks where humans still dominate; others think it’s “slightly smarter brute force” or overfitting to a contrived task.

Reasoning vs pattern matching and “PhD-level” claims

• Long subthread debates whether LLMs genuinely “reason” or just perform sophisticated pattern matching.
• One side argues: high benchmark scores, commonsense examples, and mech‑interp findings (latent world models, abstract circuits) imply functionally similar reasoning to humans, albeit text- and 1D-biased.
• The opposing side stresses failures on simple puzzles, out-of-domain tasks, lack of runtime learning, and reliance on offline RL as signs they are closer to expert systems trained to the test.
• Definitions are contested: some equate reasoning with advanced pattern matching; others insist true human-like reasoning must include continual learning and generalization to genuinely novel problems.

Dead zones, RL, and learning over time

• The article’s notion of “dead reasoning zones” is challenged; critics say humans do exhibit systematic reasoning failures, especially in abductive inference or under cognitive dissonance.
• Questions are raised about the claim that RL “forces logical consistency”; skeptics note that repeated trial-and-error with an oracle differs from humans’ one-shot reasoning and self-checking.
• Several point out that LLMs could, in principle, approximate runtime learning via external memory plus periodic fine-tuning on their own experience, but this is not how today’s models generally operate.

Practical tools, reproducibility, and evaluation

• Commenters share related frameworks (e.g., dSPY, GEPA-like approaches) and ask for reusable tools to run evolutionary prompt/program search at home with major APIs.
• Links to the project’s GitHub and Kaggle notebooks are provided for replication.
• Some worry that apparent improvements on public puzzles might just reflect training on blog posts or leaked solutions; others suggest controlled tests with pre‑ARC models and ablations of the new method.

Longevity and Support of iOS vs Android

• Many see this iOS 15.8.5 patch as evidence that Apple supports devices far longer than most Android OEMs, especially pre‑2020 Pixels and Samsungs that often got ~3 years.
• Others note Android has improved: recent Pixels and Samsungs now promise 5–7 years of updates, sometimes matching or surpassing Apple’s formal commitments (at least on paper).
• Experiences with hardware durability diverge: some report Android phones failing faster than iPhones; others report decade‑scale use of Samsung/Pixel devices while iPhones around them get replaced frequently.

Severity and Nature of the Vulnerability

• Commenters infer a serious zero‑click remote code execution in image parsing, likely exploited via messaging apps.
• It was already patched on “current” devices weeks earlier; this backport to iOS 15 is taken as a strong signal it was used in real‑world spyware campaigns.
• Several speculate it’s part of a chain with a WhatsApp bug to deploy targeted surveillance tools, potentially similar to commercial spyware.

Threat Models and Old Devices

• Some argue this mostly matters to journalists, activists, opposition figures, and others targeted by states; everyday users face much lower risk.
• Others counter that once such exploits are reverse‑engineered, they can spread to less sophisticated actors, so patching old devices limits broader abuse.
• Debate over whether high‑risk people can “just buy” a newer phone; several point out many such targets are not wealthy.

Repurposing and Openness

• Discussion on whether old iPhones are less reusable than old Androids:
  • iOS: jailbreaks, TrollStore, and Xcode sideloading exist but are constrained and fragile over time.
  • Android: LineageOS and postmarketOS can turn devices into routers, servers, etc., but support varies by model and vendor unlock policies.
• Some argue that if iPhones were as hackable as cheap microcontrollers, they’d be better long‑term dev platforms.

Vendors, SoC Constraints, and Policy Shifts

• A recurring criticism of Android: baseband/SoC vendors (notably Qualcomm) stop maintaining kernel/driver trees after a few years, capping secure support even for custom ROMs.
• Others respond this is ultimately a contractual and business‑model problem Google and OEMs could solve if they chose.
• Apple’s tighter vertical integration is seen as enabling longer practical support.

App Ecosystem and Practical Lifespan

• Even with security patches, some note that once iOS is two major versions behind, many apps drop support, making devices “functionally obsolete.”
• Counterexamples: users on very old iPhones report core tasks (browser, navigation, banking, Apple Pay) still working, though some sites and apps have already moved on.

Overall Reaction to Apple’s Patch

• Broad approval for patching 9–10‑year‑old devices; several self‑described non‑fans praise it compared to Android “abandonware.”
• Some worry that patching only this one bug on an old branch may give users a false impression that they’re fully secure when many other unfixed issues likely remain.

IP, DMCA, and Copying Boundaries

• Many commenters suggest DMCA takedowns for plagiarized text, images, and origin story; expectation is Apple will often remove blatant copies but not all.
• General consensus: copying the idea or simple functionality is fair game; copying marketing copy, assets, or decompiled code crosses a line.
• Some note legal recourse is impractical across borders and for low-revenue indie utilities.

What Can Be a Moat for a Simple Utility?

• Idea itself is not defensible; for a small Mac utility, suggested “moats” include:
  • Speed of innovation and frequent updates.
  • Better UX, native feel, and responsive support.
  • Building a brand and community trust over time.
  • Sheer stamina: keep maintaining while quick-buck clones decay.
• Others argue there may be no real moat for something that can be built in days; marketing and distribution dominate.

App Store, Distribution, and Clones

• Several argue that using the App Store means relying on Apple’s “moat”; curation is described as weak, random, or driven by volume/revenue rather than quality.
• Some criticize the 30% fee vs poor enforcement against obvious clones and spam.
• Suggestions include multi-cloning one’s own app with variations, direct distribution, and cautious use of Reddit and similar channels (avoid “I made $X in Y days” posts that attract copiers).

LLMs, Low Barriers, and Authenticity

• Multiple comments say LLMs have drastically lowered the bar to clone simple apps or marketing pages, intensifying an old problem.
• Broader unease emerges about AI-generated code, AI-written posts, and whether the thread itself is partly “vibe-coded,” raising questions about authenticity of both software and discussion.
• Some frame widespread cloning as a long-standing human behavior now amplified by new tools.

Air quality measurements while cooking

• The article’s low PM2.5 numbers from frying eggs contrast with many commenters’ experiences using various monitors and purifiers.
• Several report PM2.5 going from low single digits to 70–400 µg/m³ when searing meat or burning oil, and to device max (500–999+) when frying bacon, pancetta, or badly overheating oil.
• Some air purifiers react strongly to cooking from other floors of the house, ramping to full power within a minute.
• Others note that gentle cooking (e.g., eggs not heavily browned) often doesn’t move the needle much.

Role of oil, heat, and browning

• Multiple commenters stress that the test scenario is “too clean”: low heat, little browning, and apparently not much oil.
• High heat, Maillard browning, and approaching or exceeding oil smoke point are repeatedly cited as the main drivers of PM2.5 spikes.
• Tiny burnt fragments or a brief oil overheat can generate disproportionate particulate levels compared to non-burnt cooking.
• Some note extensive grease deposition on high surfaces and inside hoods as evidence of significant aerosolized oil.

Gas vs electric / induction

• There’s agreement that gas combustion worsens indoor air quality, but disagreement about particles: some say gas adds mostly NO₂, CO₂, CO, and VOCs, not PM2.5.
• Induction/electric avoids combustion gases but still produces particulates from food and oil.
• A few anecdotes describe modern apartments with unvented gas ranges causing CO alarms.

Ventilation, hoods, and kitchen design

• Many extractor fans (especially over-the-range microwaves) merely recirculate air through weak filters and move relatively little air compared with proper external vents.
• Even externally vented hoods are often underpowered or constrained by poor ducting and lack of makeup air, so they dilute slowly rather than rapidly clearing spikes.
• Strong praise for enclosed, Chinese-style kitchens with powerful exterior vents; critics of open-plan Western layouts complain of “whole-house cooking smells” and lingering grease.
• Others value open kitchens for social reasons and accept some spread of odors.

Nonstick pans, PFAS, and tradeoffs

• Some prefer avoiding nonstick/PFAS and accept short pollution spikes plus filtration instead.
• Others argue that intact PTFE at non-smoking temperatures is likely low-risk for the user; the larger concern is PFAS pollution from manufacturing.
• Many use oil even on nonstick for better heat transfer, browning, and flavor.

Sensor limits and composition

• Commenters note that PM sensors report size, not chemistry; oil droplets, tire dust, and metal particles are likely to differ greatly in toxicity.
• Several point out that cooking generates ultrafine particles smaller than 2.5 µm that common PM2.5 sensors may miss.

Crash cause and reproducibility

• Several commenters are skeptical until they see an independent reproduction, noting the port is for PocketPC with no code snippet shared.
• Debate over whether the crash was due to the game or the OS: some argue the OS error dialog suggests a system-level failure; others point out the article explicitly attributes it to a game-engine counter overflowing, so any OS would see the same crash.
• One commenter dissects the description (a counter compared to its previous value) and notes that alone shouldn’t obviously crash, suggesting more detail is needed; they also note that Doom’s core tick rate (35 Hz) doesn’t neatly match the ~2.5-year 32-bit overflow timeframe, which raises questions.

Tiny hosting stack and HN “hug of death”

• The original forum runs on extremely constrained hardware (reported as 32 MB RAM, even an IP camera), which impressed many, especially given how slow tools like Jira feel by comparison.
• The site struggled to load for many due to Hacker News traffic; the operator later reported about 1,500 concurrent users exhausted RAM and caused restarts, but it recovered.
• Some find the minimalist, fast setup admirable; others joke about it being run on a router or disposable vape.

Time overflows and 2038/NTP concerns

• The Doom bug triggers a broader discussion of 32‑bit time counters and the 2038 problem.
• People highlight that 2038 feels much closer than Y2K did, and that many embedded or closed-source systems may fail unless moved to 64‑bit time.
• NTP’s 2036 era rollover is mentioned; correct implementations should handle it, but many cheap devices may not.

Game timer glitches and design intent

• Commenters supply similar examples: Crash Bandicoot’s timer overflowing after ~2.26 years, Final Fantasy IX’s two‑year wraparound used to obtain a late-game weapon, and long‑horizon glitches in titles like Paper Mario.
• There’s discussion of how, in the 32‑bit era, assuming no one runs a game continuously for years was reasonable, given design lifetimes and hardware constraints.
• Some frame this as analogous to engineering for a finite “design life” rather than indefinite reliability.

C integer overflow and undefined behavior

• Several comments dig into C semantics: signed overflow is undefined behavior, unsigned is well-defined wraparound.
• They speculate that incorrect assumptions about a monotonically increasing counter, combined with UB or unchecked cases (e.g., unexpected comparison results, division by zero, bad indices), could cause deterministic crashes even on different platforms.

Doom, modern FPS design, and ownership

• Many express enduring affection for classic Doom and Doom 2016, while criticizing more arena‑style, “hub‑based” modern shooters.
• There’s mention of “boomer shooters” as a genre recapturing classic, linear, run‑and‑gun gameplay.
• Side discussion notes that Doom and many other historic PC franchises now belong to Microsoft, prompting debate about how much of PC gaming they effectively control.

Historical uptime bugs and test horizons

• A Windows NT 4 uptime bug (~49 days) is recalled as a similar timer overflow issue that forced scheduled reboots on servers.
• Several remark that running any modern stack or game cleanly for 2.5 years is itself remarkable, and far beyond what most testing cycles ever cover.

Oracle as TikTok Owner (Tone: Mockery + Schadenfreude)

• Many find Oracle owning TikTok inherently funny and deeply mismatched (“Yahoo buys Tumblr” vibes).
• Widespread hope that Oracle’s culture, licensing mentality, and “enterprise” mindset will ruin the product and effectively kill TikTok in the US.
• Numerous jokes about Oracle-style licenses, Java rewrites, and aggressive compliance/audit behavior applied to end users.

Why People Dislike TikTok (Product, Brainrot, and China)

• Strong current of “TikTok is pure brain rot” and should die along with Instagram Reels and YouTube Shorts.
• Others note that Reels/Shorts only exist because TikTok pioneered the format; hating the originator more than clones is seen as reasonable.
• A key distinction for some is foreign state control: they tolerate Meta/Google manipulation because it’s domestically regulatable; they fear latent CCP influence over political narratives, especially via geographic/demographic targeting.
• Skeptics argue TikTok’s behavior is not clearly worse than US platforms; they see mostly geo-based recommendations and little hard evidence of unique malice.

Deal Structure and “Great Firewall of America”

• Summary of reported deal:
  • New US-only TikTok app, separate content graph and users.
  • ~80% owned by US investor consortium (Oracle, Silver Lake, a16z), ~20% ByteDance.
  • US data hosted on Oracle in US; initial algorithm licensed, later reimplemented to comply with law.
  • Board includes one US government–appointed director.
• Many see this as de facto nationalization plus vendor lock-in: forced divestiture, mandated Oracle infra, and direct state presence on the board.
• Repeated comparison to China’s model: party/state seats on boards, domestic clones, and national firewalls; talk of a coming “Great Firewall of America.”

Media Power, Propaganda, and Fascism Concerns

• Intense worry about Trump-aligned billionaires (Oracle leadership, VC backers) consolidating control of TikTok plus major legacy media (Paramount/CBS, possible Warner/CNN).
• Several frame this as the next phase of a US “oligarch + state” project: state capitalism/fascist playbook, propaganda alignment on Israel/Palestine and Gaza, and tighter control over youth discourse.
• Others argue both parties enabled this: Trump initiated TikTok pressure, a bipartisan Congress passed the latest law, Biden signed it; now Trump’s administration is leveraging it.

Free Speech, Surveillance, and Which Government You Fear More

• Government-appointed board seat widely read as a political commissar to steer moderation and amplification.
• Some see US control as strictly worse for them personally: US agencies can prosecute, deny visas, or weaponize centralized datasets; China cannot.
• Others argue the core issue is not data but “controlling the message” and that US elites simply want the same speech control tools China uses.

Global Split and Future of Short-Form Video

• Concern that US users and content will be siloed from the rest of the world; some non-US commenters welcome less exposure to US culture wars.
• Debate over whether a US-only “OracleTok” can retain creators and users, or whether people will route around via VPNs or abandon it for other platforms.
• Underneath everything is a broad critique of short-form video as maximally addictive, low-information, and misinformation-prone, regardless of who owns TikTok.

Modern C++ Safety and Footguns

• Some argue “modern C++” (smart pointers, STL, sanitizers, contracts) has significantly reduced traditional footguns.
• Others counter that new features (capturing lambdas, string_view, iterator invalidation, std::array without bounds checks) introduce fresh, subtle lifetime and memory hazards.
• Debate over std::array and unchecked operator[] becomes a proxy for priorities: compatibility/perf vs. safety-by-default. Contracts in C++26 are viewed as both welcome and comically late.
• Several note that in C/C++, warnings must be treated as errors; tools (sanitizers, static analyzers) are essential, not optional.

Rust vs. C++ (Performance, Safety, and DX)

• Strong disagreement with the article’s claim that Rust is only a “small part” of improved safety in C++→Rust rewrites. Many state memory safety is exactly where Rust shines and that “just rewriting” in any language does not explain the observed reduction in bugs.
• Some C++ users prefer “performance and stability” and complain about Rust’s fast evolution and breaking ecosystem. Others report the opposite: Rust’s compiler and ecosystem feel more stable and technically “excellent” than their C++ tooling.
• Consensus that Rust and C++ are broadly similar in raw performance, with Rust gaining advantages over time as it can evolve ABI and safety without legacy constraints.

Tooling, Build Systems, and Package Management

• Big fault line: C++’s fragmented build and dependency story (make/CMake/autotools/Conan/vcpkg/pkg-config/system package managers) vs. “one-command” experiences like Cargo/Gradle.
• Some defend Unix-style “many small tools” and system package managers as a feature (curation, flexibility, offline builds, distro integration).
• Others call this Stockholm syndrome: non‑portable build scripts, version conflicts, and “build engineers” maintaining fragile C++ builds are seen as a serious productivity and onboarding cost.
• Mixed views on vcpkg/Conan/CMake+find_package; CMake is widely acknowledged as de facto, but not loved.

Complexity, Readability, and Language Design

• Many argue you cannot safely ignore “advanced” C++: move semantics, templates, operator overloading, undefined behavior, and initialization rules leak into everyday code via the standard library.
• Others advocate a “C-with-RAII” subset: minimal templates, limited overloading, heavy use of STL containers, RAII, and smart pointers; but acknowledge team members will often use more exotic features anyway.
• C++ is described as “arcane” and “monumental”; memes about its iceberg of complexity resonate. Developer experience (slow compiles, cryptic template errors, header/ABI issues) is a recurring complaint.

Legacy, Domains, and Future Trajectory

• Broad agreement that C++ (and C) will remain entrenched for decades in OSes, game engines, embedded and high‑performance systems; rewrites are costly and risky.
• For new projects, many commenters strongly favor Rust or higher-level languages unless there is a clear need for C++’s specific ecosystem or cross‑platform reach.
• Some see C++ evolving into a “COBOL/Fortran of systems” role: important but shrinking for greenfield work, with safety and DX expectations moving elsewhere.

Article reception and style

• Several readers found the piece clickbait-y: it recounts historical drainage schemes but notes no serious current effort, making the titular question feel irrelevant.
• Multiple comments say it closely tracks the Wikipedia article on Everglades drainage; some would rather have read Wikipedia directly.
• Others enjoyed the humor and narration, while a few felt the jokes and tone were “off” or AI-like.
• Betteridge’s law (“any headline that ends in a question mark…”) is invoked as obviously applying here.

Historical context vs present-day debate

• Discussion notes that large-scale drainage was a live issue in the late 19th and early 20th centuries, including early US elections, but is not a mainstream proposal now.
• Past drainage attempts (e.g., dikes around Lake Okeechobee) are debated: the article portrays them as failures; commenters argue they did “work” in surviving major hurricanes, though not perfectly regulating floods/droughts.

Ecology and experience of the Everglades

• Many stress the Everglades’ uniqueness and value as a “river of grass” and complex mosaic of ecosystems, where tiny elevation changes radically shift habitat types.
• Firsthand accounts describe canoeing, camping, birds, dolphins, manatees, fish, and mangroves building land—presented as far richer than a caricature of just “gators and snakes.”
• Multiple comments call the Everglades an irreplaceable national treasure that should be preserved, with unsustainable development not a valid excuse to drain it.

Safety, predators, and public perception

• Some express fear of alligators, crocodiles, and leeches; others argue gators are generally timid around humans and that biting insects are a bigger nuisance.
• Colorful stories recount swimming and skiing alongside gators, and the broader point that true “wilderness” includes creatures that might eat you.
• Jokes suggest dropping would-be drainers into the swamp to gain “appreciation,” contrasted with concern about introducing “invasive species” (i.e., those people).

Draining wetlands: benefits, harms, and precedents

• One thread notes that historically, draining wetlands sometimes reduced malaria (e.g., parts of Italy, France’s Landes), providing real human benefits.
• Others counter that large-scale hydrological engineering often has severe, long-run consequences:
  • Examples: Central Valley irrigation depleting aquifers and causing land subsidence; Mississippi River levees and control structures creating ecological and flood-risk problems; Mexico City and other drained wetlands.
  • Argument: humanity repeatedly underestimates complexity of such systems; “Chesterton’s fence” is invoked as a reason not to radically alter ecosystems we don’t fully understand.
• Dissenters respond that these same projects also enabled massive increases in agricultural productivity and human wealth; they see critics as ignoring successes and human needs.

Climate change, sea level rise, and Florida development

• Multiple comments argue that sea-level rise may “finish” the Everglades and threaten South Florida generally.
• There is frustration at ongoing dense coastal development just a few meters above sea level despite foreseeable flooding, saltwater intrusion, and eventual desalination needs.
• The Dutch are cited as the only people “trusted” to fundamentally reshape wetlands; others note Florida’s porous geology and hurricane risk make Dutch-style solutions much harder and costlier.

Philosophical views on nature’s purpose

• One camp emphasizes that nature does not exist for human comfort or safety; the Everglades’ value is independent of human aesthetic preferences.
• Another maintains that, practically, humans will and should prioritize what benefits people and “animals that are good for humans.”
• A subthread challenges the idea that nature “exists for us,” especially from an atheistic perspective, but others argue that “existing for” is itself a human construct.

Why the Leak Matters / Context about the Blog

• Some initially question why a leaked video of Meta’s Ray‑Ban glasses using Lumus waveguides is newsworthy.
• Others explain the blogger is a long‑time AR/VR display specialist whose detailed teardowns are widely followed in the industry, so even a small leak from them is notable for AR tech watchers.
• Technically, this is interesting because it reveals a consumer product using a relatively advanced waveguide display approach that hasn’t been common in mass‑market glasses.

Meta Ray‑Ban Glasses and “Success” Debate

• Commenters note Meta’s current Ray‑Ban glasses (audio/camera only) have reportedly sold ~2M units; some call this “extremely successful for a new form factor,” especially compared with failed or tiny‑volume competitors (Spectacles, Echo Frames, Google Glass, Humane Pin, etc.).
• Others argue 2M units is small given Meta’s scale and marketing reach; they see the product as niche, not a breakout hit.
• Disagreement over what counts as “new form factor” (vs. smartphones, Vision Pro, other AR devices).

Trust in Meta and Platform Concerns

• Multiple users say they won’t buy any Meta‑controlled hardware regardless of how good the optics are, citing past behavior around data collection and privacy.
• Some expect Meta will use glasses to harvest rich labeled data about people and environments, eventually apologize after abuses, and treat fines as a cost of doing business.

Privacy, Surveillance, and Face Recognition

• Many worry that mainstream AR glasses will normalize pervasive recording and face recognition: instant dossiers on people you see, always‑on life‑logging, and ad‑targeting based on everything you look at.
• Some hope that a shocking “mirror” of what’s possible (e.g., an app that auto‑identifies everyone) might trigger a privacy backlash; others call this naive and predict further normalization and erosion of privacy.
• Fears include:
  • No meaningful way to “opt out” of being scanned in public.
  • AR‑only interfaces making daily life hard without glasses (analogous to app‑only services today).
  • Data being sold widely and used for profiling by corporations and governments.
• Proposed defensive ideas: IR LED “jammers,” legal restrictions (e.g., EU‑style regulation), or just social stigma against visible AR hardware—though many expect the hardware will soon look like normal glasses.

Will AR Glasses Ever Be Mainstream?

• One camp is convinced AR glasses will never be everyday mainstream:
  • They don’t clearly solve problems that phones don’t.
  • Voice/gesture UIs are awkward; touchscreens are cheap and efficient.
  • Battery life and power demands are significant constraints.
• Others argue they will become common, driven by:
  • Navigation overlays, translated text, in‑situ knowledge, HUD‑style info.
  • Entertainment and large “virtual displays” for laptops/phones (e.g., using current Xreal‑type devices on planes or in bed).
  • The advertising industry’s desire for a continuous, immersive ad channel.

Use Cases and Niche Value

• Suggested useful scenarios:
  • Real‑time translation overlays, directions, and HUD minimaps.
  • Virtual big displays for productivity when traveling or in cramped spaces.
  • Accessibility or cognitive aids (e.g., remembering names/faces), though some note this feels socially “creepy” despite its benefits.
  • Professional HUD‑style applications (aviation, EMS, trucking, ATC, law enforcement, military) seen as more realistic near‑term markets.

Technology and Design Notes

• Some see the Lumus‑style waveguide as an interesting evolution, reminiscent of earlier “wedge display” concepts.
• Battery, weight, display sharpness, and device durability remain seen as major blockers for all‑day consumer AR.
• Offhand ideas include visualizing RF fields via AR for diagnostic/technical work.

General Sentiment

• Strong technical curiosity about the optics and form factor.
• Equally strong distrust of Meta’s intentions and pessimism about privacy.
• Divided views on whether AR glasses represent the “next smartphone” or a perpetual niche with impressive demos but limited real‑world demand.