Hacker News, Distilled

Overall sentiment on tiling window managers

• Many commenters love tiling WMs (i3, Sway, Awesome, XMonad, Hyprland, etc.) and say they dramatically reduce “window juggling” and mental overhead.
• Others remain unconvinced or bounced off them, finding the cognitive load, shortcut memorization, and layout management not worth it.
• Several people say they mostly run one app full‑screen per workspace, using tiling mainly for terminals or occasional side‑by‑side layouts.

Niche vs. “we need this”

• Multiple comments stress that tiling WMs are a niche within an already‑niche Linux desktop, so massive investment or new DEs is unrealistic.
• Others counter that the niche is well served: there are many actively maintained tiling WMs and even distro spins that ship them.
• Some argue Linux already suffers from too many DEs; they’d rather improve existing ones than create new tiling‑centric environments.

Integration with desktop environments

• A recurring theme: standalone tiling WMs are powerful but lack DE conveniences (auto‑mounting media, display config, volume/network integration, portals, notifications).
• Some users run tiling WMs inside DEs (e.g., KDE/Xfce/MATE + i3/XMonad) to get both tiling and DE services, though Wayland makes swapping WMs harder.
• KDE and GNOME have tiling features or extensions (KWin scripts, GNOME extensions, PaperWM-like approaches), but these are seen as less cohesive or sometimes fragile.

Usability, workflows, and accessibility

• Strong divide between keyboard‑centric and mouse‑centric users. Tiling fans praise precise keyboard workflows; others prefer quick snapping, grids, or FancyZones‑style tools on top of floating WMs.
• Some dislike automatic resizing of browsers/video when new windows appear; tiling users respond that workspaces, tabbed/stacked layouts, or newer scrolling/PaperWM‑style WMs address this.
• Poor app and web UI scaling, padding-heavy “low density” design, and mobile breakpoints are called out as major problems, especially for visually impaired users.

Technical and platform constraints

• Wayland compositors typically bundle WM + compositor, making “DE + different tiling WM” setups harder than on X11.
• Specific pain points mentioned: screen sharing, xdg-desktop-portal quirks, XWayland scaling, and proprietary Nvidia drivers blocking some Wayland tilers.
• Some see Wayland as reducing modularity; others note active development and X11 being effectively feature-frozen.

Analogy: Pie vs. Software

• Many argue the pie analogy breaks down: pies are physical, consumable, geographically constrained, degrade over time, and are rival goods; software is infinitely copyable, non-rival, and globally accessible.
• Several tweaks are proposed: software is more like a pie recipe (or chair design) than a pie; others think it’s closer to a shovel or chair (a durable tool) than to food or art.
• Some note that analogies to music performance, painting, or blacksmithing may work better for recreational programming than food analogies.

Originality vs. Utility

• One camp says: because software is easily duplicated, users reasonably ask “How is this different or better?” before investing time. Utility and novelty justify attention.
• Another view: insisting on originality for every side project is misplaced; many things exist primarily for fun, learning, or craftsmanship. Execution quality can be a differentiator even if the idea isn’t new.
• There is debate about whether reimplementations (e.g., another TODO app, JS framework, or office suite) have value beyond the creator’s learning or portfolio.

Learning, Craft, and Non-Utility Value

• Multiple comments stress that copying/replicating (simple apps, basic recipes, garden tools) is how people build mastery before doing “state-of-the-art” work.
• Others emphasize intrinsic joy and personal expression: like playing classical pieces, painting, or doing covers, originality isn’t always the main point.

Sharing Side Projects and HN Culture

• Some say that posting on Hacker News implicitly invites evaluation against existing solutions; submitters should clarify what’s different to respect readers’ attention.
• Others criticize harsh “what does this offer over X?” reactions, especially toward free, learning-oriented projects, as entitled or unempathetic.
• There’s recognition that HN’s novelty-seeking, dopamine-driven dynamic biases discussions toward originality and can undervalue solid but derivative work.

Feedback, Friendships, and Social Norms

• Disagreement over how friends “should” respond: some expect honest, even blunt feedback about unoriginality; others see that as emotionally tone-deaf or mean unless invited.
• Several note the difference between supporting someone’s growth (asking about their process or goals) vs. demanding market-level differentiation for a hobby project.

Overall views on the featured translation couple

• Several commenters enjoy their translations, saying they feel “Russian in English,” preserve structure and thought patterns, and create a strong sense of place.
• Others find them clunky, overly literal, and hard to read, describing the prose as unnatural or like “mock Russian accents.”
• Some feel the pair is aggressively marketed and has an unhealthy near‑monopoly in English editions of major Russian novels.
• A linked critical essay is cited multiple times to support the view that these translations degrade the originals into awkward English.

Alternative translations and preferences

• Multiple other translators are recommended for key Russian novels; some readers strongly prefer them for smoother English and better narrative flow.
• Older, “Victorian-sounding” translations divide opinion: some say they’re poetic and more intense; others say they feel like English novels with Russian names.
• There is debate over whether translations should modernize the language (to match how the original felt to contemporary readers) or preserve archaism (to mirror how the originals now feel to modern Russian readers).

Translation philosophy

• Tension between “literal” vs “literary effect” is central: some value close adherence to syntax and rhythm; others want idiomatic English that reproduces emotional and aesthetic impact.
• A recurring metaphor contrasts “faithful but ugly” vs “beautiful but unfaithful” translations, with some arguing that difference from the original is not automatically a defect.
• Examples from other difficult authors and experimental works illustrate how wordplay, slang, and meter complicate translation choices.

Language, politics, and culture

• One tangent debates whether “this couple reign” vs “reigns” is correct, touching on collective nouns in American vs British English.
• Another thread explores how current Russian politics has dampened some readers’ appetite for Russian culture, while others insist on separating long-term cultural achievements from present events.

Comparisons, fan work, and AI

• Commenters note similar translation wars around fantasy series, comics, and manga; name choices and puns are particularly contentious.
• Fan and underground translations (including “black market” editions) are described as surprisingly sophisticated.
• AI translation is raised as a future tool for refreshing public‑domain texts, but no concrete high‑quality literary examples are given.

