Hacker News, Distilled

Video & “Newly Found” Works

• Several commenters note that the video has a long intro; the actual performance starts around 15 minutes in, with timestamp links shared.
• It’s clarified that the pieces were not “recently found” as works, but rather that the novelty is the new attribution to Bach.
• Some who listened to the new works found them underwhelming compared to later Bach, describing them as early, less interesting pieces, akin to demos or outtakes.

Bach’s Greatness & Influence

• Many participants call Bach one of the greatest composers, even “perhaps the greatest artist,” stressing his fusion of complexity, structure, and emotional depth.
• Others push back on absolutist claims, arguing that art is subjective and that “greatest” across all art forms and cultures is essentially meaningless.

How to Approach Bach & Recommended Works

• Suggested “entry points” include cello suites, lute works, violin partitas and sonatas, organ pieces (Passacaglia & Fugue, trio sonatas, Toccata and Fugue), choral works (cantatas, St Matthew Passion, Mass in B minor), and the Well-Tempered Clavier and fugues.
• Specific movements (e.g., “Mache dich, mein Herze,” “Jesu, Joy of Man’s Desiring,” various arias) are highlighted as emotionally direct.
• Several recommend particular performers and recordings, including historically informed and modern instrumental interpretations.

Complexity, Intellect, and Emotion

• Fans praise Bach’s ability to encode extreme contrapuntal and harmonic complexity (e.g., palindromic canons, wide-ranging modulations) while remaining expressive and often spiritually intense.
• One thread compares this positively to “complexity” in software, noting that Bach’s complexity is economical and purposeful, unlike unnecessary complexity in code.

Comparisons & Critiques

• Some commenters find Bach emotionally “cold” or “mathematical” and prefer Romantic or other composers (e.g., Mozart, Saint-Saëns), arguing that Bach’s impact can be overstated.
• Others argue that his catalog’s scale, consistency, and influence are nearly unmatched, while also acknowledging that personal enjoyment is separate from technical greatness.
• Debates arise over Mozart’s depth vs. catchiness, Bach’s supposed elitism or “nepo baby” status, and whether complexity equals superiority.

History, Loss, and Culture

• Side discussions cover lesser-known contemporaries (e.g., Zelenka), the loss of many works (notably in WWII), and broader cultural damage from Nazism and the Holocaust.
• Commenters generalize from this to the fragility of media (including films) and how destroyed or lost works shape what we now consider “the canon.”

North Korean war narrative & status of the peninsula

• Several commenters dispute the article’s claim that North Korea insists the whole peninsula “has remained united” under its rule.
• Described prevailing view: both Koreas see the war as ongoing, each claiming to be the sole legitimate government for the entire peninsula, while recognizing a hostile rival controls the other half.
• North Korea’s recent constitutional change explicitly calling South Korea a “hostile state” is cited as evidence they recognize it as a separate state de facto.
• Comparisons are drawn to PRC/ROC (China–Taiwan) dual claims and to both Koreas teaching the “country” as the entire peninsula while not accepting the other’s legitimacy.

Propaganda, doublethink, and authoritarian parallels

• Commenters invoke “1984” and “doublethink” to explain how people can live with obvious contradictions when dissent is punished.
• One view: most citizens know official narratives are wrong but avoid drawing explicit consequences to stay safe.
• Parallels are drawn to Soviet practices, modern US partisan media, and general patterns of authoritarian loyalty tests and “purity spirals.”

Map design, rail focus, and technical oddities

• The atlas appears heavily rail-centric: red lines often match railways, sometimes obscure or long-closed ones, but with many omissions and inaccuracies.
• Some maps seem decades out of date; others mix rail and major roads in confusing ways.
• There are puzzling features like a nonexistent Polish river and rail in Iceland, suggesting bad data rather than deliberate “copyright traps.”
• Centering the world map on the Pacific is defended as standard in East Asia and Australia, not evidence of special narcissism.

Disputed territories and Israel/Palestine

• The atlas reflects geopolitical stances: Palestine labeled as occupied, Western Sahara and other disputes highlighted; Arunachal Pradesh and Kashmir shown in non‑Indian ways.
• Israel is reportedly treated as “nonexistent,” which commenters tie to an anti‑imperialist, pro‑Palestinian line and broader Cold War–era alignments.

Humanitarian situation and intervention

• Commenters discuss North Koreans’ suffering but argue that military intervention risks massive civilian casualties and great‑power war, so outsiders largely tolerate the status quo.

Interest in the encyclopedia artifact

• Multiple readers express strong interest in a full CD image of the atlas/encyclopedia, seeing it as a rare window into North Korean state world‑view and priorities.

Article/source discussion

• Some objected to using Microsoft’s own blog, viewing it as a corporate press release with little technical detail; preference expressed for independent reporting that adds research and context.
• Others note the article is very short and light on data (no traffic samples, limited attack breakdown), which fuels skepticism about “record” framing and marketing motives.

Residential proxies, VPNs, and abuse

• One line of discussion argues for banning commercial “residential proxy” businesses designed to evade blocks, while not outlawing personal VPN/home access.
• Many push back hard: such bans are seen as unworkable, bad for privacy, and easily conflated with cracking down on legitimate VPN usage in an increasingly authoritarian world.
• Clarification from some: many “residential proxy” services are actually built atop IoT/router botnets selling compromised devices as exit nodes.

IoT insecurity and auto-updates

• Broad agreement that IoT (routers, cameras) is a major DDoS substrate; “wave after wave” of insecure devices.
• A specific claim: compromise of a router vendor’s forced-update infrastructure (partly driven by EU “timely updates” requirements) added ~100k devices to Aisuru, showing the risk of centralized, mandatory update channels.
• Debate whether such laws reduce overall risk (by forcing patching and penalizing vendors) or just centralize failure and incentivize sloppy remote-update mechanisms.

Responsibility: users, vendors, ISPs

• Personal “secure your devices” is viewed as non-scalable; many argue manufacturers/distributors should be legally responsible for shipping and maintaining secure firmware.
• Some want ISPs to quarantine infected customers, notify them, and/or block traffic. Others note ISPs have little economic incentive and would incur support costs and customer churn.
• Examples are given of ISPs already quarantining compromised routers in some countries, but questions are raised about usability and fairness.

Mitigation mechanisms and network design

• Network engineers in the thread reference RTBH, Flowspec, and anti-spoofing as existing but underused tools to squelch attacks near origin; political/economic will is seen as the bottleneck.
• Source spoofing is discussed: Microsoft’s blog claims “minimal spoofing,” and some note modern anti-spoofing is widespread but still incomplete.
• IPv4 + CGNAT complicates IP-based blocking and attribution. Advocates argue widespread IPv6 would allow more precise, persistent blocking of individual endpoints or prefixes; critics note managing hundreds of thousands of block entries and dynamic assignments remains challenging.

Open-source firmware and supply chain security

