Hacker News, Distilled

Home Assistant–Xiaomi Integration

• New Xiaomi integration connects devices via Xiaomi’s cloud using OAuth; tokens and device metadata are stored in Home Assistant config in clear text, so local config security is important.
• Some argue this isn’t “true” integration because it still requires Xiaomi’s cloud and account; it’s seen more as an official cloud bridge than a local API.
• Partial local control exists but depends on Xiaomi “central hub gateway” functionality, which is region‑restricted and unclear for many users.

Local vs Cloud Control

• Strong preference from many for devices that work fully offline (local control, no vendor servers).
• Users categorize devices as: (1) need internet to work, (2) need internet only for setup, (3) fully local. Many aim for category 3 wherever possible.
• Multiple examples of cloud shutdowns (e.g., Feit, Sylvania) turning “smart” devices into bricks or reduced functionality.

Device Ecosystems: Zigbee, Z‑Wave, Wi‑Fi

• Zigbee and Z‑Wave widely recommended for reliability, local control, and avoiding vendor lock‑in; Zigbee2MQTT is praised for broad device support.
• Some report Zigbee problems (non‑compliant devices, noisy thermostats, mesh complexity) and prefer Wi‑Fi + ESPHome/Tasmota (e.g., Shelly, Sonoff) for mains‑powered devices.
• Concern about Wi‑Fi: firmware quality, phoning home, OTA updates, and 2.4GHz congestion; mitigated via VLANs and firewalls.

Garage Doors and Closed APIs

• myQ/LiftMaster/Chamberlain criticized for closing APIs and adding subscriptions; many recommend alternatives like ratgdo, OpenGarage, Konnected, Shelly relays, or DIY ESP32 + relay solutions.
• Debate over DIY complexity vs. ease of past cloud integrations and cost of professional installation.

Experiences with Home Assistant

• Widely praised as powerful, polished, and central to many smart homes; large integration ecosystem and companion apps (HomeKit/Google Home bridging).
• Also described as complex, programmer‑oriented, and not “set and forget”; issues include upgrades breaking configs, database corruption, and entropy over time.
• Some keep HA usage minimal: only automations (no dashboards), only where vendor apps fall short.

Privacy, Security, and Vendors

• Skepticism toward Xiaomi and Chinese IoT vendors due to ads, potential tracking, and CCP associations, but others point out similar “enshittification” by Western companies (Windows, TVs, Amazon).
• Strong cultural norm in the thread: prefer local, open solutions (Zigbee, Z‑Wave, Tasmota, Valetudo) and avoid cloud lock‑in where possible.

What Modelica Is and Use Cases

• Declarative, equation-based language for modeling cyber-physical systems (multi-domain: mechanical, electrical, fluids, thermals, etc.).
• Used heavily in automotive and motorsports (including F1 and NASCAR), HVAC, and electromagnetic systems.
• Capable of very large models (hundreds of thousands of equations) spanning engines, transmissions, multibody dynamics, hydraulics, etc.
• Can model CNC-like systems and stepper motors, though off‑the‑shelf libraries for niche components may be limited.

Acausal Modeling and Technical Characteristics

• “Acausal” means users specify relationships/equations, not explicit input→output causality; the compiler infers causality and does index reduction, state selection, etc.
• This improves composability: adding components can change optimal causality without refactoring models.
• Under the hood, models become systems of DAEs; strong numerical methods exist, but stochastic systems (SDEs) are noted as a weak spot.
• Supports discrete events and synchronous (clocked) systems directly in the language.

Tooling: OpenModelica, Commercial Tools, and Julia

• OpenModelica is the main open-source implementation; considered close to being a viable Simulink alternative, especially with strong FMU support.
• Dymola is a leading commercial tool; praised for advanced vehicle dynamics libraries but criticized for licensing, bugs, and limited advantages over free tools in some areas.
• Wolfram SystemModeler and some MATLAB products are also Modelica-based or comparable.
• Julia’s ModelingToolkit and commercial JuliaSim adopt similar acausal ideas; JuliaSim adds GUIs and embedded-target work but is proprietary/source-available.

FMUs and Interoperability

• FMI/FMUs are highlighted as a major strength: packaged models can be embedded into other environments (e.g., Python via fmpy, Simcenter, etc.).
• Third‑party support for model‑exchange FMUs on Linux is reported as weak.

Comparisons and Alternatives

• Compared to SPICE/Verilog‑A: Modelica covers more domains and has richer libraries (e.g., multibody, two‑phase fluids).
• Compared to Simulink: Simulink is causal and math‑block oriented; Modelica is acausal and physics‑component oriented. Simscape narrows this gap.
• Compared to SymPy/System Dynamics tools: Modelica is aimed at large, detailed physical models with graphical composition, not generic CAS work or high‑level system dynamics.

Strengths, Limitations, and Pain Points

• Strengths: composability, multi-physics scope, open specification, FMU export, mature standard library, vendor diversity (reduces lock‑in).
• Limitations/pain points: challenging debugging when solvers struggle, weaker stochastic support, inconsistent library coverage for some domains, and incomplete ecosystem vs. Simulink toolboxes.

Documentation, Website, and Accessibility

• Several commenters found the landing page unclear, with merch and logos more prominent than examples.
• Others note that tutorials and “Modelica by Example” are easy to reach after a few clicks.
• Searchability across docs and libraries is considered limited; finding specific models often requires broader web search or conference proceedings.

Related Languages and Research Directions

• Mention of NESTML (for hybrid dynamical systems with events), a new MARCO compiler for large-scale optimization, and discussion of bond graphs, with disagreement on how central they are to Modelica’s conceptual basis.

Perceived impact on SWE roles

• Many expect junior and “code monkey” roles to shrink first; LLMs already handle boilerplate, tests, CRUD, and simple scripts.
• Some argue mid‑level devs also at risk where work is mostly gluing APIs and frameworks.
• Others think all levels (including seniors) are exposed in the long run if “agents” become truly capable; some predict AI‑justified layoffs starting 2025.
• Counter‑view: capable senior devs are unlikely to be replaced by current or near‑term tech; the real scarcity will be people who can own complex systems and make good decisions.

LLMs as tools vs. replacements

• Strong camp seeing LLMs as a major productivity tool: faster scaffolding, tests, refactors, docs, SQL, and learning unfamiliar stacks.
• Opposing camp finds LLMs a net negative: hallucinations, wrong APIs, bad edge‑case handling, and extra review outweigh speed gains.
• Several report that LLM‑generated PRs “work” but are sloppy, inconsistent, hard to explain, and break non‑happy paths—often requiring rewrites.
• Widespread view: current LLMs excel at small, well‑scoped tasks; they struggle with large, messy, multi‑service systems and long‑horizon design.