Overall reaction to the lecture

• Many describe the 1982 talk as “fantastic,” striking for clarity, humor, and audience engagement.
• The first half aligns with other public talks by Hopper; the second half goes deeper into technical and architectural foresight.
• Viewers highlight her stand-up–like delivery, sharp wit, and strong leadership ethos (focus on leading people vs. managing things).

Technical foresight and systems thinking

• She discusses future-oriented topics for 1982: cybersecurity, loose coupling/modularity, “systems of computers,” VLSI/SoC, and language standardization.
• Her argument for breaking systems into multiple specialized computers is seen as an early articulation of distributed systems and cloud-like architectures.
• A proof she gives about how software changes propagate is praised as a strong argument for encapsulation and loosely coupled design (applicable to OO, FP, etc.).
• Her comments on “valuing information” and the lack of metrics for it are viewed as still accurate in 2024, especially in domains like biomedical data.

Microcontrollers and “computers per dollar”

• Hopper’s reference to the cheap Intel 8021 triggers a long comparison with modern microcontrollers.
• Several examples show drastic improvements in performance, memory, power, programmability, and peripherals at a fraction of the (inflation-adjusted) cost.
• Rough estimates suggest improvements on the order of hundreds to hundreds of thousands in price/performance, but only ~25× in “computers per buck,” the metric Hopper emphasized.

Visualization, databases, and 3D modeling

• Her suggestion to use 3D “molecule kits” to model complex distributed systems sparks debate.
• Some see this as conceptually right but practically superseded by abstraction, encapsulation, and robust interfaces rather than rich visual modeling.
• Others link her idea loosely to modern concepts like vector databases and matrices, though there is disagreement on how directly accurate that is.

Oxen analogy and scaling debate

• Her “don’t grow a bigger ox, use two oxen” line is taken as an early argument for horizontal scaling.
• Long subthread debates:
  • One side: vertical scaling has limits; parallelism is essential and now dominant.
  • Other side: analogy is imperfect; scaling up and out are complementary, and “bigger computers” were and are often practical.
  • Consensus: real-world engineering involves tradeoffs; parallelism is powerful but non-trivial and often misapplied.

NSA, FOIA, and archival issues

• The lecture’s release followed FOIA pressure; NSA initially said they lacked hardware to read 1‑inch AMPEX tapes.
• Commenters note NARA and specialist vendors could (and ultimately did) help; some think public discussion nudged action.
• Mixed views on NSA:
  • Some praise this release and earlier contributions (e.g., hardening DES S‑boxes).
  • Others emphasize later distrust, citing Dual‑EC and broader concerns about standards “backdoors.”
  • Extended debate over how many standards were weakened, whether actions were transparent, and how to interpret historical episodes.

History, lore, and human side

• People enjoy her nanosecond/microsecond “props,” the “first computer bug” moth story, and self-deprecating jokes about being an “early artifact.”
• References to her Letterman appearance and her pride in Navy service reinforce her cultural and inspirational status.
• Generational remarks note that she accurately foresaw children quickly becoming competent computer users, though her optimism about rural schools is questioned.

Side tangents

• Toxic waste and PCBs: Hopper’s offhand reference leads to a long digression on Superfund sites, semiconductor pollution, and generational attitudes toward environmental harm.
• Several users track down and digitize an obscure 1982 microcomputer paper she cites, demonstrating community-driven archival work.
• Practical tips are shared on finding transcripts (YouTube auto-transcript; similar 1985 stenographic record).

Human vs. Machine Dishwashing

• Several commenters initially assumed the article was about dishwashing machines; others clarified it focuses on human dishwashers who use commercial machines.
• Professional dishwashers are seen as the “heart” of a kitchen: fast, reliable cleaning prevents service collapse, especially when equipment breaks.
• Some note overlapping roles with busboys and other back-of-house staff; in practice, boundaries blur in many US restaurants.

Wages, “Living Wage,” and Labor Economics

• Intense debate over whether ~$10/hr (circa 2017 US) is fair:
  • One side: it’s unskilled, quickly trainable work; if there’s a line of applicants, the wage is “market‑correct.”
  • Other side: any full‑time job should cover basic living costs (housing, food, healthcare, some savings); otherwise the wage is too low regardless of market.
• People reference “living wage” calculators and argue over assumptions (e.g., 40th‑percentile housing costs).
• Some argue minimum wage should be a genuine living wage; others prefer UBI or stronger welfare with fewer or no minimum‑wage constraints.
• Counterpoint: raising minimum wage risks some businesses failing and workers moving to welfare; supporters respond with examples where higher minimums didn’t cut employment.

Tipping and Pay Distribution in Restaurants

• Many note the dishwasher often doesn’t get a share of tips, despite being critical to service.
• Others report tip‑pool systems where dishwashers and back-of-house get a fixed share; some dishwashers can reach $20–$40/hr in high‑end venues.
• Tipping is criticized as historically rooted in exploitation, used to justify low base pay, and as socially coercive.
• Some defend tipping as a way for high-performing staff to earn more and as culturally entrenched.

Working Conditions and Social Value

• Multiple firsthand stories describe dishwashing as physically exhausting, hot, loud, and chemically harsh, but also offering camaraderie and pride in hard work.
• Several argue “low‑skill” doesn’t mean “low value”: society depends on such roles as much as or more than many white‑collar jobs.
• Others emphasize replaceability and low training time to justify lower pay, prompting pushback around dignity and externalities (homelessness, crime, health).

Chemicals, Health, and Equipment

• Concerns raised about commercial dishwashers not fully rinsing detergents and rinse aids; cited research on epithelial toxicity at certain concentrations.
• Some distinguish commercial vs home machines: studies mentioned that household levels appear less worrisome.
• Rinse aids are singled out as likely source of taste on glasses and potential health issues; some disable them.

Automation and Robots