• Concern is raised that open-source router firmware projects (e.g., OpenWRT) also have attractive update/build infrastructure that could be compromised.
• Others counter that vendor servers are already being compromised, and open projects at least use signed firmware, reproducible builds, and more community scrutiny.
• Discussion extends into build reproducibility, bootstrappable toolchains, and the difficulty of truly offline, verifiable builds even in open source.

Aisuru botnet, Azure impact, and Cloudflare

• Aisuru is described as a Mirai-family IoT botnet, now also renting itself as “residential proxies.” The Azure attack used ~500k IPs, ~15 Tbps, and lasted ~40 seconds, targeting one Australian endpoint.
• Some suspect the short, high-volume burst is essentially an advertisement: “look what our botnet can do” to future DDoS-for-hire customers.
• Reported impact on Azure was negligible; some commenters joke that Azure is slow enough normally that extra load is unnoticed.
• Multiple people note ironic contemporaneous outages at Cloudflare and difficulty reaching the article itself, reigniting concerns about Internet centralization around a few large DDoS “scrubbing” providers.

Motives and economics of DDoS

• A large subthread explores why DDoS exists at all:
  • Extortion/protection rackets (“pay or we keep you down”).
  • Gaming-related pettiness and coercion (revenge for bans, sabotaging tournaments, forcing players from competitor servers).
  • Market manipulation: gaming economies, gambling/e-sports betting, private MMO servers, and paid cosmetics economies.
  • “Free trial” or marketing runs for DDoS-for-hire services (short, fixed-duration blasts).
• Some note that massive, random attacks against cloud endpoints may serve to obscure more targeted operations by hiding signal in noise.

Law enforcement and global governance

• Several ask why there isn’t an effective international cyber law-enforcement body that can “remove bad actors.”
• Responses emphasize:
  • Jurisdictional limits and sovereignty: states won’t accept foreign agents arresting their citizens.
  • Political incentives: some states benefit from offensive cyber activity and won’t cooperate.
  • Analogy to existing bodies (UN, anti-trafficking, etc.): they mitigate but don’t eliminate crime and are constrained by funding, corruption, and politics.
• Some fear any strong global cyber police would drift toward identity-linked IPs and censorship; others argue some coordinated mechanism to pressure ISPs and vendors is still better than today’s “wild west.”

Evidence-Based Charity & “$5k per Life” Claims

• Several commenters highlight empirical work (e.g., charity evaluators, RCTs) suggesting certain global-health charities can avert a death for a few thousand dollars.
• Direct cash transfers to people in extreme poverty are widely praised as simple, low-overhead, and demonstrably beneficial.
• Some note that evaluators benchmark programs against cash; only options that outperform “just give cash” are recommended.
• Others stress that harder-to-measure work (infrastructure, research, policy) can still be valuable even if it resists RCT-style evaluation.

Overhead, Self-Perpetuation, and Organizational Drift

• There is concern that almost any large organization drifts toward self-preservation and bloat, including NGOs and health insurers.
• Debates arise about “overhead” vs. impact: fundraising and admin can be necessary, but can also become rent-seeking or reputation-laundering.
• Some see standard charity-rating approaches as crude (focusing on admin ratios) and regard EA-style impact analysis as a genuine improvement.

Moral Foundations: Utilitarianism, Longtermism & “Ends Justify Means”

• Supporters frame EA as two claims: we can significantly help others, and some ways help far more than others.
• Critics argue EA, especially in its longtermist and tech-centric forms, easily slides into “ends justify the means,” enabling rationalizations for harmful behavior (fraud, exploitation, eugenics talk, AI utopianism).
• Others counter that core EA writings explicitly reject harming people even for large expected benefits.
• There’s extensive discussion on consequentialism vs virtue ethics: some say “be a good person” is safer than trying to compute global utility; others see virtue ethics as “open-loop” and needing outcome checks.

Wealth, Power, and Bad Actors

• Many see EA as attractive to very rich, morally questionable people who want to justify extreme wealth or delay giving (“earn to give later”).
• Defenders reply that notorious donors are an unrepresentative minority, and most EA-aligned people are ordinary donors trying to be more helpful.
• There are broader arguments about whether extreme wealth is inherently exploitative, and whether philanthropy distracts from systemic fixes like taxation and public programs.

Local Help vs Global Optimization & Branding Problems

• Some argue real altruism should focus on direct, local relationships; EA’s distant, optimized giving feels cold, elitist, or anti-human.
• Others respond that local mutual aid cannot address massive preventable deaths abroad; ignoring global cost-effectiveness leaves many to die.
• Multiple commenters distinguish “effective altruism the practice” (thinking hard about impact) from “EA the movement/brand,” which they see as politically and reputationally damaged.

Cost and AWS NAT Gateway vs self-hosted

• Many argue AWS NAT Gateway is “ridiculously expensive,” especially per‑GB traffic, compared to running a small EC2 NAT instance (iptables/nftables, Debian, OpenWrt, OPNsense, fck‑nat, etc.).
• Some note AWS’ official NAT AMIs are based on very old Amazon Linux; others confirm the same configuration works fine on modern distros like Debian or Rocky Linux.
• One claim: attaching an Elastic IP to a NAT instance causes hairpinning through AWS public infrastructure and adds regional data transfer charges; others are skeptical and ask for documentation.

Operational tradeoffs & business context

• Pro‑cloud side: managed NAT is “set and forget,” publishes metrics, and avoids hiring specialists or owning lifecycle/patching, PCI, and hardware retirement. For many businesses, saving engineering focus and launching faster is worth higher recurring cost.
• Pro‑self‑hosting side: for high‑traffic workloads, the per‑GB savings are “massive,” turning a big variable cost into a small fixed one. Some emphasize that basic Linux networking is easy enough that paying AWS premiums feels wasteful.

NAT, firewalls, and security misconceptions

• Multiple comments stress: NAT is not a firewall. The protection comes from stateful filtering, not address translation. You can have NAT without real isolation and firewalls without NAT.
• Concern that conflating NAT with security has made people afraid of IPv6, thinking RFC1918 space is “safe” by itself. Others reply that typical home routers already behave as stateful firewalls for both v4 and v6.

IPv6 vs IPv4 and “do away with NAT”

• Some want NAT gone entirely, arguing IPv6 + firewalls (or AWS egress‑only IPv6 gateways) can eliminate NAT fees and hacks like port forwarding and split‑horizon DNS.
• Others counter: IPv4 is still dominant, many AWS services and external platforms lack full IPv6 support, and ISP practices (dynamic prefixes, limited /64s, even IPv6‑behind‑NAT) complicate pure‑IPv6 designs.
• Aesthetic/usability objections to IPv6 syntax come up; several replies note that humans should be using DNS anyway.

Skills, culture, and AI

• One thread laments that modern developers avoid networking/sysadmin as “hard,” relying on managed services instead, and worries about long‑term expertise.
• Others respond that specialization is rational; devs can and do choose not to learn low‑level Linux/networking, and AI tools may both lower the bar for self‑hosting and filter out less capable practitioners.

Alternative setups & tips