Business incentives, outsourcing, and layoffs

• Executives and consultants may over‑believe AI hype and cut staff prematurely, using LLMs as a layoff justification.
• Some companies already claim they are freezing or reducing hiring because of AI, though they still recruit engineers in practice.
• Several predict a Darwinian phase: organizations that over‑automate will ship fragile systems, then later pay heavily for consultants and cleanup.

Future‑proofing strategies

• Learn to use LLMs effectively; being the engineer who can steer tools well is seen as protective.
• Move “up the stack”: domain expertise, architecture, requirements, trade‑offs, product sense, and communication with stakeholders.
• Specialize where data is scarce and reasoning is hard: systems, embedded, obscure hardware, scientific computing, security, etc.
• Develop “talent stacks”: combine SWE with SRE, product, a vertical domain (finance, bio, automotive), or people/management skills.

Limits, risks, and long‑term scenarios

• Fundamental limitations cited: lack of real understanding, brittle reasoning, time/context constraints, and unverifiable hallucinations.
• Fear that over‑reliance will erode junior training pipelines, leaving too few future seniors.
• Some see this as another hype cycle like CASE tools, no‑code, or self‑driving; others think we are at the start of a real paradigm shift whose endpoint (up to AGI and broad job loss) is highly uncertain.

Overall Sentiment

• Many commenters find Apple Intelligence underwhelming or pointless in daily use; several have disabled it.
• A minority see clear value in specific features (summaries, notification filtering, writing help), but almost nobody reports it as transformative.
• Some argue that even 20–30% of users finding value at launch could be framed as “success,” but others note the survey data is too vague to interpret cleanly.

Perceived Usefulness of Features

• Commonly liked:
  • Notification / email summaries for catching up on fast-moving threads or triaging long chains.
  • Reduce Interruptions focus and other ML-style classification (seen as “old” AI, but genuinely helpful).
  • Text proofreading / tone softening, especially for non-native writers or people who write aggressively.
  • Occasional coding assistance (mainly via other tools like Copilot/ChatGPT, not Apple’s own).
• Commonly dismissed:
  • Image Playground, Genmoji, and photo cleanup seen as toys or “corny,” often with poor quality or obvious artifacts.
  • Message / mail categorization and summaries are frequently inaccurate or even invert meaning, destroying trust.
  • Visual intelligence is mostly just handing off to ChatGPT or Lens, which users already had via separate apps.

Siri and the “Real Assistant” Gap

• Strong desire for an actually capable, context-aware assistant that can:
  • Orchestrate across apps (calendar, messages, email, notes, smart home).
  • Automate multi-step, real-world tasks (e.g., handling dentist visits, travel, recurring chores).
• Many report Siri remains unreliable, slow, or obtuse even after the Apple Intelligence branding; some say it’s only good for timers.

UX, Reliability, and Performance Problems

• Complaints about:
  • Battery drain and device freezes; some users report stability improving when Apple Intelligence is disabled.
  • Noticeable notification delays due to summarization, including in CarPlay.
  • Terrible onboarding: Image Playground fails with no clear progress indication; weird naming clashes (Playgrounds vs Swift Playgrounds).
  • Awkward UI (unreadable error toasts under the Dynamic Island, confusing controls like “Appearance”).
• Summaries in Messages and notifications often appear without clear indication that they are summaries, causing confusion.

Accessibility and Voice Interfaces

• Several see massive potential for blind or low-vision users if voice control and on-device understanding become robust.
• Current reality is described as “rage-inducing”: touch-only UIs removed autonomy, assistants are flaky, and AI promises aren’t delivered.
• Debate over whether LLMs are actually necessary versus more traditional, deterministic voice interfaces.

AI Hype, Comparisons, and Business Pressure

• Many compare Apple unfavorably to GPT‑4o, Gemini, and other cloud models; Apple’s tiny on-device models are seen as especially weak for summarization.
• Some defend Apple’s slower, more private approach and note prior ML wins (Photos search, autocorrect), arguing “AI” has been there for years without the label.
• Broader discussion about AI hype: companies pushing Copilot and similar tools for stock-market optics and “not missing the boat,” regardless of actual productivity gains.

Desired Future Direction

• Commenters want:
  • Deep, invisible integration where AI quietly improves notifications, search, Shortcuts, and app-to-app workflows.
  • Less emphasis on gimmicky generative features and more on reliable, agentic OS-level assistance.
  • Clearer affordances: what AI can do, where it’s active, and strong controls to disable specific behaviors (e.g., message suggestions) without killing everything.

Article reception & readability

• Many found the essay interesting but overlong, rambling, and light on actionable conclusions; others thought it was absolutely worth reading and consistently insightful.
• Common complaint: the page is an unstyled, full‑width wall of text with giant paragraphs, making it “designed to be unreadable,” especially on large monitors.
• Defenders argue the bare HTML is intentional: fast, accessible, easy for reader modes and tools; critics say minimalism shouldn’t mean zero typography and that a single max-width line of CSS would greatly help.
• There’s extended debate over writing style: some see it as unedited and dense; others see it as highly deliberate, prioritizing nuance and many examples over “clean” essays or short takes.

Why things (and software) don’t work well

• Commenters link the article’s examples to broader “enshittification”: marketing and sales optimized over actual quality; trust and honesty not enforced culturally; products that only have to be “just good enough” to keep selling.
• They highlight information asymmetry: buyers often lack expertise (accountants, dentists, JS libraries, SaaS, appliances), can’t reliably evaluate quality, and face corrupted signals (fake reviews, SEO, affiliate content).
• Several connect this to the “market for lemons” and the Vimes “Boots” theory: poor people or time‑pressed buyers end up repeatedly buying cheap, mediocre goods.

Markets, incentives & organizational culture

• Many push back on simplistic “efficient markets” stories: real markets tolerate large inefficiencies, especially under monopolies/oligopolies, high switching costs, and bad information.
• Econ‑101 models are criticized as a kind of “secular religion” that ignores transaction costs, power, and incomplete information.
• Anti‑trust and concentration (Big Tech, app stores, cloud) are repeatedly blamed for declining product quality and lack of incentive to improve.
• Inside firms, webs of mistrust and politics are likened to Prisoner’s Dilemmas/Nash equilibria: without leadership that enforces honesty, fiefdoms optimize for self‑protection, not quality.