• Linked commercial dishwashing robots (~$3,000/month service) spark debate about economics vs human labor.
• Some think robotics could be viable in very high cost-of-living settings; others see hidden babysitting/maintenance costs and doubt big price drops.

Unions, Immigration, and Policy

• Stories of mandatory union membership where temp dishwashers pay dues but see few direct benefits; defenders say unions optimize for long‑term, core workers.
• Discussion of undocumented workers filling kitchen roles: they’re seen as easily exploited and essential to current restaurant economics.
• Suggested remedies include regularizing undocumented workers and punishing employers who hire off‑books, rather than only penalizing migrants.

Personal Anecdotes & Cultural Comparisons

• Many reminisce about dishwashing as teens: learning work ethic, moving up to line cook or server, or confirming they didn’t want restaurant careers.
• Comparisons to Europe and Nordics: more vacation time, stronger safety nets, different union models, and weaker tipping culture; several argue these yield better outcomes.
• Examples from Japan and elsewhere where all students share cleaning/food duties are contrasted with US practices, including inequitable “work for lunch” schemes for kids.

Rust syntax and type system

• Several C/C++ developers like Rust’s safety but strongly dislike its syntax, especially deeply nested generic types (e.g., Result<Either<...>>), which they compare to “ugly” modern C++ template code.
• Others argue these types encode valuable information at a glance (errors vs new vs existing objects) and are standard ML-style algebraic data types.
• Debate over “over-typing”:
  • One side warns that very strong, highly specific types can make code rigid and painful to evolve.
  • The other side argues strict types are desirable in low-level code and that strong typing plus good tooling can safely guide refactoring.
• There is discussion about whether language-level sugar (e.g., union-like A | B) would help, and about differences between ADTs and union types for exhaustiveness checking.

Rust in the Linux kernel: culture and conflict

• A major Rust-for-Linux maintainer stepped down, citing ongoing “nontechnical nonsense.”
• Multiple comments link this to pushback from long-time C-only kernel developers, including a widely discussed conference exchange where a senior developer framed Rust as a “religion” and Rust bindings as “second-class citizens.”
• Some see that tone as rude, hostile, and discouraging to contributors; others defend it as a blunt but technically grounded warning that C refactoring will not be constrained by Rust bindings.
• There is debate over whether kernel developers should proactively help Rust maintainers (e.g., giving heads-up on API changes) vs. treating breakage as entirely the Rust team’s responsibility.

Memory safety, users, and long-term viability

• Pro-Rust commenters emphasize that most kernel CVEs are memory safety issues and that Rust could significantly reduce such bugs, even if outright panics are now rare.
• Skeptics argue Linux is already very stable for users and that introducing Rust risks fragmenting the developer base or excluding contributors who only know C.
• Some view Rust as essential for attracting a new generation of systems programmers, given the shrinking pool of expert C developers; others claim C is simple enough and that Rust’s complexity may slow development.

Alternatives and “Rust kernels” vs Linux integration

• A recurring argument: instead of fighting over Rust in Linux, proponents could build a new, fully memory-safe kernel in Rust and try to outcompete Linux.
• Counterarguments:
  • Re-creating a production-grade Linux alternative is seen by many as a multi-decade, massively expensive effort, unlike the 1990s context in which Linux emerged.
  • Improving Linux incrementally with Rust (e.g., for new drivers, embedded kernels, or specific subsystems) yields security benefits today.
• Mentioned alternatives include Zig (once mature) and various Rust-based OS projects, but none currently match Linux’s maturity or adoption.

Naming and API Design

• Several comments focus on confusing names like WorkerGlobalScope vs WorkletGlobalScope.
• Some argue that small internal differences in long identifiers are hard to visually parse; others counter that “Worker” and “Worklet” are spec-defined primitives and should be preserved.
• Alternatives like GlobalScopeForWorker or namespacing (Worker::GlobalScope) are suggested but seen as either clunky or autocomplete-hostile.
• General agreement: naming is hard; conventions affect readability, autocomplete, and error likelihood.

Scale, Build Times, and Barriers to Contribution

• Many note how daunting Chromium’s size and build requirements are (tens of minutes to hours, large RAM/CPU needs).
• Some see this as undermining the “anyone can contribute” and “just fork it” ideals for big OSS projects.
• Others argue:
  • Clean builds are worst case; incremental builds are much faster.
  • A motivated hobbyist with a mid-to-high consumer machine can maintain a small fork.
  • Browsers are OS-scale projects; heavy requirements are expected.

Tooling and Code Navigation

• Online code search (source.chromium.org / cs.chromium.org, Android’s equivalent) is widely praised for cross-references and navigation.
• Some prefer lightweight editors with ctags or built-in indexing; others use VS Code with clangd or similar LSPs.
• There’s debate over language-aware indexing vs fast plain-text search; several tools and extensions aim to make huge repos searchable locally.

Experiences with Browser Projects (Chromium & Firefox)

• Multiple anecdotes of first-time fixes in Chromium and Firefox: challenging but possible, with long compile times and hardware stress on older machines.
• Some report smoother review experiences in Chromium than in Firefox; others describe being “ghosted” on large OSS projects generally.
• Comments highlight modularity differences: Firefox devtools can be built separately; unified builds and artifact builds help performance.

Open Source, Corporations, and Compensation

• One thread questions volunteering for wealthy corporations, suggesting they should pay contributors or that effort is better spent on charities.
• Others respond that:
  • Most Chromium work is already paid; external fixes often solve the contributor’s own pain.
  • Refusing to upstream fixes can hurt users and increase personal maintenance burden.

EU Privacy Culture vs U.S. Practices

• Many commenters applaud the fine as evidence the EU treats privacy as a fundamental right, unlike the U.S., where data exploitation is seen as normalized.
• Others argue the EU overstates its moral superiority, noting pervasive European surveillance and weak practical differences for users.

Innovation, Competition, and “Leaving Europe”