• Suggestions include: DIY EC2 NAT instances with IP forwarding and iptables; turning off source/dest check; avoiding EIPs unless needed; using VPS + SSH/OpenVPN tunnels with Nginx; or using Tailscale/headscale.
• One commenter warns that simple NAT recipes don’t address kernel hardening (ICMP redirects, source routing, rp_filter, syncookies, etc.) and recommends security review before production use.

Android bloatware and setup experience

• Several commenters describe cheap Android (often Samsung/carrier-locked) phones as effectively unusable during initial setup: hours of updates, unwanted app installs, intrusive prompts, and dark patterns.
• Even premium Samsung devices are said to ship with aggressive promotions (Bixby, “Global Goals”, app recommendations) and persistent reinstalling of removed apps after updates.
• In contrast, Pixels, some Motorolas, Fairphone, and older “Android One” devices are cited as relatively clean; iPhones are seen as cleaner too, though with their own Apple-first “bloat” bundle.

Economic incentives and responsibility

• One view: low device prices are subsidized by preloaded apps, data harvesting, and ads; carriers and OEMs are paid to ship “crapware,” leading to a race to the bottom.
• Another view: hardware is cheaper mainly due to economies of scale; advertising/data revenue is “gravy,” not a real consumer subsidy.
• Some argue this is corporate greed more than necessary economics; others note consumers actively choose “cheaper but full of crap” carrier deals.

What AppCloud does, and where

• AppCloud is reported to push unsolicited app promotions and remotely install apps, bypassing normal consent and some security checks; several label this spyware, not mere bloatware.
• Initially described as limited to Africa/Asia/MENA, users report finding and removing AppCloud (via adb) on Samsung phones in the US and at least one EU case, contradicting the article’s geographic scope.

Israeli origin and geopolitical concerns

• Part of the controversy is legal: some countries bar Israeli companies; preloading Israeli-origin software could breach local boycott/anti-normalization laws.
• Others see the focus on “Israeli-founded” as politicized or “Israel bad” framing, especially since the company is now owned by a US firm and ties between AppCloud and ironSource/Aura are unclear.
• Counterpoint: given Israel’s well-known offensive cyber ecosystem, state alignment is a legitimate threat model for states hostile or wary of Israel—analogous to concerns over Chinese or Russian vendors.
• Some note that much global tech (chips, R&D centers, cloud components) already has Israeli contributions, making pure avoidance unrealistic, but distinguish that from remotely controlled ad/spy modules.

Responses, workarounds, and trust

• Suggested mitigations: buy unlocked phones, avoid Samsung/carrier models, prefer Pixels (optionally with custom ROMs like GrapheneOS), or avoid Android altogether.
• There are calls for regulation mandating a clean baseline OS and banning remote installers.
• Broader worries surface about ubiquitous “spy apps,” surveillance capitalism, and the difficulty of achieving genuinely open, verifiable, secure consumer systems.

Shopping Cart as Moral Litmus Test

• Many commenters endorse the “shopping cart theory”: returning a cart is an easy, unenforced “right thing,” so failing to do it signals selfishness or unfitness for a high‑trust society.
• Some extend this: how you behave on bad days (rain, kids screaming, tired) is the real test of character and values.
• Others generalize to “small acts” like littering, facing products, holding subway doors, queuing in traffic, or how you treat waitstaff.

Counterarguments & Practical Excuses

• Several people argue it’s a poor moral test: parents juggling small children, disabled people using carts as mobility aids, or those having a terrible day may reasonably skip the extra walk.
• Some ex‑grocery employees say they liked doing cart duty as a break from indoor drudgery, so abandoned carts weren’t clearly harmful from their perspective.
• A minority explicitly admit they don’t return carts, sometimes framing it as harmless, trivial, or “not my problem.”

Impact on Others & the Commons

• Many emphasize concrete harms: carts denting cars, blocking parking spots (including disability spaces), creating hazards in wind or storms, and making lots look chaotic.
• This is often framed as a “what if everyone did this?” or broken‑windows/tragedy‑of‑the‑commons problem; conscientious minorities are seen as “holding the world together.”
• Some people pick up stray carts on the way in specifically to “leave the world slightly better.”

Culture, Design, and Incentives

• Commenters contrast US behavior with Europe and Japan, where carts are more consistently returned and coin‑deposit systems are common.
• Others note huge US parking lots and sparse corrals can make returns a multi‑minute walk, changing the calculus.
• Coin deposits are seen both as effective nudges and as turning a social norm into a transactional “I’m paying not to return it” arrangement.

Employees, Jobs, and “Job Creation” Rationalizations

• “They’re paid to do it” and “I’m creating jobs” are widely criticized as broken‑window fallacies: extra cleanup work ultimately raises costs or worsens conditions.
• Some ex‑employees counter that more stray carts did make their shifts easier or more pleasant in practice.

Cart Narcs & Public Shaming

• The article’s reliance on Cart Narcs videos is attacked for heavy selection bias.
• Many dislike the vigilante, filmed-confrontation style, seeing it as harassment, especially of people with invisible disabilities, and symptomatic of low social trust.

Direct-sales bans and dealer power

• Commenters ask why manufacturers are barred from selling directly in most states.
• Explanations given: mid‑20th‑century franchise laws to protect dealers from being undercut by manufacturers; desire to ensure local service/parts at a time when logistics were weaker; and heavy regulatory capture by politically powerful local dealers.
• Some frame this as “protecting local labor” and town keystone businesses, analogous to anti‑offshoring protections.
• Others argue the laws are now mostly rent-seeking by dealers, not consumer protection.

Tesla, service control, and right-to-repair

• Tesla is cited as an example of direct sales plus tight control over repairs and parts.
• Complaints: restrictions on third‑party/used parts, difficulty for independent mechanics, and supply‑side suppression of a third‑party parts market.
• Counterpoints: Tesla does sell many parts and publishes manuals/diagnostic software, but access can be costly.
• Broad agreement that right‑to‑repair legislation would be a better consumer safeguard than protecting dealerships.

Vertical integration debate

• One view: vertical integration tends to be bad for competition and can let firms lock up parts and distribution.
• Counterview: vertical integration can improve quality and reduce dependence on volatile supply chains, and does not inherently imply monopoly.
• Some nuance: larger players benefit more from vertical integration, which can reinforce dominance even if it doesn’t cause it.

Dealers vs online platforms

• Strong dislike of in‑person dealership haggling and upselling; some welcome anything that reduces contact with salespeople.
• Others value in‑person inspection and same‑day mechanic checks, especially for used cars.
• Experiences with Carvana/Shift/Cinch vary: praised for hassle‑free buying and return windows, but criticized for quality issues, pushy financing, and post‑sale problems.

Amazon’s role and incentives

• Many note Amazon is just a lead generator/front end; the local Ford dealer still delivers, adds options, and handles warranty.
• Speculation that Amazon’s main motive is advertising revenue in a lucrative auto market.
• Some doubt Amazon can profitably ensure thorough inspection and support on used cars; others note traditional used dealers manage this, though often with lower standards.