Build vs buy, software ecosystems, and JS

• The discussion reinforces the article’s build‑vs‑buy theme. Many describe buying SaaS/low‑code tools that look great on paper but are fragile, misleadingly marketed, and hard to integrate.
• Others note that in huge, noisy ecosystems (especially JavaScript/npm), popularity metrics (stars, downloads) are poor quality indicators; winners are often chosen by marketing, hype, and “being top of mind,” not engineering quality.
• Some engineers respond by re‑implementing things themselves, building small internal libraries, or vertically integrating, accepting higher upfront cost for long‑term control and reliability.

Buyer coping strategies

• Suggested heuristics:
  • Read 1‑star reviews to detect systemic issues.
  • Judge libraries by docs, issue churn, and maintainer history rather than stars.
  • Buy older, proven models or used gear (cars, tools, appliances, audio) that have “passed the test of time.”
  • Buy less overall, or buy cheap first and upgrade only if you actually wear something out.
• Many note this still often fails: brands quietly cost‑cut, models change quickly, and even expensive products (cars, mice, laptops, B2B software) can be deeply compromised.

AI and “will this fix it?”

• One commenter asks if AI can solve the selection problem by assessing who/what is “good.”
• Most replies are skeptical or negative: AI is seen as likely to widen understanding gaps, accelerate disposable products, and become yet another overhyped “panacea” narrative (like blockchain before it), rather than structurally improve quality.

Article tone & framing

• Some see the piece as flippant and jingoistic about nuclear deterrence and China; others find it level‑headed, factual, and refreshingly low on overt opinion.
• Disagreement over whether highlighting Chinese missile‑sub threats while noting larger US numbers is fear‑mongering or just context.
• Several note these “stealth is dead” stories reappear with political cycles and can serve defense‑industry agendas.

Submarine roles, numbers, and AUKUS

• Participants stress most subs are for conventional sea control and anti‑shipping, not just nuclear armageddon.
• Clarifications: US has ~67 nuclear subs vs ~12 Chinese nuclear boats (per article), not “thousands.”
• Long debate over AUKUS:
  • Pro‑nuclear view: Pacific distances and Australia’s desire to operate far north (South/Philippine Seas) make nuclear subs’ speed and endurance essential; AIP boats are great near Europe but under‑ranged for the Indo‑Pacific.
  • Skeptical view: Nuclear boats are extraordinarily expensive, low in numbers, slow to reload, and may be increasingly vulnerable as ASW sensors and drones improve; money might buy more effective missile and air capabilities instead.

Stealth vs detection: physics and tactics

• Many argue subs will remain viable: oceans are vast, thermoclines and complex water properties make detection hard, and any ML/AI advances benefit both sides.
• Others think quieting is nearing physical limits while sensing keeps improving, pushing the contest toward camouflage and decoys rather than pure silence.
• Ideas discussed: active acoustic camouflage, cheap noisemaker and decoy subs, drone swarms, and sensor‑saturation tactics.

Drones, unmanned systems, and comms

• Strong interest in large autonomous underwater vehicles (e.g., Orca XLUUV) as cheaper, persistent strike or drone‑carrier platforms that may erode carrier and manned‑sub dominance.
• Counterpoint: long‑range, covert underwater communication is fundamentally hard (EM absorption, need for buoys/tethers or acoustics), making truly remote‑controlled deep drones problematic.
• Debate over fixed tether networks and passive sensor grids vs vulnerability and “dark forest” dynamics.

Technology, terminology, and misc

• Several object to vague “AI-enabled” claims; prefer precise references to machine learning and specific DSP methods.
• Comments touch on alternative detection (gravity, magnetic anomaly detectors), nuclear propulsion noise vs diesel‑electric quietness, and even map color choices in the article.

Alleged 4090 “Nerf” and Why It Exists

• Claim: AD102 dies (RTX 4090) have an eFuse blown that halves FP16-with-FP32-accumulate throughput vs the RTX 6000 Ada, which uses the same die.
• Debate whether this is:
  • Pure market segmentation to protect high-margin data-center SKUs.
  • Or conventional binning: parts that fail as RTX 6000s get sold as 4090s with features disabled.
• Some argue binning and segmentation are intertwined: even flawless chips may be disabled to maintain product tiers.

Nvidia’s Moat vs Intel’s Old Moat

• Comparison with Intel’s past dominance: Intel relied heavily on process-node advantage and x86 software lock-in, which eventually eroded.
• Several comments argue Nvidia’s moat is deeper: repeated “paradigm changes” (SIMT, tensor cores, FP8, upcoming FP4) and fast iteration while competitors lag a generation or more.
• Others note Nvidia is fabless, so less exposed to process-node stagnation than Intel was.

CUDA, Software Stack, and AI

• Disagreement on whether Nvidia’s advantage is mainly hardware or software.
• One side: AI developers mostly use PyTorch/JAX/etc., so CUDA is less visible; alternative backends (TPU, Apple GPUs) show portability is possible.
• Counterpoint: these frameworks still depend on proprietary cuBLAS/cuDNN; duplicating their performance is seen as very hard, reinforcing Nvidia’s software moat.

Pricing, Segmentation, and Economic Arguments

• Some see artificial throttling as wasteful and “greedy,” reducing output from the same silicon.
• Others defend segmentation as enabling:
  • Cheaper gaming cards that still meet gamers’ needs.
  • Higher margins that fund R&D and new nodes.
• Debate whether consumer GPUs are cross-subsidized by data-center profits or vice versa; consensus: lack of competition lets Nvidia charge very high markups.

eFuses, Unlocking, and Modding Prospects

• eFuses described as one-time programmable bits in silicon; once “blown,” practically impossible to reverse.
• Firmware-based workarounds are blocked by signed firmware; past accidents (like hash-rate limits) depended on Nvidia itself releasing permissive firmware.
• Some speculate about far-future “garage” chip surgery, but others consider practical restoration of such fuses effectively impossible.

Competition and Alternatives

• Many call for stronger AMD/Intel competition; others note AMD’s weak software story (especially for ML) and Intel/AMD’s smaller innovation cadence.
• Cloud TPUs, Trainium, Gaudi, and others are mentioned as partial alternatives, but availability and ecosystem limits keep Nvidia dominant.

Overall reaction to “Code Yellow”

• Many see the described “Code Yellow” usage as extreme and disproportionate, especially when invoked for missing growth or sales targets rather than existential outages or safety issues.
• Several commenters interpret it as an attempt to normalize mandatory overtime and constant crunch, framed as “grit” or “sweating the problem.”