• One camp warns strict rules could reduce innovation and drive U.S. companies away, harming EU users.
• The dominant rebuttal: the EU market is too big to abandon; if some firms leave, local or non‑US competitors (e.g., Bolt, FreeNow, local delivery/taxi apps) will fill the gap.
• Several argue that what’s framed as “innovation” is often just worker exploitation or regulatory arbitrage, not genuine technical progress.

GDPR Enforcement and the Uber Case

• Many welcome proof that GDPR is “not just cookie banners,” criticizing banners and consent forms as mostly malicious or sloppy compliance.
• The Uber fine is tied to years where it transferred highly sensitive driver data to the U.S. without a valid legal mechanism after Privacy Shield was invalidated.
• Some note fines must be high enough to not become just “cost of doing business,” but others see the size and multi‑year appeal process as quasi‑political or a revenue grab.

EU–US Legal Conflict & Data Location

• There’s extensive discussion that U.S. laws (FISA 702, CLOUD Act, etc.) let U.S. authorities compel access to data, including non‑U.S. persons, even if stored in the EU.
• One view: this makes full compliance for U.S.-linked companies effectively impossible; fines punish companies for a geopolitical dispute.
• Counterview: that’s a U.S. problem; if U.S. law makes your company incompatible with EU rights, you shouldn’t handle EU personal data.

Global Internet Fragmentation & Tech Sovereignty

• Some lament the end of a borderless internet, predicting nationally siloed services and higher complexity.
• Others respond that fragmentation is a necessary reaction to abuse (mass surveillance, data brokerage, platform dominance), and that local, privacy‑respecting ecosystems are preferable.

Capitalism, Regulation, and Morality

• Multiple comments argue capitalism is structurally amoral and will exploit data unless regulated.
• Disagreement centers on whether current EU approaches are effective guardrails or overreach that risk long‑term competitiveness.

Reaction to Removing the Pricing Calculator

• Many agree the core problem was users’ misunderstanding of metrics (QPS, vector counts), not the calculator UI itself. Small input errors could yield 10–1000× overestimates.
• Some argue removing the calculator plausibly improves signups but may simply hide sticker shock, pushing painful surprises to later bills.
• Others counter that incorrect self-estimates are worse than no estimate, and once users are onboarded they can see real usage-based billing and extrapolate more reliably.
• A few think the real fix should be a simpler pricing model, not deleting the tool.

Pricing Transparency and “Contact Us for Pricing”

• Strong dislike for “contact us for pricing” in B2B and especially consumer contexts; many say they will skip such vendors entirely.
• Concerns: price discrimination based on company size, sales “games,” sunk-cost pressure after lengthy sales calls, and difficulty piloting a tool when usage is initially unknown.
• Some defend non-public or negotiated pricing in narrow enterprise markets or bespoke solutions, but others insist there should at least be clear ballpark tiers.

A/B Testing, Metrics, and Dark Patterns

• Multiple comments criticize shallow A/B practices: optimizing for signups or clicks without tracking long-term outcomes (retention, complaints, churn).
• Removing information (like pricing details or snippet content) often increases short‑term engagement but may harm user trust or satisfaction.
• Some note this dynamic creates incentives for dark patterns and information asymmetry rather than genuine clarity.

Simplicity vs. Necessary Complexity

• Broad support for the “removal” mindset: YAGNI, “less is more,” and the idea that good design often comes from deleting features, not adding.
• Counterpoint: overzealous YAGNI can backfire; cheap, future‑useful structures removed early can be expensive to reintroduce later. The “right” deletion rate is debated.
• Several reference engineering cultures that deliberately encourage removing components, accepting that some must later be added back.

Organizational and Cultural Factors

• Long internal debates, polls, and Slack threads are seen as symptoms of over‑hiring, unclear ownership, and design‑by‑committee.
• Removing user‑visible features is politically hard; once something exists, some workflows inevitably depend on it, making deletion risky and unrewarded.

Personal experiences with fraudulent applicants

• Multiple commenters report similar remote-hiring scams: fake locations, fake employers, and candidates who collapse under basic probing about cities, companies, or schools.
• Tactics include: someone else taking the technical interview, then a different person showing up for the job; camera-off video interviews with strong performance, followed by an obviously different person on day one.
• Some say fraudsters treat this as a numbers game, A/B-testing resumes and interviews across many stolen or fabricated identities.

Red flags vs discrimination

• Common “signals” discussed: no online presence, implausible work locations, weak English for claimed background, highly scripted answers, refusal of non-remote work, and background noise suggesting a “call center of interviews.”
• Several people warn that some of these strongly overlap with protected characteristics (race, national origin) and normal behavior (no social media, desire for remote work).
• There is concern that “name doesn’t match ethnicity” or “English level doesn’t match name” is close to illegal stereotyping under US employment law.

North Korea-specific debate

• Some accept the NK attribution, citing prior talks with law enforcement and known DPRK programs training developers abroad and assigning them to earn foreign currency or support hacking groups.
• Others argue that the same patterns exist in many other countries (China, India, etc.), so labeling weak applications as “North Korean” is speculative.
• Several stress empathy for ordinary North Koreans coerced by their state, while still acknowledging sanctions and security risks.
• A few question whether the supposed NK engineers are even competent, or whether companies are just bad at hiring.

Skepticism about the article and ex-intelligence framing

• Multiple commenters doubt the story’s strength of evidence; “suspected North Korean” is seen as doing a lot of work.
• Some note the piece repeatedly highlights the founders’ CIA background and see it as marketing, propaganda-adjacent, or “trust and safety industry” puffery.

Hiring practices, legality, and ethics

• Discussion touches on legality of probing location details (“what metro stop?”) and using accents/names as signals, with warnings about US anti-discrimination law.
• Some defend verifying resume truthfulness; others say many supposed “red flags” are normal traits of privacy-conscious or non-traditional candidates.

What the law changes

• Codifies an employee’s right to ignore work calls/messages outside contracted hours, with some “emergency/irregular hours” exceptions.
• Employers may still contact staff; the change limits their ability to discipline or fire people for not responding after hours.
• Seen by many Australians as a formalisation of good practice rather than a radical shift, but important where managers are abusive.