“Pre-owned” language and trust

• Debate over “pre‑owned” vs “used”: some see it as harmless euphemism, others as deceptive corpspeak exploiting negative connotations of “used.”
• Confusion over whether “pre‑owned” implies “certified” and extra warranty; several emphasize that “certified pre‑owned” is a distinct category and the details matter.

Name Collisions and Project Naming

• Many comments focus on “Gemini overload”: Google’s AI, this protocol, and other uses make the word ambiguous.
• Several note this protocol predates Google’s LLM (started ~2019), so blame is split on who is “cluttering” search results.
• Broader gripe: tech naming in general is uncreative, collisions are inevitable, and big companies dominate name meaning (“Amazon” example).
• Tangent discussion on internal codenames, boring vs whimsical names, and the perennial difficulty of “naming things.”

What Gemini Is and How It Works

• Described as “modernized Gopher” or “a radically stripped down web stack.”
• Technically: a client sends a one-line textual request over TLS; the server returns a MIME-typed response or error, then closes the connection.
• Gemtext is a very simple, line‑based hypertext format, roughly like minimal Markdown; easy to implement and render nearly statelessly.
• Positioned between Gopher and the Web in complexity: heavier than Gopher, lighter than HTTP/HTML.

Philosophy and Appeal

• Core goals: simplicity, privacy, non‑extensibility, and defense against the modern web’s bloat, tracking, and JS-heavy pages.
• Fans enjoy “smallweb” vibes: cozy, low‑noise reading, often via desktop clients like Lagrange; some run gemlogs, social-style services, and even a Gemini “Wayback Machine.”
• The separate protocol acts as a gatekeeper: only people strongly motivated by minimalism and privacy tend to show up.

Discovery and Ecosystem

• Discovery works via search engines, directories, feed aggregators, and webring-like linking between “capsules.”
• There are multiple clients and servers, some HTTP proxies, and search/crawl projects indexing thousands of hosts and ~1M documents.

Design Choices and Controversies

• Strong restrictions: mandatory TLS, no inline images or embedded media, no inline links, no styling, no file size or range requests.
• Supporters say the value is in what you can’t do: no JS, no tracking pixels, trivially simple rendering, predictable UX across sites.
• Critics argue these constraints are “stupid by today’s needs,” make art and rich documents awkward, and limit adoption; several wish for HTML 2/4 + no JS instead.
• There is tension over clients that add optional features (favicons, auto-fetching images); some call this spec-violating, others see it as practical.
• Some complain about the per-request TLS handshake overhead and lack of connection reuse.

Critiques of Messaging and Broader Context

• Multiple readers say the front-page 100‑word intro is vague motivational fluff that doesn’t clearly convey “it’s a protocol + text format.”
• Broader lament about the modern web: browsers becoming “publishers’ agents,” DRM in HTML, erosion of user control, and speculation about attested, locked‑down future clients.
• For some, Gemini is a nostalgic, principled refuge; for others, it’s an unnecessary NIH reimplementation that Gopher or “simple HTML” already covered.

XSLT deprecation: usage, impact, and backward‑compatibility

• Many commenters see XSLT-in-browser as niche and “dead”; others show concrete uses: RSS/Atom and podcast feeds, sitemap and government/regulatory sites, XML-based hobby sites, IoT devices exposing XML+XSLT, document/report viewers, and simple templating for non‑programmers.
• A recurring argument: even if usage is small, the web’s “contract” was that standards-based content would keep working indefinitely. Removing a standard feature is viewed as a precedent that erodes trust.
• Others counter that backward compatibility itself has a cost; if a feature’s usage is tiny, removing it can be justified.

Security, maintenance, and cost–benefit

• Pro‑removal side: libxslt is old C code, a frequent source of security reports, and expensive to maintain; the maintainer quit under unpaid bugfix pressure. Keeping unused, complex code increases attack surface.
• Critics respond that “security” is overstated or misused: XSLT has memory‑safe implementations and could be sandboxed or shipped as a WebAssembly/JS polyfill bundled with the browser, largely eliminating native-risk without breaking sites.
• Disagreement over process: some feel Chrome pushed “intent to remove” and code changes before properly quantifying usage or understanding key cases (e.g., podcast feeds), contrary to Google’s own deprecation guidelines.

Comparisons with other web features

• Opponents note XSLT’s usage is reportedly higher than various newer hardware APIs (WebUSB, WebSerial, MIDI, WebTransport) that browsers are eager to add and keep; they see inconsistency in invoking “low usage” only for older XML tech.
• Defenders reply these APIs can’t be polyfilled and enable genuinely new capabilities (device setup, education, debugging), whereas XSLT transformations can be done on servers or in JS.
• FTP and Gopher removals are cited as precedent. Some argue they were more widely used than XSLT but still rightly removed; others say FTP never got a proper successor for directory‑style browsing.

Standards process and Google’s influence

• Several stress that removal was proposed within WHATWG with support from Mozilla and Apple; it’s not purely a unilateral Google move.
• Nonetheless, Google’s dominance and its speed in landing Chromium patches make people see this as symptomatic of a browser‑vendor‑driven web, where implementor convenience outweighs user and author needs.
• There is concern about Chrome moving to a partial Rust XML parser, seen by some as a signal that even standards‑compliant XML support may shrink.

Alternatives, polyfills, and RSS/Atom usability

• Multiple people suggest that RSS/Atom feeds could be made friendly with JS and CSS embedded in XHTML namespaces, or via JS XSLT polyfills.
• Critics argue that:
  • This breaks “truly static” sites and very constrained devices.
  • It forces authors to learn more complex JS instead of simple declarative templates.
  • It degrades the experience for non‑technical users who click feed links and see raw XML.
• Some propose that browsers should instead offer first‑class, built‑in RSS/Atom rendering, which would obviate XSLT here, but they doubt such support will materialize.

Broader “open web” and philosophy debate

• One camp: removing XSLT is a routine pruning of obsolete complexity and narrows the API surface, which can even help new engines like Ladybird.
• Another: it exemplifies a shift from the web as a durable document network toward a brittle, app‑delivery platform optimized for ads, telemetry, and proprietary ecosystems, with backward compatibility and user control treated as secondary.

Perceived Forecast Accuracy & Consumer Experience

• Several commenters say Google’s consumer forecasts (Search, Pixel, default Android weather) have become noticeably worse in the last 6–12 months, with temperature off by a few degrees or rain predictions clearly wrong.
• Others report consistently good results from national services (e.g., Norway, US NWS) or apps like Windy, yr.no, and some niche apps.
• A recurring theme: forecasts have objectively improved over decades (linked long‑term statistics), but users still experience jarring local failures, especially for precipitation and in complex microclimates.

Ensembles, Uncertainty, and Metrics (CRPS)