Comparison with real incident management

• People working in healthcare and other critical sectors compare “Code Yellow” to genuine major incidents where outages directly affect safety; they argue those justify all‑hands responses, but missed KPIs do not.
• Former incident managers note that once a crisis process is the only way to get things done, organizations are tempted to declare “emergencies” for everything, which is seen as process and leadership failure.

Google-style priority codes

• Commenters describe internal schemes with Code Red/Yellow/Purple/Green, with explicit definitions (e.g., Red = active severe harm; Yellow = 3–6‑month existential risk).
• In that context, such codes require senior sign‑off and are rare, not routine; they are meant to override politics and drop other commitments, not to punish teams.

Work–life balance and ethics

• Strong criticism of statements about “sacrificing the ‘L’ and ‘B’ in work‑life balance” and writing crisis emails during children’s events.
• Multiple comments emphasize that work should support life, not the other way around, and that lost family time is irreversible.

Management, prioritization, and culture

• Many argue repeated “Code Yellows” signal poor planning, weak prioritization, and an inability or unwillingness to make trade‑offs earlier.
• Some see it as a blunt but sometimes useful political tool to cut through bureaucracy and org charts when a truly critical issue is otherwise blocked.
• Others point to high executive churn and recurring crises as signs of deeper dysfunction and “hero culture,” where visible firefighting is rewarded more than building resilient systems.

Incentives and employee perspective

• Commenters question why rank‑and‑file staff should comply without substantial compensation (bonuses, PTO multipliers).
• There is concern that, under pressure to “sweat,” employees will cut corners or quietly disengage rather than truly buy in.

Education and school use

• Some expect more free literature for schools; others argue curricula already rely heavily on public-domain works and cheap editions, so little change.
• Schools’ tight budgets make it hard to replace sets of books with new copyrighted titles.
• Drama programs sometimes pay hundreds or thousands for popular branded plays, even when public-domain alternatives exist; motivations range from student interest and “safe” appeal to accessibility and ease of working with modern scripts.

What actually enters the public domain

• Only works from 1929 are affected now (e.g., early black‑and‑white Tintin, early Popeye), not later color editions or later character developments.
• Later revisions added substantial changes (e.g., updated technology, color, reputation “rehabilitation”), which remain under copyright.
• Some details matter: the public‑domain Popeye predates the spinach gimmick, and only the earliest Mickey design is free; newer visual traits remain protected.
• Trademarks do not expire, so character names and branding can still be legally sensitive.

Jurisdiction and legal complexity

• Users discuss that early Tintin becomes public domain in the US but not in the EU/UK, where terms are longer (often life+70).
• A derivative made lawfully in a short‑term country might infringe if exported to a long‑term country.
• For sound recordings, US federal and state rules create extra complexity, with some unpublished recordings under state law.

Derivative works, parody, and horror adaptations

• Public domain enables non‑ or minimally‑transformative uses (e.g., accessibility edits, straightforward sequels) that would be risky under fair use.
• Very transformative horror parodies (e.g., slasher versions of children’s characters) probably could have existed under fair use even before expiry; opinions differ on how strong that defense would be.
• Participants expect more remixes, games, and films using newly free characters; some cite existing Tintin parodies and fan comics.

Tintin fandom, nostalgia, and critique

• Many express deep nostalgia for Tintin, Asterix, and related European comics used both for pleasure and language learning.
• Others highlight racist and stereotyped depictions in early Tintin and similar works, seeing them as “of their time” yet uncomfortable now.
• There is interest in “modernized” or edited versions that soften problematic content, though some note this can effectively reset copyright.

AI and style issues

• People anticipate an explosion of AI‑generated Tintin‑style art once legal risk drops.
• Some image models already approximate the “ligne claire” style; others historically struggled.
• Major AI services enforce style and copyright safeguards, refusing prompts that directly mimic certain named artists, though open‑source models or fine‑tuning can bypass this.

Copyright duration debate

• Multiple commenters argue current terms (e.g., life+70, 95‑year corporate terms) are excessive, favor large rightsholders, and slow cultural reuse.
• Suggested alternatives range from 25–30 years for most works to differentiated terms by medium (shorter for films/software, longer for books).
• Others note that international treaties and EU harmonization, not just one company’s lobbying, drove long terms; some point to strong publisher interests in countries like Germany.

Project concept and feasibility

• Original article proposes reusing the Nokia 5110’s separate UI board (screen, keypad) with a new 4G modem+MCU board inside the old case.
• Several commenters say this is effectively building a new phone that just reuses case/buttons/display, not “just” swapping a modem.
• Many note that the promised “Part 2” never arrived (over two years later), reading this as evidence the task was harder than presented.
• Prior art is mentioned (e.g., DIY phones and kits) showing it’s possible in principle, but time‑consuming and non‑trivial.

Technical details: modems, VoLTE, and architecture

• Old feature phones often used a single CPU for both UI and radio; newer designs typically use modular 4G modems accessed via AT commands over serial/USB.
• For modular designs, a 4G module can sometimes present calls/SMS in a 2G‑like way, but VoLTE compatibility and carrier quirks complicate things.
• Several point out 4G voice is SIP/VoIP over a prioritized data channel (VoLTE); some argue it’s “proper” telephony, others criticize poor standardization and whitelisting.
• One commenter clarifies the project’s approach: replace the whole logic/radio board, not re‑use the original firmware.

Networks, shutdowns, and e‑waste

• 2G is gone or going in many western markets (notably North America and Australasia) but persists in parts of Europe and elsewhere.
• 3G shutdowns (e.g., Australia, parts of Europe) are causing problems: VoLTE‑incompatible or non‑whitelisted phones become unusable for voice, creating e‑waste.
• Some still successfully use old 2G phones where 2G remains and legacy SIMs are still valid.

Nostalgia and modern “Nokia” issues

• Strong nostalgia for 5110/3210/3310/6310‑era devices: robustness, week‑long battery life, instant boot, simple UI, and memorable models like n900, E‑series.
• Several want a 5110‑like phone with modern LTE/VoLTE and a modern battery, preserving the old UI/feel.
• Multiple reports that current Nokia‑branded feature phones (by HMD) feel cheap, have buggy firmware, poor call quality, and short lifespans; others report acceptable or good experiences, so quality is viewed as inconsistent.

Alternatives and “dumbphone” recommendations