Support and perceived benefits

• Protects low‑income and vulnerable workers (e.g., retail, some teachers, legal staff) who are pressured to be effectively on call 24/7 without pay.
• Gives workers a legal “foot to stand on” with ombudsmen/tribunals when managers conflate “problems” with “emergencies.”
• Some frame it as restoring pre‑smartphone norms where work stopped at the door.

Concerns, loopholes, and enforcement

• Skeptics argue managers will simply reframe retaliation as “poor performance,” “unresponsive,” or “not a team player.”
• Phrases like “reasonable to refuse” and “high salary includes reasonable overtime” are seen as vague and open to abuse.
• Enforcement is viewed as similar to other labor rights: you still need evidence and a case; subtle penalties are hard to prove.

On-call, emergencies, and overtime

• Law is not understood to ban planned on‑call rotations; it targets unpaid, ad‑hoc expectations of 24/7 availability.
• Disagreement on what counts as an “emergency” (life/safety vs. business‑critical outages).
• Some argue true 24/7 support should require paid shifts or explicit on‑call compensation; others prefer light on‑call to avoid permanent night shifts.

Business impact and competitiveness

• Some employers complain of “death by a thousand paper cuts,” higher costs, and reduced startup viability.
• Others counter that if a business model relies on unpaid off‑hours labor, it’s exploitative and should fail.

Cultural and international context

• Comparisons to EU countries (Germany, Netherlands, Switzerland) where strong norms or laws already limit off‑hours contact.
• Contrasts drawn with the US and India, where at‑will employment or weak protections make saying “no” risky.
• Many commenters already self‑enforce boundaries via separate devices, disabled notifications, and refusing to install work apps on personal phones.

Deep Time and Earth’s Changing Face

• Many comments focus on how long Earth has existed and how radically it has changed.
• People share tools and videos that visualize continental drift and geological time, emphasizing how different Earth looked 120+ million years ago.
• There is mention that 66 million years ago the continents were roughly where they are now, but earlier (e.g., 120 million years) Africa and Brazil were adjacent.
• Some discuss variable rates of continental drift, suggesting plates can move faster initially and slow later, using ocean floor roughness as a heuristic.

Human Future vs. Cosmic Timescales

• One thread notes that Earth has “used up” much of the Sun’s habitable window; humans might have ~1 billion years before solar heating ends habitability.
• Others argue this is abstract compared to near-term risks like climate change, mass extinction, and civilizational collapse.
• There’s debate over whether humanity is on its “way out” due to industrialization or capable of adapting through technology, clean energy, and geoengineering.

Climate Change, Collapse, and Adaptation

• Pessimistic view: severe climate impacts (AMOC shutdown, uninhabitable heat zones, sea level rise) could cause famine, mass migration, war, and long-term setback with no “second industrial revolution.”
• Optimistic view: humans are highly adaptable; progress is (or was) exponential; resources, space, and technology (solar, nuclear, storage, vertical farming, space resources) can support far more people.
• Disagreement over whether such crises threaten extinction vs. “only” massive suffering and reduced population/quality of life.

Hunger, Progress, and Ethics

• Dispute over metrics: some emphasize that more people are hungry in absolute terms; others stress hunger rates have fallen with technological and agricultural progress.
• One side argues growth is essential and historically improves life for the poor; the other insists that even small numbers of preventable deaths remain a moral tragedy.

Creationism, Evidence, and Family Dynamics

• Several comments discuss how fossils, dinosaurs, and geology challenge young-Earth creationism.
• Some note that committed creationists often reinterpret evidence (e.g., global flood) rather than abandon beliefs.
• Others describe avoiding such topics with religious relatives, or realizing close family members interpret scripture very differently.

Plate Tectonics and “Matching” Footprints

• Matching fossils and formations across continents are highlighted as key evidence for continental drift and plate tectonics.
• Some skepticism about the headline term “matching”: clarification that it refers to the same type of dinosaur tracks, not the exact same individual.
• A few readers wanted direct links to the primary scientific paper rather than repeated popular summaries.

Defense Spending, Threats, and “Defense” vs. “Offense”

• Some argue defense is a “growth industry”; others note US defense as % of GDP is historically low.
• Supporters say more defense innovation is needed to deter authoritarian states and avoid over‑consolidated contractors.
• Critics counter that the US is already “bellum paratum,” highly militarized, and often uses force offensively rather than defensively.
• Debate over whether cruise missiles can ever be truly “defensive,” with some saying it’s about use, not tech.

Ethics, Foreign Policy, and Democracy vs. Dictatorship

• Multiple comments highlight US involvement in coups and regime change (Latin America, Iran, Operation Condor) as evidence that US power isn’t always used to defend democracy.
• Others stress they still prefer a world led by imperfect democracies over authoritarian regimes.
• One view: democracies can eventually admit and compensate for wrongs (e.g., Japanese internment); counterpoint: even dictatorships sometimes repudiate past crimes.

War Crimes, Accountability, and International Law

• Concerns raised about lack of accountability for US war crimes, including legal shielding from international courts.
• Examples cited: drone strikes, lethal strikes programs, Yemen airstrikes linked to US/UK weapons, and laws enabling resistance to ICC jurisdiction.
• Defenders emphasize terrorists and hostile actors using civilians as shields; critics say this is overused to excuse civilian casualties.

Global Peace, Deterrence, and the UN

• One camp says the world is increasingly hostile; another claims it’s the most peaceful era ever.
• Credit for avoiding world wars is variously given to nuclear deterrence, UN institutions, or both; some call UN largely ineffective.
• Debate over whether Russia–Ukraine is a proxy war and whether Ukraine giving up nukes enabled invasion.

YC, Startups, and Defense Industry Structure

• Some see YC’s move into weapons as natural: huge, sticky budgets; inefficient incumbents; government spending rising as % of GDP.
• Others see it as technofascist drift and “working for warlords,” noting Silicon Valley’s long defense roots.
• Clarification that YC has funded defense-adjacent startups before; Ares is distinct for making actual weapons.
• An industry insider describes structural barriers for new defense firms: slow payments, reliance on a single (USG) customer, and procurement rules that favor big, waterfall-style contractors.