• Multiple comments explain that modern forecasting is fundamentally probabilistic: an ensemble of scenarios is run, and “chance of rain” reflects the fraction and spatial coverage of rainy members.
• Some users want a single “best” forecast; others strongly value explicit uncertainty/variance.
• WeatherNext 2’s emphasis on many scenarios and CRPS loss is discussed:
  • CRPS encourages sharp, well‑spread probabilistic forecasts, countering the blurring and loss of extremes seen with L2 losses.
  • Noise-driven ensembles (applied to inputs or parameters) plus CRPS help generate diverse but calibrated members without heavy post‑processing.
  • This is framed as a major technical advance versus earlier neural weather models and generative approaches.

Comparison with Traditional NWP Models

• Several commenters insist the key benchmark is accuracy vs major physics-based models (GFS, ECMWF, ICON), not speed. They note the article gives limited direct skill comparisons.
• There’s praise for Google’s recent hurricane track performance and criticism that US GFS has had a poor hurricane year.
• Some meteorology-savvy participants argue that, in this stack, WeatherNext still relies on ECMWF analyses, so it doesn’t yet close the loop with observation targeting or new data assimilation techniques.

High-Resolution & Specialized Use Cases

• Energy market participants need 5–15 minute forecasts for load and renewable generation; they describe using regional high‑resolution models like HRRR and custom NWP runs.
• Other specialized needs (e.g., structural engineering wind gust statistics, wildfire or severe thunderstorm behavior) often require reanalyses, regional models, or bespoke simulations; commenters doubt generic AI models yet excel here.

Data Sources, Integration, and Access

• Discussion of smartphone barometer data: historically proposed, but commenters note privacy, quality-control, and limited benefit; WeatherNext 2 does not use such data.
• WeatherNext 2 outputs are available via Earth Engine, BigQuery, Vertex AI, and are being integrated into Search, Gemini, Pixel Weather, and Maps/Maps Weather API; no dedicated consumer “WeatherNext” app exists.

History and pharmacology of stimulants

• Commenters note that substituted amphetamines and related phenethylamines (meth, MDMA, 2C-x, cathinones, etc.) have been around since the 1930s–50s and were researched for depression and what became ADHD.
• Stimulants were widely used in WWII by multiple militaries (“go pills”), and still see limited use (e.g., Dexedrine, modafinil) in modern forces.
• There’s debate over Adderall’s chemistry: some emphasize it’s just mixed amphetamine isomers and salts, not a “substituted amphetamine” like MDMA or meth.

Huxley, Soma, and fictional drugs

• Many initially confuse the article’s topic with Brave New World’s “soma,” then clarify that the linked Huxley lecture instead imagines a side-effect-free focus/attention drug.
• Discussion over what soma most resembles pharmacologically (weed, benzos, opiates, MDMA-lite) leads to broader debate on how cannabis and MDMA actually feel and function.

ADHD, Adderall, and stigma

• A large subthread pushes back hard on the framing “Adderall increases mental efficiency.”
• ADHD commenters stress that for them Adderall primarily reduces executive dysfunction (starting tasks, following through, managing daily life), not IQ or general “efficiency.”
• They highlight severe untreated-ADHD outcomes: shorter lifespan, high depression and suicide rates, rejection sensitivity, and emotional dysregulation.
• Several describe life-changing benefits from Adderall, atomoxetine, or modafinil, and object to framing these medications as shortcuts or productivity hacks. Misconceptions are seen as fueling stigma and diversion, making access harder for those who need them.

Therapy vs medication

• Disagreement over behavioral therapy: some say it “does nothing” for ADHD; others cite guidelines and CBT studies showing moderate benefits, especially combined with medication.
• Nuanced view: therapy doesn’t fix core neurobiology but can help with acceptance, coping strategies, and guilt; it’s complementary rather than an alternative to meds.

Cognitive enhancement, abuse, and safety

• Several argue Adderall does not make non-ADHD people smarter and may even reduce performance while increasing the feeling of productivity.
• Others point to historic and military use of stimulants for endurance and boring tasks, suggesting real (if narrow) performance gains.
• Debate over addiction and “wear and tear”: some call amphetamines safe and low-risk at prescribed doses; others note dependence potential, strong side effects, and misuse in academia.

Corporate structure and secrecy

• Commenters are surprised a company raising $6.2B can remain so opaque (unclear start date, location, staff).
• Several explain U.S. structures: corporations/LLCs must exist in state records, but private firms disclose minimal ownership or operational details; Delaware and some other states expose almost nothing publicly.
• Sole proprietorships and some partnerships can operate with almost no registration, but that’s seen as unlikely for a multi‑billion‑dollar vehicle.
• Speculation that this entity is buried under layers of holding companies and possibly using a code name, making it effectively untraceable to outsiders.

Scale and nature of the funding

• Some see $6.2B as potentially circular: money flowing from Amazon-related interests to the startup and back via AWS or chip purchases.
• Others suggest similar circular deals are widespread in the current AI boom, inflating apparent spend and valuations, though there’s disagreement about how extreme this is.
• A few wonder if this is partly an “experiment in AI financing” designed to multiply capital on paper without much real deployment.

AI productivity, jobs, and the bubble question

• One thread claims concrete evidence of reduced hiring in AI‑susceptible roles (content writing, front‑end dev), with an anecdote about replacing a front‑end developer using AI coding tools.
• Others push back: correlation with weaker hiring doesn’t prove AI causation; some roles might simply be easy to consolidate or were “non‑essential” already.
• There’s debate over whether AI tools really increase productivity for skilled workers, with one side citing studies and the other emphasizing lived experience.
• Several see the whole sector as a bubble or “musical chairs,” while others argue there is substantial real spend and consumer/business value underneath.

Co‑CEO role and billionaire behavior

• “Co‑Chief Executive” is widely read as a vanity or “seagull management” role: money brings final say without day‑to‑day work.
• Others counter that top‑level CEOs mainly set direction and hire; executing is delegated, especially when one is a celebrity billionaire.
• Some praise the founder’s historical track record and view his involvement as a net positive; others point to delays and underperformance at his space venture as evidence of distraction.

Relation to Amazon and the AI landscape

• Multiple comments argue Amazon has become bloated and ineffectual in AI, with tiny startups out‑innovating it; this could explain why a separate venture was chosen.
• People note Amazon’s existing multi‑billion stake in another frontier lab and hope this new effort is “something wildly different,” possibly focused on physics‑based or simulation‑driven scientific discovery.
• There’s cautious optimism that more well‑funded frontier labs increase competition and innovation, tempered by concern that this accelerates risky capabilities.

Ethics, science, and public trust

• Some see “AI to advance science and engineering (e.g., materials, manufacturing, spacecraft)” as one of the most socially positive AI directions.
• Others are skeptical, recalling earlier promises from high‑profile AI orgs that later pivoted to profit maximization; trust in billionaire‑led “for humanity” narratives is low.
• A recurring criticism is opportunity cost: instead of another AI moonshot, ultra‑wealthy individuals could address homelessness or other social problems, but commentators also argue that their personalities are intrinsically driven to chase more influence and wealth.

Miscellaneous reactions