• Commenters discuss modern rugged or minimalist phones (Sonim, AGM, CAT, etc.) as partial replacements: calls/SMS, hotspot, sometimes Android Go and sideloading, but not week‑long battery.
• Trade‑offs: availability by region, VoLTE support, band compatibility, price, and vendor support (some brands’ makers have gone bankrupt).

Regulator, Law, and Democratic Context

• Debate over Ofcom’s independence: some say it has wide operational leeway and quasi‑independent status; others argue the Secretary of State and political conventions make that independence mostly nominal.
• The Act is described as high‑level and vague, with Ofcom to define platform‑specific codes after consultation.
• Several commenters note no major UK party opposed the law and that public opinion generally supports tougher rules on social media, especially for children.
• Extended side‑discussion on UK electoral flaws (FPTP, safe seats, lack of proportionality) and whether outcomes have real “popular support.”

Free Speech, “Harm” and Hate Speech

• Strong criticism that “harmful” and “psychological harm” are elastic concepts that can be used to censor unpopular or political speech, with examples of UK prosecutions over tweets, posts during riots, and “non‑crime hate incidents.”
• Others respond that the Act targets specific illegal harms (terrorism, CSAM, fraud, incitement to suicide, etc.), not generic “offensiveness,” and that existing UK tradition accepts more limits on speech than the US.
• Concerns about chilling effects: fear of selective enforcement, speech‑crime prosecutions already in the thousands per year, and comparisons (for and against) with Russian “extremism” laws.

Child Safety, Age Verification, and Parental Role

• Many argue social media is demonstrably harmful for many children (grooming, bullying, extremism, scams, eating‑disorder and pro‑suicide communities), and parents strongly back regulation.
• Others counter that bad parenting and lack of supervision are the real problems, and that “protect the children” is used to justify mass ID checks and erosion of anonymity, enabling broader political control.

Impact on Platforms, Small Sites, and Decentralization

• Large platforms are expected to absorb compliance; some think they quietly welcome regulation that raises barriers to entry.
• Hobby forums, Mastodon instances, and niche communities fear huge compliance burdens and potential £18m fines; some operators plan to block UK users entirely.
• Discussion of decentralized/federated or E2E‑encrypted systems: unclear how the Act can be enforced against them; some developers consider excluding UK customers or relying on VPNs.

Broader Trajectory and Reactions

• Many posts frame the Act as part of a wider authoritarian drift in the UK (speech prosecutions, protest crackdowns, data retention, AML/KYC analogies).
• Others see it as a pragmatic, imperfect but necessary response to scams, extremism and social media harms, emphasizing that the UK has never had US‑style absolutist free speech.
• Some high‑earners and technologists say they are leaving or considering leaving the UK over high taxes plus increasing surveillance and regulation.

Responsibility for Sweden’s Energy Problems

• Many argue Sweden’s issues are primarily self‑inflicted: shutting reactors, under‑investing in grid capacity, and choosing to participate in the EU power market.
• Others see Germany’s nuclear exit and reliance on gas/coal as a major external driver of high regional prices, exacerbated by interconnection.
• Some say the minister is using Germany as a political scapegoat; others note she has long pushed for more nuclear and only recently gained power.

Nuclear Phase‑Out Debates (Sweden & Germany)

• Sweden: 6 of 12 reactors closed since 1999; debate over whether this counts as a true “phase‑out” or just reduction / non‑replacement at end‑of‑life.
• Germany: sharp split between those blaming Greens for anti‑nuclear ideology and those arguing long‑ruling centrist parties made and maintained the key decisions (including Nord Stream).
• Pro‑nuclear side: sees nuclear as low‑risk, low‑CO2, essential to replace fossil baseload and enable renewables; criticizes Germany’s high emissions and coal use.
• Skeptics: highlight huge build costs, debts (e.g. utility finances), long lead times, waste and accident risks; argue new nuclear is now economically worse than rapidly falling‑cost renewables plus storage.

EU Market, Price Zones, and Exports

• Sweden and Norway are net exporters but still face very high domestic prices due to marginal pricing and EU rules requiring most capacity be available to the market.
• Southern Sweden and Denmark pay more due to zonal pricing and limited transmission; proposals include more granular zones near interconnects to decouple local prices from continental spikes.
• Some suggest leaving or limiting the EU market; others prefer windfall taxes, profit‑sharing, or redesigning zones instead of “cutting the cables.”

Grid Infrastructure & North–South Constraints

• Big structural issue: most Swedish hydro is in the north, most demand in the south; north–south lines are insufficient.
• Simply “laying more cable” is contested: critics cite the need for local inertia (large rotating machines), system losses, environmental permitting, and huge capex.
• Question whether more internal capacity would mainly equalize Swedish prices with Germany rather than ease them.

Privatization, Markets, and Public Utilities

• Several comments blame liberalized, pseudo‑competitive electricity markets: separation of grid and generation, mock auctions, and profit‑maximizing exports over domestic affordability.
• Others push back, noting core Swedish transmission remains public and pointing instead to political decisions on capacity, zoning, and plant closures.
• Broader skepticism about privatization of essential utilities (energy, water); UK water is cited as a negative case (leveraged buyouts, under‑investment, debt shifted to ratepayers).

Renewables, Storage, and Technology Choices

• Consensus that wind and solar expansion has outpaced investment in storage and grid‑scale balancing.
• Storage views diverge:
  • Some say battery and storage costs are dropping fast, poised for a similar inflection as solar/wind; CO₂ pricing will make storage arbitrage more attractive.
  • Others doubt large‑scale batteries, favoring gas/“green gas” or hydrogen, and emphasize efficiency limits and material intensity of storage.
• Debate over whether renewables plus storage can realistically replace fossil and nuclear in the next 10–30 years or whether nuclear must be expanded in parallel.

Social and Equity Concerns

• Multiple comments stress that high prices hit households and industry hard: colder homes, reduced spending, struggling energy‑intensive firms, and calls for compensation.
• Some see current policy mix as de‑industrializing Europe and benefiting Chinese manufacturing.
• There is frustration that states and utilities profit from exports while domestic users shoulder volatility.

Article & Site Presentation

• Many readers found the blog page nearly unreadable due to CSS (e.g., forced word-breaking), on both mobile and desktop.
• Several note the article is largely a curated email thread from the Python mailing list.
• Some claim parts of the article are inaccurate or confused (e.g., multiple NumPy versions in one process, Jupyter/kernel behavior, “current directory” module shadowing being unrelated to Conda).

Conda: Pain Points