Technology, Drones, and Proliferation Risks

• Discussion of cheap cruise missiles/drones potentially creating a “conventional MAD” scenario.
• Some speculate Ares may be closer to low‑cost FPV drones than traditional cruise missiles.
• Worries about second‑order effects: exports to partners (e.g., Israel), use in conflicts like Yemen, and domestic militarization of police, though cruise‑missile use by police is seen as unlikely but not unthinkable.

Fifth Amendment and Legal Framing

• Many argue the Fifth Amendment is misapplied: it protects against compelled testimonial self‑incrimination, not against creation of physical or video evidence while doing one’s job.
• Several note courts distinguish testimony from non‑testimonial evidence (blood, fingerprints, recordings), so body‑cam footage wouldn’t be covered.
• A minority thread explores whether any immunity (e.g., qualified immunity) interacts with Fifth Amendment rights; consensus is that qualified immunity is a civil concept and doesn’t remove criminal Fifth Amendment protections, but remains largely irrelevant to body‑cam operation.

Employment, Public Role, and “Right to Quit”

• Common view: officers are public employees with unique state power; camera use is a job condition, not a constitutional violation.
• If they dislike mandatory recording, they can exercise their “right” by not being police at all.
• Comparisons are drawn to delivery drivers or cashiers under workplace cameras; refusing monitoring means not doing that job.

Body‑Cam Design, Off Switches, and Privacy

• Many question why an “off” button exists, seeing it as designed impunity.
• Counterpoints: legitimate reasons to pause recording include:
  • Victims of sensitive crimes (e.g., sexual assault) not wanting to be filmed.
  • Protecting informants or community sources.
  • Bathroom breaks and occasional personal calls.
• Others counter that:
  • Victim privacy should be handled via strict access controls, not disabling cameras.
  • Informants can’t truly trust “it’s off” anyway.
  • Officers with lethal authority can accept more inconvenience and reduced on‑duty privacy.
• Some suggest technical/administrative solutions (remote-controlled pauses, scheduled break windows) instead of officer‑controlled off switches.

Effectiveness and Limits of Body Cams

• Multiple comments note body cams often exonerate officers against false complaints, raising confusion about resistance.
• Others argue cameras don’t fix the core problem: culture, impunity, and weak consequences even when footage shows misconduct.
• Reference cases are cited where missing or selectively available footage enabled false reports or obscured brutality.

Oversight, Politics, and Reform

• Several emphasize this is fundamentally a policy/oversight issue: city councils and local structures can constrain or remove chiefs.
• Others push back that local engagement can be risky or ineffective, citing harassment, retaliation fears, and “decision already made” experiences.
• Broader concerns surface about police culture, low standards, and incentives to protect power rather than public trust.

Project goals and approach

• Dozer is a Rust compiler written in (portable, minimal) C that targets Cranelift/QBE, aiming to fit into the “from-nothing” bootstrappable toolchain that starts with a tiny C compiler like TinyCC.
• Main motivation: drastically shorten and simplify the bootstrap path to a modern Rust compiler compared to the current chain (Guile → OCaml → early Rust → many rustc versions).
• Intended use is not performance or daily development, but as a bootstrap step that can compile the “real” rustc.

Why C, and why not other languages

• Many argue C is the practical first target because nearly every platform gets a C compiler first, and libraries like Lua are easy to port to minimal C.
• Alternatives proposed: Java, a proto-Rust subset, Forth, WASM+wasm2c, or decompiling rustc output back to C. Critics note:
  • Java bootstrapping is complex.
  • Forth is ideal conceptually but unpleasant enough to program in that no one follows through at scale.
  • Generated C or blobs (like Zig’s wasm stage1) are seen as unauditable and against bootstrappable-build principles.

Security, trust, and reproducible builds

• A major driver is reducing exposure to “trusting trust” style compiler backdoors and supply-chain attacks.
• Bootstrappable Builds ethic: no pre-generated code; everything must be derivable from human-readable source, starting from a tiny binary seed (e.g., hex loader).
• Some see full-chain auditing as still practically infeasible; others argue “more auditable than today” is already valuable.

Practicality, porting, and skepticism

• Use cases discussed: porting Rust to new OSes, where current bootstrapping via many rustc versions and LLVM is painful and time-consuming.
• Counterpoint: for new platforms, cross-compilation often suffices; Dozer specifically targets same-architecture, from-scratch bootstrapping.
• Critics call the effort mostly aesthetic or futile given Rust’s fast evolution and complex language; supporters value the cleaner bootstrap story and educational value.

Project status and limitations

• Current codebase is ~5k lines of C. Lexer and parts of the parser exist; typechecking is minimal (e.g., i32 only); macros/modules and robust codegen are missing.
• It can only handle trivial Rust examples; cannot compile large crates like Tokio yet.
• No substantial test suite is evident; some commenters want clearer test coverage of supported Rust features.

Origin of the term “sharding”

• Consensus that database partitioning long predates Ultima Online; the game is credited mainly for popularizing the name, not the technique.
• Multiple commenters stress the article explicitly says it’s about naming database partitioning “shards” in the game’s lore (a world-crystal split into parallel worlds/servers).
• N-gram and Wikipedia references suggest “database shard/sharding” only appears in print in the 2000s, after Ultima Online (1997), which supports but does not prove the etymology.
• Wikipedia lists two likely sources for the term in databases: Ultima Online and an earlier SHARD system.

Partitioning vs. sharding

• Several comments clarify that sharding is a kind of partitioning, usually:
  • Vertical vs. horizontal partitioning as general concepts.
  • Sharding ≈ horizontal partitioning, often across multiple instances/machines.
• Others use “shard” and “partition” nearly interchangeably and note even Wikipedia is inconsistent.
• One definition: partitioning can be within a single instance; sharding implies separate instances.

Earlier academic and industry uses