• Several mock the name “Project Prometheus” as overused, and joke about mythological punishment and Amazon‑style liver subscriptions.
• Co‑CEO structures are called “a recipe for disaster” by some, though others note examples where dual leadership appears functional.
• Side threads discuss whether a 100‑person, multi‑billion‑dollar entity still counts as a “startup,” NYT’s “A.I.” styling, and celebrity‑gossip details of the founder’s social life.

Why geothermal hasn’t been a “holy grail”

• Usable high‑temperature resources are geographically patchy (Iceland, rift zones, volcanic regions). In most areas, hot rock is deep, heat flow is tiny (~40–60 mW/m²), and rock is a poor conductor, so you quickly “cool the rock” and must wait for it to reheat.
• Several commenters frame non‑volcanic geothermal as more like a finite hot‑rock “battery” than a continuously renewable source unless drilling is very cheap and very deep.
• Economics are “iffy”: very expensive wells for tens of MW, with high exploration risk and uncertain output. In many cases, solar and wind are already cheaper.

What’s changing

• Oil/gas drilling and fracking have driven costs down and enabled much deeper, more precise wells; some see this as the enabling tech for “deep geothermal” / enhanced geothermal systems.
• Ideas: plasma drilling, fracturing to increase rock contact, branching wells, and reusing orphaned oil wells for geothermal remediation projects. Opinions are mixed on how much this really fixes cost and water‑intrusion issues.

Heat vs power: ground‑source confusion

• Several comments emphasize the difference between:
  • Deep geothermal power (hot rock, steam turbines, MW‑scale electricity).
  • Ground/pond‑source heat pumps and district heating, which mainly exploit shallow ground as a seasonal heat store, often ultimately solar‑driven.
• Ground‑source heat pumps are praised as effective for buildings, but they don’t solve grid‑scale electricity needs.

Geothermal vs solar, wind, and nuclear

• Pro‑geothermal view: dispatchable, low‑carbon, good complement to intermittent renewables and for district heating (e.g., Munich, Iceland, flooded mines).
• Skeptical view: steam turbines and drilling are fundamentally expensive; with PV module prices plunging and batteries improving, geothermal will remain a niche except in very favorable geology.
• Large side debate: whether nuclear fission should be the core solution (cheap baseload if politics and regulation allowed) vs renewables+batteries outcompeting new nuclear on cost and build speed. No consensus.

Grid integration, storage, and “baseload”

• One camp argues “baseload generation is obsolete”: cheapest energy is now intermittent (solar/wind), and what’s needed is dispatchable capacity and storage (batteries, pumped hydro, demand shifting).
• Others counter that real grids still have large continuous loads and that countries relying heavily on intermittent renewables (e.g., Germany) struggle with costs and coal backup, whereas nuclear‑heavy grids (e.g., France) enjoy cheap, low‑carbon power—though maintaining aging fleets is getting very expensive.
• Several note promising work on large‑scale batteries, thermal storage in rock/soil, and grid‑forming inverters, but long‑duration/seasonal storage remains hard; many expect some continued fossil backup.

Risks and planetary impacts

• Induced earthquakes from enhanced geothermal projects have already shut down some trials, prompting calls for caution, especially in historically seismic regions.
• Concerns about “cooling the core” are dismissed as physically negligible relative to Earth’s internal heat budget, based on figures shared in the thread.

C++20 as GCC’s Default

• Some welcome GCC 16 moving to C++20 by default, wanting easier access to features like modules without extra flags.
• Others insist serious projects should always pass an explicit -std= flag, so defaults shouldn’t matter for well-maintained code.
• Concern is raised that unpinned legacy projects and deep dependency trees implicitly rely on a stable default and may break when it changes.

Modules Debate

• A strong faction argues C++20 modules are a failed feature: underspecified, implemented ad‑hoc across major compilers, and not robust enough for serious, non‑hobby code.
• It’s noted that the original high‑profile “modules are dead” critique predates standardization, but commenters claim the final standard still lacks a solid, independently implementable spec.
• Counterexamples like Microsoft Office are clarified as using non-standard “header units,” not full C++20 modules, so not evidence of mainstream module adoption.

Standards Support and Backward Compatibility

• People question why not default straight to C++23 or newer; the answer in the linked GCC docs and thread is that support is still incomplete.
• Compatibility concerns center on new keywords and stricter rules making previously valid code fail. There’s disagreement over whether this constitutes “breaking changes”:
  • One view: C++ rarely makes truly breaking changes and is strongly backwards compatible.
  • Another: changing defaults so old code fails to compile is practically a breaking change, even if technically minor.

Bootstrapping and Self‑Hosting

• Some confusion arises about whether changing the default impacts GCC’s own build; others clarify that GCC’s build uses explicit standard flags, so this is only about user defaults.
• There’s a side debate on bootstrapping and whether using the latest standard complicates self-hosting with older compilers; participants dispute what “requires bootstrapping” actually means.

Rust and Release Cadence Comparison

• A few praise C++’s slower, multi‑year default updates compared to Rust’s rapid evolution, arguing Rust’s culture of always targeting very new compilers complicates distro self‑hosting.
• Others counter that Rust projects can and do pin minimum versions, and that rapid improvements are beneficial rather than inherently problematic.

Anubis / Anime Gateway Tangent

• A large subthread focuses on the anime-style Anubis gateway in front of the GCC mailing list:
  • Some find it jarring, unprofessional, or creepy, especially in serious or corporate contexts.
  • Others like the playful aesthetic, argue open-source maintainers should prioritize fun over “corporate bland,” and note that the mascot doubles as a funding/branding mechanism (free version keeps the mascot; paid allows custom art).
  • Comparisons are made to Cloudflare-style blocks: Anubis is considered less harmful because it still shows page content, though some note performance issues on poor connections.
  • There’s a meta-argument about cultural bias toward anime art and whether negative reactions to “anime mascots” reflect broader prejudices.

Coroutines and ABI Concerns

• One commenter wonders whether differing coroutine implementations could break interoperability between GCC and Clang binaries; the question is raised but not substantially resolved in the thread.

Practices and Personal Choices

• Several commenters reiterate they always specify language standards and warning flags (both for C and C++) and consider relying on defaults a bad practice.
• Some developers state they’ll continue using older standards (e.g., C99 or C++03/11) regardless of GCC defaults, prioritizing stability and long-term compatibility over new language features.

Russia–EU War Scenarios & Drone Warfare

• Several comments envision a future Russia–EU conflict shaped by mass, decentralized drone attacks on logistics and civilian infrastructure, not classic tank thrusts.
• Others dispute this, arguing Russia’s battlefield losses, sanctions, and fuel shortages limit its capacity; if it could win big conventional wars, it would have taken Ukraine already.
• Some cite reports of Russia rebuilding and storing tanks, with fewer deployed to Ukraine, reading this either as preparation for larger future conflicts or simply adaptation to a drone-dominated battlefield.
• There is disagreement over whether Russia could quickly seize the Baltics or would instead lose air superiority and supply lines against NATO.

Putin’s Constraints & Domestic Politics