• Frequent complaints about extremely slow and sometimes “stuck” dependency resolution, especially with conda‑forge and larger environments.
• Mixing conda and pip in the same environment is widely viewed as a major source of breakage.
• Some describe Conda environments as fragile when shared or reproduced across machines; others say it works fine if you treat envs as disposable and recreate from YAML.
• Newer libmamba-based solving is reported as faster, but several still consider performance bad.
• Some avoid Conda entirely due to prior bad experiences or due to new licensing limits for large companies.

Conda: Strengths & Use Cases

• Strong support for Windows and compiled scientific stacks was the original killer feature (SciPy/NumPy, CUDA, GDAL, etc.).
• Handles non-Python dependencies and multi-language stacks (C/C++/Fortran, R, Java, Node, command-line tools), which pip/PyPI generally do not.
• Popular in bioinformatics and scientific computing because it can install almost all domain tools from one ecosystem.
• Seen as valuable for corporate environments needing central control, mirroring, access policies, and reproducibility.

Alternatives & New Tools

• Many users now prefer uv for Python-only workflows: very fast, PEP-compliant, and a potential replacement for pip/poetry/pipx.
• pixi is highlighted as “Conda done right”: project-local environments, fast solving, conda-style binary ecosystem plus PyPI via uv.
• mamba is recommended as a drop-in, faster Conda CLI.
• Nix (and tools built on it) is praised for cross-language, fully reproducible environments, sometimes replacing Conda altogether.

Broader Python Packaging Debate

• Many see Python packaging as unusually fragmented (pip, venv, conda, poetry, etc.) and historically under-designed compared to ecosystems with a single “blessed” tool.
• Others argue venv + pip (and now wheels) are adequate for many projects, especially outside Windows and heavy scientific/ML workloads.

Ownership, Auctions, and Museums

• Many see the manuscripts as artifacts that “belong in a museum,” given de Gaulle’s status.
• Others note they were found in a safe belonging to his son, so heirs have legal and moral claims.
• French museums can preempt auction sales, using auctions to set market value and then buying with public funds.
• Concern over “a portion” of proceeds going to charity: some suspect the majority will go to heirs and auction intermediaries.
• Several argue that being descendants of a “founding father” should incline the family toward prioritizing public interest over profit.

De Gaulle, Leadership, and Modern Politicians

• Commenters highlight de Gaulle’s willingness to sacrifice for the country, contrasting him with today’s more businesslike, media-driven politicians.
• Some attribute his character to wartime hardship; others counter that hardship alone doesn’t reliably produce moral leaders.
• Debate over whether military figures in politics were an exceptional product of WWII or part of a broader historical pattern.

Honor and Military Ethics

• De Gaulle’s rhetoric about “honor” prompts reflection on how rarely modern politicians use such language.
• Discussion contrasts broad, moral notions of honor (including conscience and limiting wartime brutality) with narrow, procedural definitions in some military documents.
• German and US perspectives on “honor” are compared; ambiguity remains over formal US definitions.

French Constitution and Political Stability

• Significant back-and-forth on whether the Fifth Republic’s strong presidency is a stabilizing legacy of de Gaulle or a root cause of current dysfunction.
• One side: the Third and Fourth Republics were chronically unstable; a powerful presidency is needed for long-term policy.
• Other side: current issues (no parliamentary majority, weak coalition culture, synchronized elections) show that the system discourages compromise and over-centralizes power.
• Disagreement over whether instability is mainly constitutional or a broader political/cultural problem; no consensus.

Colonialism, Algeria, and Historical Judgment

• De Gaulle is praised for resisting US dominance and ultimately granting Algerian independence, and for facing a military coup.
• Others stress his complicity in a brutal colonial war involving torture and repression; parallel critiques raised for Churchill and FDR.
• Tension between acknowledging major contributions (e.g., anti-Nazi resistance) and confronting racist policies and colonial atrocities.
• Some argue it’s hard to judge past figures by modern moral standards; others insist contemporaries already recognized colonialism and racism as wrong.

Immigration, ‘The French People,’ and Culture

• Extended debate on what “the French people” means: citizenship and shared political community vs. something closer to ethnicity.
• In French legal/political usage, it’s described as citizens/nationals, not race; in English, some hear ethnic implications.
• Historical examples of Italians, Armenians, Spaniards, Portuguese assimilating are used to argue that today’s migrants will similarly become “fully French.”
• Others question whether large Muslim populations can or will assimilate into a secular-liberal framework, citing value conflicts.
• Some defend protecting “Frenchness” as preserving a culture, analogizing to protecting Indigenous cultures in Canada; critics label this as veering into “Great Replacement” thinking.
• Disagreement over whether assimilation is breaking down in recent generations and how much that matters for national identity.

Overview of OpenERV Discussion

• Decentralized, through-wall/window Energy Recovery Ventilator (ERV) using 3D‑printed parts.
• Widely seen as a clever, much-needed product category: “open window” freshness without throwing away heating/cooling energy.
• Many users already monitor CO₂ and report big comfort/productivity gains from ERVs in general.

How It Works: Regenerative vs Counter‑Flow

• OpenERV uses regenerative heat exchange: one core alternately sees exhaust and intake air, with flow reversing every ~30s.
• Heat (and optionally moisture via sorbents/desiccants) is stored in the core then released when direction flips.
• Contrasted with traditional recuperative/counter‑flow cores (two separate airstreams separated by thin walls).
• Some confusion on how >80–90% efficiency is possible; others explain temperature gradients along the core and analogies to countercurrent exchange in biology.
• Some skepticism about claimed efficiencies until independent Passive House–style lab tests are available.

Use Cases, Climate, and Humidity

• ERVs/HRVs common or code‑mandated in many cold‑climate regions and newer European/North American builds.
• Strong debate on humidity:
  • Some say ventilation is primarily to remove moisture (avoid mold).
  • Others report extremely dry indoor air in winter even with poor ventilation, needing humidifiers.
  • Effectiveness and goals vary by climate (very cold/dry vs humid vs UK‑style damp).
• Desire for smart control: switch between heat‑recovery and simple ventilation depending on season and temperature delta.

Indoor Air Quality & Filtration

• Primary motivation: reduce CO₂ and indoor pollutants (VOCs, combustion byproducts, off‑gassing).
• Outdoor air is usually lower in CO₂, but particulate quality varies; people near highways or in polluted cities worry outdoor air is “not worth” bringing in.
• OpenERV can accept HEPA and carbon filters, but options differ between models; some see filtration as essential.

Cost, Noise, and Comparisons