• References to an 1980s “SHARD” system (System for Highly Available Replicated Data) and related papers from 1985–1988.
• Difficulties locating some of these papers; at least one person has a copy but is unsure about copyright.
• Some recall “shards” being used informally with DB2 in the 90s, but this could be influenced by either that system or later gaming usage.
• Several comments emphasize the original question is about word origin in DB context, not whether the technique is new.

MMOs and broader tech impact

• Multiple anecdotes that MMOs drove early large-scale distributed systems, sharding, and clever network tricks.
• Ultima Online cited as pioneering in scaling, social systems, and ethics of online communities.
• Other games and virtual worlds mentioned for similar innovations (e.g., per-user or per-world sharding, BitTorrent-based patching).

Ultima Online culture and legacy

• Many nostalgic stories: unofficial “shards,” player-run worlds, heavy social dynamics, PK vs. “carebear” debates.
• Discussion of ongoing freeshards and modern spiritual successors aiming for single shared universes without sharding.

Debugging and engineering war stories

• Memorable debugging tales: using PC speakers as “caveman debugging,” audio cues tied to code paths, Malloc “Geiger counters,” even AM radios for hardware noise.
• Seen as emblematic of the creativity in early game and systems programming.

Scalability and sharding schemes

• Question raised about indefinitely scalable sharding like S3; no definitive answer, but:
  • Examples given of very large sharded deployments (e.g., LiveJournal) using manual user-based shards plus a global lookup.
  • Per-customer databases described as a simple but imperfect scaling approach, with “one huge customer” as a typical stress point.

Meta and information-finding

• Frustration expressed that attention-grabbing posts often mix partial truth and speculation; comments are needed to reconstruct nuance.
• Prior HN threads on the same topic are cataloged; a desire is voiced for better automatic surfacing of related discussions.

High‑cost psoriasis biologics as example

• Bimzelx and similar biologics for psoriasis/psoriatic arthritis can cost six figures annually but target severe, refractory disease, often preventing pain, disability, and joint damage.
• Patients report dramatic quality‑of‑life improvements from alternatives like Taltz, but only after exhausting cheaper, riskier options; foundations sometimes cover huge gaps when insurance refuses or requires “step therapy.”
• Ads focus on “clear skin,” while commenters stress underlying degenerative, painful, and infection‑prone disease.

Insurance, formularies, and access

• Coverage depends heavily on pharmacy benefit managers and formularies; new or “tier 3” specialty drugs are often excluded or carry massive copays.
• ACA out‑of‑pocket caps only apply to formulary drugs; off‑formulary can be effectively uncapped.
• Patients may need to appeal, accept older drugs with worse side‑effect profiles, or rely on manufacturer foundations.

What drives prices? R&D, failures, and marketing

• One side argues the main cost driver is R&D plus the many failed candidates; high prices are needed to justify risky, capital‑intensive investment.
• Others counter that basic science is publicly funded, clinical trials are where private money dominates, and pharma margins ~20% limit how far prices can fall without affecting incentives.
• Disagreement over whether marketing surpasses R&D spend: some cite SG&A vs R&D ratios, others narrower ad‑spend data that show R&D still much larger.

Public funding and “socialized costs, private profits”

• Several note taxpayers fund large amounts of foundational research (e.g., NIH), while private firms capture patent rents.
• Proposals range from: government also funding expensive clinical trials and keeping publicly developed drugs non‑patent, to full public drug development funded by taxes.
• Skeptics say governments avoid full risk and don’t want to run drug production; political will is lacking.

US vs rest‑of‑world pricing

• Common claim: high US prices subsidize lower prices elsewhere where governments negotiate or cap prices; others ask what evidence would actually prove or disprove this.
• One suggestion: require companies to sell in the US at no higher net price than any other developed country, expecting US prices to fall and others’ to rise.

Medicare “negotiation” / price controls

• Critics say the Inflation Reduction Act’s scheme is de facto price control: Medicare can dictate prices under threat of broad penalties, not normal voluntary bidding.
• Cited analysis predicts several “lost” blockbuster drugs over a decade as investment falls; commenters see this as “killing the golden goose.”
• Others favor negotiation as a counter to patent‑backed monopolies and question whether innovation losses would be large or worth today’s extreme prices.

Advertising to consumers and doctors

• Direct‑to‑consumer drug advertising (legal only in US and NZ) is widely criticized as wasteful, distortionary, and contributing to overuse or brand‑switching rather than better care.
• Pharma also spends heavily on influencing doctors via reps, samples, and educational events; defenders see this as necessary information transfer, critics as targeted manipulation.
• Some argue ad budgets “pay for themselves” and thus don’t directly steal from R&D, but others see a Red‑Queen race where competing brands burn money with little social benefit.

Innovation incentives vs equity and access

• One camp: high returns are essential; lower prices mean less VC and fewer risky biotech bets, slowing future breakthroughs.
• Another camp: life‑saving and quality‑of‑life drugs should be treated as public infrastructure, funded and priced like other collective goods, with access prioritized over profit.
• Tension remains unresolved between wanting robust future innovation and broad, affordable access today.

Perception vs. reality of Telegram’s encryption

• Many non-technical users, journalists, and even some techies assume Telegram is fully “encrypted” or e2e by default.
• Commenters stress: only 1:1 “Secret Chats” and 1:1 calls are end‑to‑end encrypted; regular private chats, groups, channels, and desktop/web clients are not.
• Secret Chats are hidden in the UI, can’t be used for groups, don’t sync across devices, and are unavailable or awkward on some platforms, so most real-world use is non‑e2e.

Why people actually use Telegram

• Common motivations: UX, stickers/emoji, cross‑device sync, media handling, bots, large groups/channels, and not having to expose phone numbers to other users.
• Some frame Telegram as closer to Discord/Reddit/Twitter than Signal: a social platform and public broadcast tool, not primarily a secure messenger.

Durov’s arrest, moderation, and censorship