• One line of discussion suggests Putin personally has “no way out” of the war because dictators cannot appear weak, even if Russia as a state could withdraw.
• Internal power struggles among security elites are mentioned as a factor that may limit his options.

Nature of the Airport Drone Incursions

• Commenters ask what drones are actually being seen: cheap FPV hobby drones, civilian quadcopters, or military systems like Shaheds.
• Some say it’s mostly civilian-style drones operated by locals recruited online (e.g., via Telegram), potentially as part of low-cost Russian intelligence/sabotage operations.
• There is frustration over vague imagery and limited public evidence, with comparisons to earlier “mass delusion” drone/UFO episodes.

Countermeasures & Practical Constraints

• Ideas range from jamming, radar, counter-drones, and automated turrets to tracking drones back to operators.
• Others stress constraints: legal bans on shooting/jamming near civilian airports, response-time issues, risk to aircraft and bystanders, and difficulty detecting small, fast drones in time.
• Some governments are reportedly updating laws and exploring specialized anti-drone systems, but defense has largely been oriented toward hobbyist, not military, threats.

Attribution, Motives, and Skepticism

• Proposed culprits include: Russian sabre-rattling, NATO running secret drills, opportunistic “idiots,” and (less credibly argued) China.
• Some see the media narrative as fearmongering to justify expensive anti-drone “walls” and military spending.
• A minority frame the broader conflict as Western aggression against Russia and speculate the drone incidents are false-flag operations to prepare public opinion for a larger war.

Overall reception of the article

• Several commenters found the piece insightful and said it should be taught in professional development; others derided it as naïve, “AI slop”-like, or emotionally tone-deaf.
• Many agreed that “movie logic” (conflict sustained by not naming the obvious issue) is both pervasive in fiction and recognizably present in dysfunctional workplaces, friendships, and marriages.
• Others argued the advice is oversimplified: you can’t fix deep psychological patterns with three conversational tricks.

Debate over the Good Will Hunting example

• The article’s flagship example was widely called out as wrong: in that film, everyone does tell Will he’s wasting his talent; his problem is believing it and processing his trauma.
• Several noted the film is explicitly about how inner change requires experience and emotional readiness, not just someone finally saying the magic sentence.
• This was used to argue that real change rarely comes from a single frank conversation or “epiphany.”

Communication, conflict aversion, and feedback

• Many recognized themselves or their cultures (especially Midwestern U.S.) as kind but conflict‑averse, leading to unclear priorities and hidden tensions.
• Others emphasized how hard it is to receive feedback: sunk-cost thinking, emotional investment, and fear of vulnerability often override stated desires for honesty.
• One thread argued basic communication skills are rare and may worsen as people outsource writing/thinking to AI tools.

When bluntness fails or harms

• Multiple anecdotes described “clearing the air” making relationships colder, awkward, or unrecoverable, especially with conflict‑avoidant people or those with serious mental/behavioral issues.
• Commenters stressed that directness can feel like attack, leave “scars,” or destroy tolerable-but-imperfect dynamics; judgment is needed about when not to raise issues.

Movies, exposition, and “idiot plots”

• Several invoked “Idiot Plot” and discussed how poor communication and withheld info drive drama in films and TV.
• Others noted that in real life, people also avoid uncomfortable topics; movies often mirror, rather than distort, this avoidance.

Deeper psychological and cultural angles

• Some tied the issue to self-deception: people can’t communicate honestly because they’re not honest with themselves.
• Cultural differences (e.g., blunt vs. circumspect societies) were cited as crucial context for how “direct” talk lands.
• A few mentioned therapy and game theory: surfacing implicit knowledge changes the “game,” but usually requires outside help and long-term work, not one neat conversation.

C vs C++ vs “C with Superpowers”

• Many argue that if you want RAII, vectors, smart pointers, and sum types, you should just use C++ (possibly in a “C-like” style) instead of macro-heavy C.
• Counterpoints:
  • C++ is hard to parse and tool for; C stays “hackable” with simpler parsers and tiny compilers (TCC, slimcc, etc.).
  • Some embedded vendors still don’t ship usable C++ toolchains; C remains the lowest common denominator.
  • Migrating a large legacy C codebase wholesale to C++ is non-trivial.

Portability, Toolchains, and Extensions

• The header relies on GCC/Clang features like __attribute__((cleanup)) / [[gnu::cleanup]]; this excludes MSVC and strict C99/C11 environments.
• Clarifications that C23 only standardizes a small set of attributes; cleanup remains a vendor extension.
• Some suggest using C11 threads.h / atomics instead of POSIX mutexes for better portability.

Value and Limits of the “Safe C” Header

• Supporters: neat toy, shows how far you can push C toward safer patterns (RAII-like cleanup, vectors, Result types) without adopting full C++/Rust.
• Critics:
  • Expect many corner cases and UB; without a spec and battle-hardened implementation it’s risky for serious code.
  • Macros create a project-specific mini-language that newcomers must learn.
  • Shared-pointer and view/string_view style constructs still allow use-after-free; nothing enforces correct lifetimes or refcount discipline.
  • “Result” types don’t force checking like Rust; you can still ignore errors.

Safety vs. Language Choice

• Some say energy should go into incrementally rewriting C systems in memory-safe languages (Rust, Fil-C, etc.), not layering more macro magic.
• Others argue there are billions of lines of C that can’t be rewritten soon; incremental tools that reduce footguns are valuable.
• Debate over whether an “improved C” could achieve memory safety via ownership and lifetimes without GC; lifetimes + polymorphism seen as likely required.

GC, Fil-C, and Performance

• Fil-C (a GC-backed C runtime) is raised as a more thorough safety approach.
• Long subthread on garbage collection:
  • One side: GC overhead is negligible for most programs; safety payoff is huge.
  • Other side: GC can significantly hurt throughput, latency, and working set for systems/embedded workloads; manual or ownership-based schemes are still preferred there.

Coding Practices and Alternatives

• Some prefer classic patterns: goto out cleanup blocks, arenas, or simply not freeing process-lifetime data (like parsed CLI options).
• Concern that trying to make C “safe” hides its nature; better to use languages like Nim, Go, Rust, or specialized verified C dialects (Frama-C, Fil-C) when safety is paramount.

Legacy Devices & Alternative OSes

• Commenters note active work on dual-booting older devices like the N900, suggesting Maemo Leste as a strong option despite incomplete hardware support.
• 3G network shutdowns make such devices less usable as phones; someone wonders about a 4G/5G “bridge” that presents a local 2G/3G cell, with a joking reference to Stingray devices.

Linux Phone Experiments (postmarketOS, Sailfish, Waydroid)

• Several people are testing postmarketOS and Sailfish on modern hardware (Fairphone, Xperia, Redmi).
• Consensus: usable for tinkering and some daily tasks, but not yet full daily drivers. Common issues: audio, sensors, and especially banking/“app-only” services.
• Waydroid (Android-in-a-container) works “pretty good” and helps fill app gaps; questions remain about background GPS, sensors, and navigation reliability.
• Some users value having a standard Linux userland (Nix, Python, git, containers) more than perfect phone features.