• Many note commercial single‑room units from established brands at similar or higher price points; often installation dominates cost.
• Debate over BOM cost and potential for ultra‑cheap mass‑manufactured versions vs artisanal 3D‑printed units.
• Noise figures (~37–42 dBA at substantial flow) are discussed; some think this is quiet, others fear it’s too loud for bedrooms.

“Open Source” Status and DIY Friction

• Files (STLs, STEP, firmware) are published under CC BY‑NC‑SA, which several commenters state is not OSI‑compliant “open source.”
• Key scripts and detailed BOM/assembly instructions are perceived as incomplete or printer‑specific.
• Some feel the site discourages DIY and is more marketing for a semi‑closed product; others note the intent is maintainability/repair, not cloning.
• Interest in forking or making a more community‑driven DIY variant, but no clear effort yet.

Safety and Reliability Concerns

• Questions about condensation, mold, and Legionella; consensus that design/hygiene and proper drainage or sorbents matter.
• Warnings that DIY ventilation can damage buildings or health if done poorly.
• Unclear how units behave on power failure or one‑sided failure (possible unwanted passive air paths).

Free speech, censorship, and constitutionality

• Many see the TikTok divest-or-ban as a major First Amendment issue: banning a platform where people speak is argued to be functionally restricting speech, especially given TikTok’s scale and network effects.
• Others argue speech isn’t banned, only one distribution channel; users can move to Instagram, YouTube, etc., and governments are not obliged to “facilitate” specific platforms.
• Some point out prior U.S. cases: banning foreign propaganda has historically run into constitutional limits, but recent courts have upheld the TikTok law on national security grounds. Several commenters expect the Supreme Court to be decisive.
• There’s extensive debate over whether this is “censorship” or a commercial/ownership restriction on a foreign adversary’s media asset.

National security, propaganda, and “brainworms”

• Supporters frame TikTok as a CCP‑influenced “brainworm”: an addictive, algorithmically curated channel a hostile state could use for propaganda, election interference, or undermining U.S. military recruitment and social cohesion.
• Critics say there’s no public evidence of concrete CCP manipulation beyond what any platform could do, and that U.S. media and platforms already engage in heavy narrative‑shaping and government‑aligned moderation.
• Some tie the timing to pro‑Palestinian content and perceived loss of narrative control on Gaza/Israel, arguing this is about suppressing dissenting foreign-policy views. Others deny this and emphasize broader China rivalry.

Reciprocity, geopolitics, and precedent

• A popular pro‑ban argument: China blocks or tightly controls U.S. platforms; reciprocity justifies blocking Chinese apps.
• Opponents respond that mirroring authoritarian controls undermines U.S. claims to be “freedom‑oriented” and risks a slippery slope to a Western “Great Firewall.”
• Several note this aligns with earlier moves against Huawei and foreign-owned media, and may expand as a general rule against “foreign adversary–controlled” apps.

Data, algorithms, and platform power

• Some focus on data exfiltration: even if TikTok stores U.S. data on U.S. clouds, Chinese law can still compel access. Others counter that the same structural concern exists for U.S. companies abroad.
• Several say the real issue is the opaque recommendation algorithm: foreign control over what goes viral is seen as more dangerous than raw data access.
• A minority argues the logical response would be algorithmic transparency and cross‑platform rules, not a China‑specific ban.

Social media harms and broader tech policy

• Many commenters think all major social platforms (Reels, Shorts, X, etc.) are addictive, polarizing, and socially corrosive; singling out TikTok is viewed as protectionism for U.S. tech.
• Others welcome any blow to TikTok specifically, especially for youth mental health, while acknowledging the move does nothing about Meta/Google/X.
• There’s debate over sideloading, web apps, VPNs, and whether this will meaningfully reduce usage or just shift attention to domestic “brainworms.”

Study design and cross-country comparisons

• Commenters link the OECD report and note that many countries show declines, with some (e.g., Poland, Lithuania, Korea) dropping more than the US.
• Several argue cross-country comparisons are weak because questions are culturally loaded; within-country trend changes may be more meaningful.
• One notes US has high non-response bias and cautions that sampling 16–65, with scores falling with age, may leave residual bias despite weighting.

Score declines and which adults are affected

• The largest drops are in older adults (55–65).
• Some argue this doesn’t match explanations focused on current schooling methods or social media use, since those cohorts left school long ago.
• Others suggest compositional effects: increased immigration including older adults with limited formal education may depress averages. This is disputed and flagged as speculative.

Debate over the sample literacy question

• Much discussion centers on the “crackers become soft at 9% moisture” item.
• Some say this is trivial and the issue is poor schooling and reading instruction methods.
• Others focus on wording nuances: “seem” vs “become,” “about” 9%, and the mismatch with real-world reasoning, arguing tests reward pattern-matching over genuine comprehension.
• A subthread questions whether syntax like “At what moisture level…” is actually complex or just unfamiliar; some note people may parse inverted word order poorly.

Test implementation and user experience

• Multiple commenters try the OECD demo tests and describe the interface as janky, confusing, and outdated (including a Firefox-only notice).
• A few find the items straightforward once the UI is understood; others say the UX itself could depress performance.

Possible causes: COVID, media, technology, and AI

• One line of discussion proposes COVID-related neurological effects as a contributor; others see this as plausible but unproven and point instead to broader pandemic-era social and psychological disruption.
• Social media and mobile devices are blamed by some for eroding sustained attention and deep reading; others insist this needs rigorous study rather than repetition.
• Several worry that ubiquitous LLMs could further atrophy reasoning if people offload thinking too quickly, while others note that if reasoning becomes rarer it might also become more economically valuable.

Alternative interpretations and skepticism

• One commenter argues the data do not show people “getting stupider” but reflect cohort differences (e.g., schooling during turbulent vs more stable eras) and a shift toward audio/video learning that tests don’t capture.
• Another initially dismisses the test as irrelevant to modern information work, then retracts somewhat after trying it, criticizing implementation more than the conceptual goals.

Assessment formats and AI use

• Many courses rely mostly on papers, projects, and presentations rather than proctored exams; some universities reduced or removed exams during Covid and never restored them.
• Others report traditional models with midterms, finals, in‑class essays, language interviews, and problem‑solving exams still dominant.
• Proposed countermeasures: handwritten in‑class essays, paper‑and‑pencil or air‑gapped lab exams, oral exams/interviews, orals at scale using AI assistance, and weighting exams more heavily to offset easy homework cheating.
• Major constraint: time and labor for oral or closely proctored assessment, especially with large classes and limited TA support.

What counts as “cheating” with AI