• Several argue his French arrest is about lack of moderation of illegal content (drugs, CSAM, extremist material) in public channels, not about e2e encryption.
• Others view it as pressure to obtain access to data or enforce state censorship.
• There is debate over whether Telegram already cooperates with some governments (Russia, UAE); evidence is mixed and largely “unclear.”

Data storage, metadata, and the “mud puddle test”

• Telegram’s cloud chats are stored on its servers; users can re-login on a new device and see history, so the service can access content.
• This fails the “mud puddle test”: if you can recover data without your own key, so can law enforcement or an attacker with server access.
• Telegram’s claims about split keys and “0 bytes disclosed” are challenged with reports of data handed to German and Indian authorities.

Comparisons with other messengers

• Signal, WhatsApp, Matrix, Briar, Cwtch, SimpleX, Jami, etc. are discussed.
• Signal is widely treated as the “gold standard” for default e2e, but criticized for UX, phone-number requirement, and metadata exposure.
• Matrix offers e2e and self‑hosting but has metadata and UX issues.
• Some argue Telegram is safer “in practice” for some protest/crime use cases (burner SIMs, anonymity of handles); others strongly disagree.

Trust, threat models, and user behavior

• Repeated theme: defaults matter; most people won’t opt into hidden secure modes.
• Several emphasize that if you must reason about the operator’s honesty under legal pressure, you should not treat the system as a secure messenger.

Platform responsibility & moderation

• Central dispute: whether it is “absurd” to hold a platform or its owner responsible for abuse on the platform.
• Critics argue Telegram is a major hub for drug markets, malware, CSAM, and revenge porn, and often ignores takedown requests, citing academic studies and government complaints.
• Others counter that they have successfully reported and had scam/drug channels removed, suggesting uneven or context‑dependent enforcement (public vs private spaces).
• Comparisons:
  • Meta/Facebook/Instagram seen as also full of scams, drugs, and abuse, with weak or inconsistent moderation despite formal policies.
  • Some argue the key difference is that Meta at least claims to enforce rules and cooperates with regulators, while Telegram’s rhetoric denies responsibility.
  • Several note Instagram is identified in research as the primary platform for networks selling illicit sexual content involving minors.

Law, liability & the Digital Services Act (DSA)

• Multiple comments insist EU law does impose duties on platforms regarding illegal content; if Telegram says otherwise, it is either misreading the law or rejecting it.
• Others note the DSA is being invoked rhetorically in Telegram’s defense, but the CEO’s arrest is formally under French law, not the DSA.
• There is debate over whether other large platforms quietly grant governments access to user data and whether non‑cooperation by Telegram is the true irritant for authorities. Claims here are contested and details are unclear.

Durov’s arrest & motivations

• Some see the arrest as selective enforcement or politically motivated, especially given lack of detailed public charges and wartime context (Ukraine–Russia, Russian use of Telegram).
• Others stress that hosting massive amounts of CSAM and other serious crimes in public channels, while failing to cooperate with law enforcement, can legitimately trigger criminal liability, analogized to Tor exit operators hosting abuse content.
• A number of commenters emphasize insufficient information: what exactly Telegram failed to do, which laws were violated, and how French vs EU roles interact remain unclear.

EU messaging apps & regulation vs innovation

• Discussion of whether the EU should or does have its own secure messaging: Matrix, Wire, Threema, and government‑specific systems (e.g., Tchap) are mentioned, but none are seen as a universal EU “official” alternative.
• Broader debate on EU regulation:
  • Critics portray the EU as anti‑innovation, overly protective of incumbents, and hostile to startups, comparing unfavorably to the US.
  • Defenders argue EU rules prioritize workers’ and consumers’ rights over business convenience, and that many Europeans prefer this trade‑off even if it slows some forms of innovation.
  • There is extended back‑and‑forth on social mobility, living standards, and cultural attitudes toward work, risk, and wealth in Europe vs North America, with no consensus.

States vs the internet

• One subthread revives the idea that the internet will ultimately erode state power (censorship, surveillance, control over money and trade).
• Most replies are skeptical, pointing out that physical infrastructure, borders, and coercive power remain decisive, and that state involvement in policing the internet has generally increased, not decreased.

Feasibility of a “Car-Free” 2028 LA Olympics

• Many see the “car-free” branding as unrealistic or marketing spin; expectations range from “overly optimistic” to “politically doomed.”
• Several expect officials to “declare victory” by narrowing metrics (limited areas, time windows, or trip types).
• Others argue even partial success (20–30% car-use reduction) would be worthwhile if it builds lasting momentum for transit.

Transit Infrastructure, Buses, and Metro

• LA is adding rail and planning 3,000 extra buses; some call buses the only scalable option, but note LA’s current system is infrequent, slow, and fragile to disruption.
• Critics say simply adding buses is pointless without bus-only lanes and signal priority.
• The NextGen Bus Plan aims for high-frequency service for most riders, but may neglect lower-demand suburbs.
• Some describe LA buses as poorly signposted and user-hostile compared with “proper” systems abroad.

Cars vs. Transit vs. Bikes

• Multiple anecdotes show biking or transit commutes in/around LA as similar in time to driving, sometimes slower but more pleasant and cheaper (no parking, chance to read).
• Others report LA transit is unsafe or perceived as unsafe; recent moves to create a dedicated Metro police force are mentioned as a response.
• Several argue bikes and e-bikes can outperform cars for many urban trips if given protected lanes and better infrastructure.

Comparisons to Other Cities & Past Olympics

• Paris is cited as a model for reducing car dominance, though some view its changes as dehumanizing or over-controlling; others strongly defend them as clear environmental and quality-of-life gains.
• The 1984 LA Olympics are recalled: feared gridlock never materialized because residents self-diverted.
• Comparisons with Madrid’s much higher ridership and denser rail network highlight how underbuilt LA transit is.

Homelessness, Displacement, and Social Impacts

• Several expect pre-Olympics sweeps of homeless encampments, framed as enabled by recent legal changes.
• Broader criticism targets the Olympics as structurally harmful: cities often bear long-term social and urban costs for short-term spectacle and political “virtue signaling.”