AOSP Forks, GrapheneOS, and Security Models

• Debate over “why not just hard-fork AOSP”:
  • One side: Android’s permission model and sandboxing are far ahead of classic Unix security and should be preserved.
  • Others: if you can’t or don’t rebase on AOSP, Android apps break; truly hard forks are unrealistic.
  • Concern that if Google stopped updating AOSP, OEM/chip-vendor private channels or Chinese forks would dominate; unclear how non‑open SDK/NDK would affect viability.
• GrapheneOS is cited as an example of a privacy/security-focused AOSP fork:
  • Critics report poor battery life (especially with 5G and GPS tracking apps), an intrusive GPS indicator, and UX too complex for “normal users.”
  • Defenders say it feels like stock Android with better privacy controls and no noticeable battery issues.

postmarketOS vs Android Security

• One camp calls postmarketOS “antiquated” for phones: classic Unix permissions allow mic snooping, ransomware, and credential theft if apps are compromised.
• Others counter that:
  • Linux increasingly uses sandboxing (Flatpak, etc.) and distro trust; dangerous permissions can be constrained.
  • Not all use cases require Android’s tight model; many users value root/admin control and reject “Android‑bis.”
• Follow‑ups stress that all software should be treated as untrusted (citing the XZ backdoor) and that defaults, not optional hardening, matter for most users.

Terminology & Control: “Sideloading” vs Installing

• Long subthread on language:
  • Some argue “sideloading” is a PR term to stigmatize installing apps outside Play Store; they prefer just “installing,” or phrases like “installing from outside the store.”
  • Others say the distinction is useful: installing via the main, monitored channel vs arbitrary APKs from the web is a real risk difference for typical users.
• Comparisons to macOS, Linux package repos, and game consoles:
  • On desktop Linux, nobody calls manual .deb/AppImage installs “sideloading,” but the same conceptual distinction (official repo vs third-party) exists.
  • Some see Android and iOS converging on console-like walled gardens; others argue it’s “industry standard” and still more open than consoles/iOS.
• There’s disagreement over whether Play Store monitoring meaningfully reduces risk, with counterexamples pointing to Play malware and F-Droid’s better record.

Hardware Openness, Bootloaders & Firmware Layers

• Concern that unlockable bootloaders are getting rarer; advice is to buy devices officially supporting unlock (LineageOS device list, recent Pixels, some Motorolas).
• Xperia devices are praised for upstream kernel contributions, bootloader unlocks, headphone jacks, and microSD—even as some report physical quality issues.
• Technical discussion on why phones lack a PC-like “BIOS experience”:
  • Many modern phones (especially Qualcomm-based) do use UEFI under the hood, but there is no ACPI-like standard layer.
  • On x86, decades of legacy BIOS/UEFI interfaces (INT 10h, 13h, 16h) make minimal OS bring-up trivial and portable.
  • On ARM, each board relies on a specific devicetree and custom drivers; that fragmentation makes generic OS support and projects like postmarketOS much harder.

Alternative Uses & Networking Freedom

• Some run postmarketOS phones as pocket Linux PCs with external keyboards and power banks; ARM and small screens limit but don’t prevent real development work.
• A few envision phones as nodes in mesh networks and resilient P2P systems (Freifunk-style), independent of big tech clouds.
  • SDR + protocols like Reticulum/Yggdrasil could provide the fabric, but stock Android struggles as a general-purpose server/container host.
  • Commenters lament that phones, despite powerful open-source cores, are “tivoized” and locked down like consoles, undercutting the benefits of open source.

Big Tech, Competition, and Lock-In

• One commenter delivers a broad critique of big tech as building “alien” ecosystems, with heavy AI/PR layers detached from human needs.
• Others respond that in competitive markets, firms “fight for their lives” by erecting barriers to competition; app-store lock‑in and restricted installation are seen as examples.

Device Support & Resources

• The postmarketOS device compatibility matrix is highlighted, plus a scraped table of “testing” devices (considered relatively stable).
• LineageOS’s device list with a bootloader-unlock filter is suggested as a guide for future‑proof, hackable purchases.

Risk & Bricking Concerns

• Someone asks how hard it is to unbrick a phone when attempting dual-boot/flash experiments; the thread does not provide a clear or general answer.

Desire for openness and control

• Many see these hidden iPadOS features on iPhone as proof of how much Apple locks users out of their own hardware.
• Several commenters say they’d rather have “boring” but open devices (Linux laptops, Android/GrapheneOS phones) than powerful but constrained Apple hardware.
• Some argue that, as paying adults, they should be allowed to assume more risk (sideloading, root, custom OS) if they want.

What people say they’d do with a more open iPhone/iPad

• Run full browsers with extensions, true ad blocking, and alternate engines.
• Sideload apps (especially FOSS), install personal/internal apps permanently without paying Apple, and pin old versions to avoid “enshittified” updates.
• Script and automate via shells (termux/a-shell–style), run CLIs like ffmpeg/yt-dlp, packet sniff, fine-grained firewalls, and even Emacs, Python stacks, or Mathematica.
• Customize UI/UX (window managers, key remapping, disabling unwanted UI “glass” trends) and small quality-of-life fixes (flashlight behavior, Screen Time controls).
• Use phone/tablet as a dockable desktop: external display, keyboard/mouse, desktop-class multitasking, maybe even VMs.

Security, battery life, and complexity

• Opponents of openness stress that phones hold “entire lives” and that relaxed security, root, and sideloading would massively increase risk for typical users.
• Others counter that desktop OSes work despite weaker models, that power users could improve battery by killing unwanted background services, and that Android/Lineage/GrapheneOS show FOSS can be efficient.
• Some think iPad/iPhone multitasking UIs are already too complex for nontechnical users; others argue complexity should be optional, not forbidden.

Mac vs Linux and “locked down” debate

• Debate over whether Apple Silicon Macs are truly “locked down”: many say macOS lets them build/run anything and is a good dev machine; others dislike notarization, UX constraints, lack of Linux boot, and proprietary GPU/Vulkan stack.
• Asahi Linux is mentioned as partial relief but not yet a full mainstream replacement.

iOS vs iPadOS and feature gating

• Thread consensus: iOS and iPadOS are clearly the same codebase with features toggled via configuration, not separate OSes.
• Some see the separation as largely marketing and possibly regulatory strategy (keeping iPad out of EU “gatekeeper” rules).

Multitasking, small screens, and external displays

• Mixed views on split-screen and Stage Manager: some find them useless or cramped even on 11" iPads; others rely on split-screen even on small Android phones.
• Strong interest in a DeX-like or even macOS-on-iPhone/iPad mode when docked to a monitor, but skepticism Apple will ship anything that cannibalizes MacBooks or weakens App Store control.

Meta: article accessibility

• Multiple complaints that the linked site is overloaded with ads, trackers, and/or Cloudflare errors, making it nearly unusable without reader mode.