• Described spectrum: brainstorming topics, outlining, polishing prose, full drafting, paraphrasing tools, grammar checking, or using AI to explain readings.
• Humanities educators in the thread tend to see AI‑assisted writing as cheating; some science/technical educators are more open if the ideas and analysis are original.
• Participants highlight a large unresolved gray area and call for clearer definitions (e.g., AI‑generated then edited vs. human‑written then AI‑edited).
• One suggestion: require students to submit prompts as part of grading to expose how AI was used.

Detection tools and their limits

• Turnitin plagiarism detection is variously described as:
  • Expensive with many false positives and reliance on crude similarity metrics.
  • Still useful for catching blatant copying and paraphrasing.
• AI‑detection is widely viewed as unreliable “snake oil,” with concerns about:
  • High false‑positive rates (including non‑native speakers).
  • Lack of independent validation of accuracy.
  • Arms‑race dynamics as prompts/styles change.
• Newer tools that record the writing process (keystrokes, edits) are described; they may work now but raise evasion concerns, privacy/FERPA issues, and face adoption barriers (apathy, red tape, cynicism).

Learning, incentives, and ethics

• Some students use AI to save time or clarify material; others may bypass learning entirely.
• Debate over analogy to calculators: baseline skills are seen by some as essential to later understanding and to critiquing AI output; others argue much hand‑work is unnecessary busywork.
• Several comments criticize higher ed for emphasizing credentials, curves, and high‑stakes grading, making AI a rational way to “game” a zero‑sum system.
• Others stress personal integrity and long‑term self‑harm from cheating, while noting broader cultural distrust of institutions and role models who succeed via dishonesty.

Future of essays and assignments

• Some argue if AI can do an assignment well, the assignment design is obsolete; call to move away from formulaic essays toward presentations, more authentic tasks, or different communication forms.
• Others defend essays as a core way to develop thinking and writing, noting essay‑like writing is common outside academia (editorials, blogs, long posts).

Overall Reception

• Many commenters find the visualization “phenomenal,” “artful,” and surprisingly usable and fast, even on mobile.
• The playful country names (e.g., “Lispaña,” “Sussex,” “Homelabia,” “Quitlessia,” “The GitHub Archipelago”) are widely enjoyed and become a running joke.
• Some treat it as a game: trying to locate specific projects without search or “sailing” from one project to another via paths.

Data Source, Similarity, and Layout

• Repos are positioned based on overlapping stargazers. Dots are close if they share many stargazers.
• Edges between repos are derived from a similarity metric, primarily Jaccard similarity over star sets, with a threshold to decide which edges exist (exact threshold not specified).
• Lines only appear when zoomed into a region.
• Popular “celebrity” projects tend to cluster together due to generic popularity rather than semantic similarity; commenters note this as a known limitation.
• Suggestions include using TF–IDF over the user–star matrix to downweight “overstarring” users, or code embeddings, though resource costs are questioned.
• The author experimented with multiple similarity metrics and chose Jaccard subjectively as “best” for this use.
• Clustering uses community-detection–style algorithms (Louvain/Leiden plus custom methods). Hierarchical clustering ideas (e.g., HDBSCAN) ran into memory issues at this scale.

Interpretation Quirks and Ecosystem Insights

• Several projects appear in “unexpected” lands (e.g., Linux near frontend/awesome lists, HTMX in Djangonia, Django in Pythonia, MicroPython/CircuitPython placement, Magisk forks in different regions).
• Explanations offered:
  • Users star surrounding ecosystem projects more than core ones (e.g., Linux kernel, Django).
  • “Aspirational” star patterns (e.g., people star Julia alongside Python ML/AI projects without fully moving ecosystems).
  • Overlap of interest communities (e.g., crypto with AI).
• Some observe smaller-than-expected regions for Rust, Node, or Azure, and very large ones for JavaScript, YAML/DevOps, Python/AI, Vim/Emacs.
• One hypothesis: ecosystems with lower friction to publishing packages (e.g., JavaScript) yield larger “islands.”
• PHP’s prominent “kingdom” is noted as evidence it remains widely used and actively developed.

Critiques of the Map Metaphor and Stars

• Some question the country/map metaphor and fuzzy region names; they propose hierarchical cluster diagrams with clearer labels.
• Others appreciate that it is “just a view, not a thesis,” and like the personality over stricter analytical clarity.
• Skeptics note that stars can be noisy or gamed (bots, vanity projects), so importance and quality are not faithfully represented.

Cyberpunk Aesthetics and Cultural Influence

• Many commenters connect Kowloon Walled City (KWC) to cyberpunk and Blade Runner–style visuals.
• Some argue cyberpunk aesthetics were heavily inspired by KWC, not vice versa.
• Rock music, comics, films, and recent Hong Kong cinema are cited as drawing on KWC’s imagery.
• Several people describe the visual fascination as more “morbid curiosity” than admiration.

Software Architecture Metaphor

• KWC is likened to large SaaS codebases: layers of ad‑hoc additions, hard to navigate, understood only by insiders.
• Discussion branches into code reviews, coding standards, and mechanical enforcement.
• Some argue “building codes” for software (regulation, audits) could reduce chaos; others say this would stifle innovation or is ineffective, citing regulated domains (medical, automotive, aviation) that still suffer complexity.
• There is tension between business speed and clean architecture; some note that tech debt can sink companies.

Living Conditions, Romanticization, and Ethics

• Strong disagreement over whether KWC is being romanticized.
  • One side criticizes outsiders who view it as a cool dystopia or “human zoo,” stressing squalor and danger.
  • Others stress resident attachment, low cost of living, and autonomy; some residents reportedly miss it, and some refused to leave.
• Immigration/legal status and lack of other options are mentioned as reasons people lived there.
• Some argue that before eliminating “awful” places, society should address the conditions that make them necessary.

Comparisons and Related Places

• KWC contrasted with U.S. public housing projects; one view calls KWC anarchic and self-assembled, unlike state-planned estates.
• Chungking Mansions and Mirador Mansion are discussed as present-day, somewhat similar dense, chaotic environments; multiple first-hand accounts describe tiny rooms, noise, elevator queues, touts, and occasional violence, but not always extreme filth.

Resources, Media, and Documentation

• Multiple links shared: photo books, architectural cross-sections, documentaries (including German ones), novels, history books, and an airport recreation exhibit.
• Some lament limited first-person accounts and that KWC vanished before the era of ubiquitous online video.
• One commenter wishes KWC had been preserved as an open-air museum, given its cultural impact.