Hacker News, Distilled

AI powered summaries for selected HN discussions.

Page 532 of 547

<dialog>: The Dialog Element

Overall view of <dialog> and web standards

  • Many see <dialog> as a net win: a standard, built‑in way to do modals without “flavor‑of‑the‑month” JS frameworks, especially for internal tools.
  • Others describe the API as “messy” and only mediocre, emblematic of how web standards are valuable mainly because they are ubiquitous, not because they’re well‑designed.

API design, standards process, and history

  • Some criticize that <dialog> was pushed into all browsers despite long‑standing accessibility/security concerns and only fixed later.
  • Others counter that those issues were eventually resolved via spec updates and implementations.
  • There’s frustration about the “living standard” process and perception that legacy APIs like alert/confirm/prompt are being nudged out without equally simple replacements.

Styling, UX, and native look

  • A major disappointment: <dialog> is almost unstyled by default. Some had hoped for OS‑native looking, movable dialogs; instead it feels like a “glorified div.”
  • Several argue this blank‑slate behavior is correct: most sites have custom design systems and need full control; heavy UA styling is hard to undo.
  • Disagreement on whether native‑looking controls are desirable vs. brand consistency. Many note a broader pattern: native widgets (date pickers, media controls) look different across browsers and are often avoided.

Modals, accessibility, and top layer behavior

  • <dialog>’s modal behavior (focus trapping, top layer) is generally praised for accessibility, but there are complaints about edge cases: scroll events bubbling, inability to adjust z‑index, and clashes with AdSense interstitials.
  • Debate over modals themselves: some say they’re overused and user‑hostile; others argue they’re essential for multi‑step workflows and simpler state management.
  • Concerns about dark patterns and user‑locking dialogs are raised, with pushback that any element can be abused.

JS reliance, forms, and alternatives

  • Some dislike that opening/closing dialogs generally requires JS; desire CSS/HTML‑only control is mentioned, with “invokers” and popover attributes cited as partial answers.
  • Reported quirks include form submission unexpectedly closing dialogs and limited event hooks to intercept closing.
  • Several people experiment with async/await‑style wrappers around dialogs as non‑blocking alert/confirm/prompt replacements, often built on showModal() or popover.

Every V4 UUID

Overall reaction & concept

  • Many commenters love the project as funny, artistic, and surprisingly polished, likening it to a “Library of Babel” for UUIDs.
  • Others initially misunderstand it as a database of existing UUIDs or UUID-shaped domains before realizing it’s a deterministic generator over the full v4 space.

Implementation & technical details

  • The site enumerates all possible UUIDv4s by mapping each integer index in [0, 2^122) bijectively to a valid UUIDv4 using a Feistel-like cipher, not random generation.
  • This preserves uniqueness: each index yields exactly one UUID, and no UUID appears twice.
  • Only 122 bits are free; version and variant bits are fixed per the v4 format.

Search behavior

  • The “search” is effectively a custom full-text finder that uses the known mapping to generate UUIDs matching a substring rather than scanning stored data.
  • It does not strictly enumerate matches in order; “next/prev” can revisit different UUIDs, and mobile browser find-in-page doesn’t integrate.
  • Commenters propose more rigorous schemes (linear algebra over GF(2), T-functions, format-preserving encryption, SMT solvers) to get ordered results while retaining a random-looking sequence.

UUID format and scale

  • Several comments explain that v4 UUIDs are 128-bit values with 6 fixed bits, leaving 2^122 possibilities.
  • There is discussion of valid hex digits, version nibble 4, and allowed variant bits (8–b), and of why naïve strings like deadbeef-f00d-f00d-deadbeef are invalid.
  • People compare the keyspace size to card-shuffle factorials and cosmic-scale analogies.

Performance, UI, and browser quirks

  • Users praise how smooth and responsive the “infinite” scrolling feels compared to typical web apps.
  • Implementation uses a virtualized table and custom scroll handling because browsers cap scrollable height well below “trillion-pixel” ranges.
  • Some report edge-case bugs (e.g., scrolling past the bottom throwing errors, trackpad vs. wheel differences, mobile scroll/search limitations).

Security, privacy, and “data leaks” jokes

  • Running joke: “all UUIDs have been leaked,” paralleling lists of all ATM PINs or SSNs; people mock-check “their” UUIDs, passwords, and keys.
  • One commenter briefly worries this could be a useful rainbow table but others clarify that UUIDs are generated on the fly and cover the entire space, not a curated subset.

Ideas, feature requests, and variants

  • Requests include: bookmarking via deep links, an API, smooth/autoscroll, draggable scrollbars on mobile, Excel export, and “I’m Feeling Lucky” / scrubbing controls.
  • Many enjoy hunting for vanity/hexspeak UUIDs (e.g., deadbeef, b00b, 69420, pi) and joke about “claiming” or minting them as NFTs.
  • Some imagine similar projects for every SSN, every password, or “every UTF-8 string,” extending the Library-of-Babel theme.

The largest open-source dataset of car designs, including their aerodynamics

Open-source aerodynamics tools and methods

  • Multiple commenters recommend open-source tools for aircraft/RC/flying-wing design:
    • CFD: OpenFOAM (powerful but often overkill for hobby use).
    • 2D airfoils: XFOIL.
    • 3D / vortex lattice / panel methods: AVL, VSP Aero, XFLR5, FreeWake, Datcom.
    • Higher-level toolkit: AeroSandbox (GitHub).
  • Consensus: for “normal-ish” designs, panel / potential-flow models are much easier and faster than full CFD, and good enough for performance and stability estimates.
  • Emphasis that some aeronautics background is needed to interpret results and understand limitations.

Dataset scope, content, and access

  • Data is hosted on Harvard Dataverse and referenced GitHub; also mirrored at caemldatasets.org without access restrictions.
  • Dataset size is reported as “a few hundred gigabytes.”
  • Clarification that the dataset consists of parametric, randomized car-like shapes derived from a template, not CAD models of real production cars.
  • One linked paper describes it as a large multimodal car dataset with CFD simulations and deep learning benchmarks; practical downstream uses are not deeply discussed in the thread.

Licensing and “open source” controversy

  • Dataset is licensed under Creative Commons Attribution–NonCommercial (CC BY‑NC 4.0).
  • Several commenters argue that:
    • Non-commercial licenses are not “open source” under established definitions.
    • Calling it “open source” is misleading and waters down important legal concepts.
  • Others note:
    • CC BY‑NC still allows broad access, but restricts commercialization of the dataset.
    • There is ambiguity about whether using the data inside a commercial workflow (e.g., training models, designing a car) would violate “NC”; interpretations differ and remain unclear.

Car design, modularity, and aesthetics

  • Some lament that aerodynamics + regulation push all cars toward similar “blobs.”
  • Others welcome standardization and shared parts for cost and repair benefits, but note manufacturers have incentives to avoid interchangeable components to protect margins.
  • There is a tension between:
    • Desire for cheap, robust, standardized vehicles.
    • Desire for emotionally appealing, varied designs; several commenters feel current design trends are in a “dark age.”

EV size, weight, and efficiency debates

  • Extensive side discussion on why many modern EVs are heavy crossovers/SUVs:
    • Large, heavy battery packs to meet customer range expectations.
    • Consumer preference and profit margins for SUVs and crossovers.
    • Safety, crash standards, and “arms race” dynamics with larger vehicles.
  • Energy-density arguments:
    • One side cites ≈100× higher gravimetric energy density of gasoline vs batteries.
    • Another points out EVs’ higher drivetrain efficiency and regenerative braking, reducing the effective gap to around 5× in practice for usable energy.
    • Disagreement on whether that numerical refinement is “pedantic” or materially important.
  • Some argue ICE vehicles remain more mature and cost-effective; others claim certain EVs (e.g., mid-market crossovers) can already be more cost-effective than comparable ICE models.
  • Electric aircraft are mentioned as an example where battery weight and inability to “burn off” mass severely limit viability; landing-weight constraints exacerbate this.

Future EV architectures and packaging

  • Several comments note that many current EVs are adapted from ICE platforms, limiting efficiency and packaging gains.
  • Others highlight a shift toward EV-native platforms:
    • Examples cited (Tesla, Hyundai, etc.) and quotes from an automaker CEO promising “super-efficient platforms” with small exterior size but larger interior volume, and sub‑$40k or even sub‑$30k targets.
    • Suggestion that truly compact, efficient, family-friendly EVs may emerge within a few years.

Questions about aerodynamic extremes

  • A commenter asks how many of the ~8,000 shapes achieve very low drag coefficients (Cd < 0.20), citing a historical EV with Cd 0.19.
  • The thread does not provide an answer; distribution of Cd values in the dataset remains unclear.

Tokyo is set to introduce a four-day workweek for government employees

Scope and Policy Details

  • Applies only to Tokyo metropolitan government workers, not national or ward employees; likely mainly office roles.
  • Some see it as “too little, too late” and only modestly relevant to fertility; others emphasize “start somewhere” and incremental change.

Four-Day Week Structures and Tradeoffs

  • Many commenters stress the crucial question: 32 hours vs. compressed 40.
  • Some strongly prefer 4×10 over 5×8 for the extra full day off; others found 10‑hour days exhausting, unproductive, and incompatible with commuting and childcare.
  • Experiences with 9/80 schedules, half‑day Fridays, and 80–90% contracts are mixed: transformative for some, torture for others.
  • Several argue that true social progress is 4 days with no pay cut or workload increase; otherwise it can become “same work, less pay.”

Japanese Work Culture and Feasibility

  • Multiple comments doubt young staff will feel free to actually take the time off, citing norms of unpaid overtime, presenteeism, and deference to seniors.
  • Others say the culture is changing: younger workers are increasingly rejecting extreme corporate expectations and seeking flexibility or “less prestigious” but freer jobs.

Family Life, Childcare, and Mental Health

  • Many parents describe reduced schedules (80–90%, extra weekday off) as life‑changing: more time for kids, chores, bureaucracy, and personal well‑being.
  • Others note that if schools/childcare stay on 5‑day schedules, parents may just buy extra care for the 5th day; caring for small children is not “free time.”
  • Mental health strains, especially in Eastern Europe and Japan, are repeatedly linked to overwork, instability, and weak support for therapy.

Fertility, Demographics, and Intergenerational Duty

  • Thread repeatedly connects the policy to Japan’s low birthrate and aging population, but many argue work hours are only one factor.
  • There’s deep debate over obligations between generations: some see current systems as transgenerational exploitation of the young; others view supporting elders as a core social contract.
  • Popular view: modern low fertility largely reflects choice, education, and opportunity costs, not just policy; generous benefits in Europe haven’t fully reversed declines.

Economic and Social Effects

  • Some argue shorter weeks can raise productivity and job satisfaction, referencing prior company experiments and historical 35‑hour weeks.
  • Others see potential for higher labor costs with no extra output, or simply redistributing existing work across more people.
  • Concerns raised about reduced access to government services and perception that government workers already underperform.

Ask HN: What are the best programmable holiday lights?

WLED and DIY Addressable Systems

  • WLED + addressable LEDs (WS2811/WS2812B and compatibles) are the dominant recommendation.
  • Features highlighted: many built‑in effects, time-based scheduling, web UI, mobile apps, Home Assistant and DMX (sACN/Art‑Net) integration, HTTP API, and multi-controller sync.
  • Installation is considered unusually easy via the browser-based firmware flasher.
  • Works very well for 1D strips; experiences with 2D/irregular layouts are mixed: some report big improvements with the newer 2D wizard, others still find mapping non-rectangular shapes frustrating and “bolted on.”

Controllers & Hardware Options

  • ESP32 boards are preferred; ESP8266 is now seen as underpowered for complex setups, and ESP32‑C6 is warned against due to firmware incompatibility.
  • Pre-flashed or plug‑and‑play WLED controllers (athom, QuinLED, Pimoroni Plasma, various AliExpress/Amazon boards) reduce wiring/soldering.
  • 5V strips allow per‑LED control; 12V nodes/strips reduce voltage drop but some types group LEDs in threes. Bullet‑style 12V nodes are popular outdoors.
  • BTF-Lighting is frequently cited for quality strips/strings.

Prebuilt Consumer Ecosystems (Govee, Twinkly, others)

  • Govee: praised for easy setup, rich effects, LAN API, and “scene” features to coordinate multiple products; good for permanent house outlines.
  • Twinkly: repeatedly praised for camera-based 3D mapping of bulbs and attractive patterns; used on trees and walls, can cluster multiple strings; some complaints about buggy or awkward apps.
  • Other suggestions: Eufy outdoor strips, Shelly RGBW for whole-strip color, “dumb” lights on smart plugs (often Tasmota).

Power, Safety, and Insurance Concerns

  • Strong advice to use reputable, UL-listed power supplies, especially for hardwired or outdoor installs.
  • Debate over whether non‑listed supplies or unpermitted DIY work voids insurance; consensus: insurance probably still covers plug‑in mistakes, but code and inspections require listed gear for hardwiring.
  • General distrust of random no‑name Amazon power supplies; brand-backed, tested units are preferred.

Scaling Up to Full Shows

  • For large musical shows: 12V WS2811 pixel nodes, standardized connectors, and dedicated controllers (Falcon, AlphaPix) with xLights/Falcon Player are common.
  • Coroplast props and 3D‑printed elements are used to create standout displays; hobby is described as fun but time- and money-intensive.

Alternative Controllers & Mapping

  • Pixelblaze is strongly recommended by some over WLED for complex or organic patterns, arbitrary 2D/3D mapping, live browser-based coding, and multi-controller sync; proprietary firmware is the main downside.

Other Topics

  • Projection mapping (e.g., Luxedo) is attractive but expensive; open-source mappers on Raspberry Pi plus a bright, weather-sheltered projector are suggested.
  • “Astro” timer switches and standalone calendar-based timers are proposed for sunset/sunrise control without a full smart‑home stack.
  • Aesthetic debate: some prefer warm white or even incandescent‑like looks; others like bright, cool white, often season- or time‑of‑day dependent.

Mistakes as a new manager

Performance, posture, and “carrot vs. stick”

  • Several comments argue new managers are too lenient, especially early on, and should be more willing to fire for persistent underperformance and missed standards.
  • Others see this as a symptom of dysfunctional cultures, warning that aggressive hire/fire cycles and strong “stick” usage can be toxic and demoralizing.
  • Two rough styles are described: “restless” (hire/fire fast, strict rules) vs “patient” (train, tolerate more slack), with trade‑offs in fairness, morale, and speed.

Delegation, IC habits, and staying off the critical path

  • Delegation is widely cited as a top struggle: managers take work themselves to “save time,” then become bottlenecks and neglect management duties.
  • Strong consensus: managers should avoid owning critical‑path tasks, and if coding, focus on low‑risk refactors, docs, and tech debt.
  • Some feel “working managers” can be effective on very small teams; others say this fails once meeting and coordination load grows.

Feedback, conflict, and psychological safety

  • Many highlight “avoiding hard conversations” as the biggest new‑manager mistake, especially when managing former peers.
  • Debate centers on how to give feedback: behavior/outcomes vs. character, specificity vs. vague “quality issues,” individual blame vs. systemic problems.
  • Some warn that scripted, indirect phrases can feel passive‑aggressive; others say candid, behavior‑focused feedback, in a blameless culture, is essential.
  • There’s tension between “ruinous empathy” (never confronting) and overly adversarial approaches.

Technical depth and manager scope

  • Some insist line managers must be deeply technical and able to understand systems, ask hard questions, and detect BS; a few go so far as to say they should be able to step into a report’s work.
  • Others push back: that’s closer to a tech lead’s role; managers should understand “why” and trade‑offs, not do every “how.”
  • Over‑probing by technically curious managers can waste IC time if not managed carefully.

Dopamine shift and redefining success

  • Multiple commenters resonate with losing the immediate gratification of shipping code.
  • Some never adapt and return to IC work; others report longer‑cycle but more durable satisfaction from developing people, getting promotions for reports, or removing blockers and politics.

Do managers add value?

  • One view calls management “fluff” and largely unnecessary.
  • A counterexample from a flat org describes how lack of oversight led to entrenched underperformance, resentment, and eventually a heavy-handed management reset—argued as evidence that good middle management prevents worse outcomes.

Llama-3.3-70B-Instruct

Performance and Benchmarks

  • Multiple commenters say Llama‑3.3‑70B‑Instruct performs on par with, or slightly better than, Llama‑3.1‑405B and close to GPT‑4o on several shared benchmarks.
  • Some note it does unexpectedly well on independent evals (e.g., Kagi).
  • Others give concrete counterexamples (e.g., D&D 5e rules) where it hallucinates; another model (Claude) did better there.
  • Overall sentiment: very strong free / “open weight” model, but not universally superior across tasks.

Quantization, Local Use, and Tooling

  • Users run 70B locally via Q3–Q5 quantization on consumer GPUs and CPUs, reporting ~2–16 tokens/s depending on hardware (4090, 3090s, M‑series Macs, older GPUs).
  • Q4 is widely seen as the practical sweet spot; heavier quantization degrades coherence, prompt adherence, and precision, especially for complex conditionals and chain-of-thought.
  • Discussion of model size vs VRAM: rough rule is parameter count ≈ GB at 8‑bit; halve for 4‑bit plus overhead for context and OS.
  • Many recommend smaller models (8–20B, ~32B) as “sweet spots” for 12–24GB cards.
  • Tools mentioned: Ollama, LM Studio, llama.cpp, Open WebUI, plus Unsloth for more efficient fine‑tuning.

Base Model and “Openness”

  • Some are disappointed there’s no separately released base model; others say the base is effectively the earlier 3.1‑70B.
  • Strong debate over terminology: several insist this is not “open source” but “open weight” freeware due to license restrictions and lack of full reproducible training pipeline/datasets.
  • Others argue practical rebuildability is moot at current training costs, but critics point to the importance of true open source definitions and training‑data legality.

Safety, Censorship, and Uncensoring

  • Interest in uncensored/unaligned variants; reports that many “decensored” models feel noticeably dumber or still refuse content.
  • One line of work (abliteration) is criticized as often “lobotomizing” models; straightforward fine‑tuning on uncensored data is reported to preserve quality better.
  • Some describe manual tricks (editing refusals mid‑response) as local workarounds.

Meta’s Strategy and Ecosystem Impact

  • Broad agreement that releasing strong free models pressures proprietary providers (OpenAI/Anthropic), drives prices down, and benefits developers.
  • Several frame this as classic “commoditize your complement”: Meta strengthens its social/ads core business while commoditizing general‑purpose AI.
  • Views on Meta’s motives and ethics are mixed: some see a “redemption arc” and founder‑driven ambition; others stress past privacy/ads scandals and warn about more powerful ad‑targeting and AI “slop” in feeds.

Oldest known wild bird lays egg at 74

Extreme longevity and generations

  • Commenters note that a 74-year-old albatross that starts breeding at ~5 could “overlap” with many descendant generations, prompting playful notation debates ((great-)^13 grandchild, etc.).
  • Other long-lived animals are mentioned (turtles, whales, koi, elephants), plus trees, fungi, and bacteria that experience huge numbers of generations around them.
  • A side thread asks what it means to “witness” generations, with some joking about language and literature.

Albatross biology, mortality, and mating

  • Albatrosses are praised as beautiful and often described as “mate for life,” but others link sources showing notable rates of “divorce” and partner switching, especially after failed breeding or mate death.
  • Long-line fishing is highlighted as killing tens of thousands of albatrosses annually; this is framed as emblematic of humans destroying beauty and pushing many species toward threatened/endangered status.

Fishing, seafood, and food ethics

  • Several commenters say they have reduced or stopped eating fish due to overfishing, bycatch, disease issues in aquaculture, environmental damage, and even slave labor in parts of the supply chain.
  • Some suggest land-based recirculating aquaculture as a possible (but expensive, fragile, low-volume) solution.
  • Others argue industrial-scale wild harvest for billions of people is inherently unsustainable and morally troubling.

Meat reduction, vegetarianism, and veganism

  • Multiple people describe cutting meat to a few meals per week, or eliminating factory-farmed meat and most restaurant meat.
  • There is discussion of gradual reduction (“one less meat meal a week”) versus all-or-nothing veganism, with the idea that many people halving intake could have large collective impact.
  • Protein concerns are discussed: some use whey, Greek yogurt, or beans; others say the feeling of “needing more protein” is subjective and unclear.

Cultural and culinary threads

  • Commenters compare past norms where meat was eaten only a few times a week to current expectations of meat at every meal.
  • Polish vegetarian/vegan-friendly dishes are listed (e.g., borscht variants, mushroom pierogi, sauerkraut-based soups, potato pancakes), often requiring only minor substitutions.
  • There is a side debate on whether vegans can eat bread (yes, since yeast is a fungus) and on how religious dietary rules handle things like alcohol in bread or microscopic organisms in water.

Moral frameworks and animal suffering

  • One view ranks animal moral status by intelligence/capacity to suffer (monkeys > cows > fish/chickens), suggesting shifting from large mammals to smaller animals and better welfare (e.g., “better” eggs) as pragmatic harm reduction.
  • Others reject this as arbitrary, arguing industrial farming is fundamentally inhumane (e.g., cramped cages, beak trimming, male chick culling, engineered fast growth in chickens).
  • There is debate over whether grass-fed cattle on “undeveloped wilderness” are environmentally beneficial or instead a driver of habitat loss and methane emissions.
  • A counterpoint claims vegetable production also kills many small animals and that, per calorie, grazing cows might kill fewer animals than some crops; others strongly dispute this, calling the comparison delusional.

Human health and dietary extremes

  • Some report serious health issues on long-term vegan diets (brain fog, cold sensitivity, heart palpitations) and say switching to meat-heavy or beef-only “carnivore” diets dramatically improved autoimmune or other conditions.
  • Others insist most vegans do well when properly balanced and cite plant-based athletes, suggesting tools like cast-iron cooking or “lucky iron fish” to address iron deficiency.
  • The prevalence of vegan health problems is contested: some say it’s “extremely rare,” others say they’ve seen it fairly often in committed vegan circles.

Humans, population, and planetary impact

  • Several comments link collateral ecological damage (extinctions, habitat loss, industrial pollution) to broader human behavior, characterizing our species as abusive and cruel to the biosphere.
  • One person speculates that declining human birth rates might eventually give nature a chance to recover, though this isn’t explored deeply.

Birds, dinosaurs, and lifespan implications

  • An old albatross leads to questions about dinosaur lifespans. Commenters emphasize that birds are dinosaurs (avian theropods); all living dinosaurs are birds, but not all ancient dinosaurs were birds.
  • Crocodiles are discussed as close relatives but not dinosaurs; links to phylogenetic visualizations are mentioned.
  • One argument: if giant non-avian dinosaurs had grown like lizards, they’d have needed centuries to reach size, so their growth patterns likely resembled birds’ rapid juvenile growth instead.

Age verification and tag-swapping skepticism

  • Some wonder if band/tag swapping could have faked the 74-year age.
  • Others argue it’s unlikely: modern photography, consistent nest location and partner behavior, and the difficulty of secretly re-tagging a bird in a remote colony make fraud improbable, though not logically impossible.
  • Potential biological checks (scars, patterns, future bone or DNA analysis) are suggested but not confirmed in the thread.

Bird aging and late-life reproduction

  • A question arises: do birds, like humans, have higher risks or abnormalities when reproducing at advanced age?
  • A cited literature review suggests some seabirds show minimal age-related decline in survival or reproduction; some even improve reproductive success with age.
  • Long-lived seabirds (terns, gulls, albatrosses) may show weak or no decline in reproductive output despite rising mortality, possibly linked to evolutionary traits like delayed maturity and low annual fecundity.

Captive bird lifespans and “legacy pets”

  • Several comments note that many parrots and other birds in captivity can live for many decades, often outliving multiple owners and requiring “legacy plans.”
  • Examples include cockatoos reaching or surpassing 100 years and a ~45-year-old pet cockatoo that enjoys dancing to music.

TikTok divestment law upheld by federal appeals court

Legal reasoning and constitutional scrutiny

  • Appeals court upheld the divest-or-ban law, saying it would survive even under strict scrutiny, so it didn’t need to decide between strict vs. intermediate scrutiny.
  • Strict scrutiny framing: compelling interest = national security; “narrow tailoring” satisfied because Congress tried a less-intrusive mitigation plan (Oracle / data localization) first and rejected it as insufficient.
  • Some commenters argue this sidesteps the key First Amendment question and insulates the ruling from Supreme Court review; others think SCOTUS will still take the case because it’s a novel, high‑profile free‑speech issue.
  • Debate over whether the law is an unconstitutional bill of attainder targeting a single company; the court said the remedy isn’t “punishment,” critics disagree.
  • Concern that “national security” is being used as a low‑evidence trump card, with critical evidence presented under seal and not to the public.

National security vs. free speech

  • Security argument: TikTok’s Chinese parent is structurally tied to the CCP; that allows:
    • Data access useful for espionage or targeting.
    • Invisible algorithmic boosting/suppression to shape US and allied opinion, especially in crises (e.g., Taiwan).
  • Supporters say you shouldn’t “wait for a smoking gun”; adversarial control of such a large platform is itself an unacceptable risk.
  • Opponents emphasize lack of concrete proof TikTok has been used this way, calling the threat hypothetical and the remedy broad censorship of millions of Americans.
  • Strong First Amendment camp: government should counter propaganda with more speech, not bans; letting the state decide which platforms are “too dangerous” is seen as authoritarian creep.

Platform parity and selective targeting

  • Many note identical risks (data harvesting, disinformation, addictive algorithms) exist on US‑owned platforms (Meta, X, YouTube), which helped facilitate past election interference and genocidal incitement abroad.
  • One view: foreign adversary ownership is the key difference; it’s legitimate to treat TikTok differently from domestic platforms.
  • Another: this is protectionism (especially for Meta) and/or backlash against TikTok hosting pro‑Palestinian and anti‑establishment content.

Enforcement and likely impact

  • Law’s timeline: ban effective Jan 19, 2025, 270 days after signing, with a single possible 90‑day presidential extension.
  • Enforcement levers mentioned: app stores, hosting, payments, and potentially ISPs.
  • Some expect users to move to VPNs and web apps, citing China/Russia/Brazil experience; others think friction plus network effects will kill most US usage.
  • Creators and some users see TikTok as uniquely valuable for surfacing marginalized voices and non‑mainstream political perspectives, and frame the ban as part of a longer US pattern of suppressing dissenting narratives.

Install postmarketOS on Android phone and use Docker as a home server

Scope of the Article / Title Confusion

  • Many note the article is really about flashing postmarketOS (Alpine/musl) and then installing Docker, not “Docker on Android.”
  • Some find that less exciting (“just Linux on a small computer”), others like it as a way to reuse old phones.

Android vs. Linux for Phone-as-Server

  • Android is seen as problematic for servers due to:
    • Aggressive background OOM killing that can terminate services like sshd or containers.
    • Lack of swap and difficulty marking critical services as non-killable.
  • Several argue you can “play by Android rules” (foreground services, root workarounds, system flags) or use Termux to run long-lived services, including Docker.
  • Others counter that a proper Linux distro (postmarketOS, Mobian, etc.) gives more predictable server behavior and mainline kernels.

Battery Life, Degradation, and Safety

  • Strong concern about leaving phone batteries on charge 24/7:
    • Repeated anecdotes of swollen batteries over years of continuous power.
    • Comparison to UPS batteries: lead-acid tolerates float charge; phone Li-ion does not.
  • Suggestions: remove battery entirely, fake the battery electrically, or use phones with configurable charge limits (e.g., 60–80%).
  • Coulomb counting and BMS behavior are discussed; partial charge + occasional full cycles may help, but long-term accuracy is tricky.
  • Some describe hardware “chargers/limiters” and timers; others call crude timer-based cycling unsafe and destructive.

Security and Firmware Concerns

  • Avoiding Android is also framed as a kernel-security and firmware issue:
    • Old Android devices often have outdated kernels.
    • Many proprietary firmware blobs (baseband, Wi-Fi, BT, etc.) stop receiving updates; this is seen as a risk if exposed to the internet.
  • Using mainline Linux (postmarketOS, Mobian) can improve kernel support, but firmware blobs largely remain closed and unmaintained.

Linux Phone OSes and Practicality

  • Status of Linux phones (PinePhone, Librem 5, SailfishOS) is mixed:
    • They can work as daily drivers for some, but hardware (battery life, modem reliability, performance) is often the bottleneck.
    • Android remains far more power-efficient and has better app availability.
  • Many conclude phone-as-server is appealing mainly for hardware reuse and ultra-low power, not as a general replacement for SBCs or mini PCs.

Rivian is opening its charging network to other EVs

Rivian’s Network and This Change

  • Many were surprised Rivian even has its own fast‑charging network (~90–92 locations now, 3,500 planned).
  • Strategy so far: place DC fast chargers in remote, outdoorsy areas and national parks, complementing (not duplicating) urban chargers and Tesla Superchargers.
  • Opening the network is welcomed, especially by non‑Tesla drivers who want better access to “adventure” destinations.
  • Rollout to other EVs is phased; some are disappointed it isn’t “just a software update” due to hardware, voltage‑range, and payment-interface constraints.

Connector Standards and Compatibility

  • Strong pushback on the idea of “seven” meaningful plugs in North America; in practice the thread converges on:
    • DC: CCS1 and Tesla’s NACS/J3400 (with CHAdeMO described as effectively dead).
    • AC: J1772 (often integrated with CCS1).
  • Industry trend: migration to NACS/J3400; US has designated it the federal standard.
  • Adapters between CCS1 and NACS are widely available and relatively cheap; protocol-level compatibility helps.

Superchargers, Port Placement, and Cable Length

  • Rivians at Tesla Superchargers often occupy two stalls because Rivian’s port is front‑left vs Tesla’s rear‑left and cables are short.
  • Some blame Rivian design, others Tesla’s short-cable, Tesla‑only layout.
  • Newer V4 Superchargers and some other networks add longer, often liquid‑cooled cables and trailer‑friendly stalls, but longer cables have cost, efficiency, and theft downsides.

Economics and Reliability of Charging Networks

  • DC fast chargers are reported as expensive (tens to hundreds of thousands of dollars per plug with infrastructure), with additional ongoing grid “demand charges.”
  • Compared with gas stations, utilization is lower (many EVs charge at home), making standalone charging a tough business; subsidies (e.g., Dieselgate/EA, state and federal grants) are seen as key.
  • Tesla is portrayed as unusually cost‑efficient and possibly profitable; other networks are described as subsidy‑dependent.
  • Tesla and Rivian-branded networks are praised for uptime and rapid repairs; third‑party networks, especially Electrify America historically, are criticized for frequent outages and slow fixes, though some claim EA has improved markedly with newer hardware.
  • US subsidies now require high uptime (97%), which may push better maintenance.

User Experience and Payments

  • Many complain about fragmented apps, QR codes, and account setups; strong preference for “plug in and tap card/phone” or true plug‑and‑charge.
  • Some networks (ChargePoint, EVgo, 7‑Eleven, Tesla V4 in Europe) already offer contactless card/tap.
  • ISO 15118 “plug and charge” exists, and Tesla plus most automakers implement or plan to, but certificate management and roaming are still unsettled.
  • Europe is cited (by commenters) as ahead on standardizing contactless payment; US efforts via SAE and federal rules are emerging.

Standardization and Policy

  • Several argue lack of early North American standardization (vs. Europe/China) slowed private investment and created today’s connector and app chaos.
  • Others note that in practice, modern EV charging is already “two systems plus adapters,” and in-car navigation typically hides incompatible stations.

EV Adoption, Depreciation, and Used Market

  • Some see opening more networks (Tesla, Rivian) as crucial to easing range anxiety and mainstream adoption.
  • Noted that many buyers don’t fully understand charger compatibility and may wrongly assume any visible charger will work.
  • Depreciation of some EVs, especially early or high‑MSRP models, is called “crazy,” but others highlight that this makes used EVs and leases very attractive.
  • Commenters claim long battery life (often >80% capacity at 10 years/200k miles) and predict sharply lower pack replacement costs in coming years, though figures are speculative within the thread.

Ethical and Environmental Debates

  • One thread criticizes EVs for reliance on cobalt linked to child/slave labor in the DRC; another counters with the climate and health harms of continued fossil‑fuel use.
  • Acknowledgement that some chemistries are cobalt‑free, but the supply chain issues for cobalt remain a concern for some.

Miscellaneous Ideas and Side Topics

  • Suggestions: gas stations and restaurants as natural DC fast‑charge hubs; co‑locating chargers with retail/food to monetize the “captive audience.”
  • Discussion of land/real‑estate plays around stations vs. uncertainty about future much‑faster charging (sub‑10 or even sub‑20 minutes).
  • Peer‑to‑peer “emergency” charging at homes already exists via platforms like PlugShare.
  • Some argue third‑party chargers lack strong incentives for reliability, akin to low‑quality ATMs, while OEM‑linked networks have direct brand and sales exposure.

Romanian court annuls result of presidential election first round

Alleged interference and TikTok campaign

  • A previously little‑known presidential candidate surged from low single‑digits in polls to win the first round.
  • Many commenters link this to a massive TikTok campaign:
    • Thousands of dormant accounts allegedly reactivated in a coordinated way.
    • Influencers reportedly paid through intermediaries; many clips not labeled as electoral ads despite Romanian law.
    • Intelligence reports (recently declassified) describe organized online activity resembling earlier Russian campaigns in Ukraine and Moldova, though the exact proof and attribution to a “state actor” are contested in the thread.
  • Others point to leaked chats showing local volunteers organizing and self‑funding print materials and online promotion, arguing this could explain some of the surge without foreign control.

Campaign finance violations

  • The candidate officially declared “zero” campaign spending despite visible nationwide promotion.
  • Romanian law requires:
    • All campaign contributions and expenditures to flow through registered accounts.
    • Clear labeling and traceability of electoral ads.
    • No foreign financing.
  • Some see this as clear fraud that by itself invalidates the process; others argue such violations should lead to prosecutions and fines, not annulling millions of votes after they’re cast.

Role and powers of the Constitutional Court

  • The Court annulled the entire electoral process and ordered a full restart.
  • Supporters say:
    • The constitution tasks the Court with guaranteeing proper procedures.
    • Law allows annulment when fraud distorts results; combined TikTok interference and undeclared spending meet that bar.
  • Critics argue:
    • Law only clearly allows annulling a specific election day for ballot fraud, not wiping the whole process after one round was already validated.
    • The Court acted on intelligence “hearsay” without due process, effectively inventing a new power and setting a dangerous precedent.

Democracy vs. national security

  • One camp: allowing a president effectively installed via Russian/Chinese influence and illegal financing would be worse for democracy than re‑running the election.
  • Other camp: once votes are cast and fairly counted, overturning results because people “voted wrong” or were “misinformed” is more dangerous; it legitimizes do‑overs whenever elites dislike an outcome.

Comparisons and precedents

  • Austria 2016 is cited as a European precedent for canceling a presidential round over irregularities.
  • Parallel debates with US 2016–2024 elections and “Russian interference,” Brexit, Georgia’s “foreign agent” law, and France’s handling of populist parties.

Broader worries: propaganda, platforms, and trust

  • Strong concern that modern social‑media algorithms (especially TikTok) make targeted psychological campaigns cheap and powerful, outpacing laws and institutions.
  • Others stress that systemic corruption, economic problems, and cultural backlash (e.g., against EU liberal norms) create fertile ground; foreign actors are accelerants, not root causes.
  • Several Romanians emphasize longstanding distrust in domestic parties, courts, and services; some view the annulment as necessary defense, others as a “soft coup” by an unpopular establishment.

Why is printer ink so expensive?

Economics & Business Model

  • Many comments frame ink pricing as classic “razor and blades”: cheap or loss-leading printers, high-margin consumables.
  • Some argue this is driven by competition on upfront printer price; profit must come from ink.
  • Others say price is simply “what the market will bear,” largely decoupled from manufacturing cost.
  • Debate on profitability: some claim printer makers aren’t hugely profitable; others point out shareholders and capital still demand high returns.

Lock-in, DRM & Legal Environment

  • Strong criticism of DRM, firmware updates, and chips that block third-party cartridges or degrade output.
  • Viewed as anti-competitive bundling: tying ink to printer brand and using legal tools to attack compatible cartridges.
  • Some argue the “razor and blades” story hides the central role of IP, regulatory capture, and lawfare in sustaining the model.

Printer Types & Usage Patterns

  • Broad consensus:
    • Laser printers are better for infrequent, document-heavy home use (no clogging, long-lasting toner).
    • Inkjets are better for high-quality photo printing and special media but require regular use.
  • EcoTank/ink-tank models get praise for cheap bottled ink but still need periodic use to avoid clogs.
  • Regional differences noted: in some countries lasers are much more expensive than inkjets.

Subscriptions, Surveillance & Privacy

  • Some recommend cheap printers plus ink subscriptions; others worry about telemetry and lack of firmware transparency.
  • Defenders say printers typically only send page counts and levels; skeptics distrust opaque “phone home” behavior.

Health, Environment & Waste

  • Concerns about:
    • Ultrafine particles and ozone from lasers.
    • Thermal paper fading and BPA exposure.
    • Waste from tossing whole printers when ink/toner is more expensive than a new device.

Workarounds & Alternatives

  • Refilling cartridges with syringes and bulk ink was and is possible but messy and undermined by DRM.
  • Many suggest:
    • Cheap monochrome laser at home + external services (drugstores, FedEx, local print shops) for color/photos.
    • Ink-tank or refillable systems for heavy color users.
  • Some wonder why there are no disruptive low-cost Chinese printers; speculation that technical difficulty and legal moats deter entry.

Kagi Teams

Search Quality and Overall Experience

  • Many long‑time users report significantly better results than Google, mainly due to fewer ads, less SEO spam, and higher density of useful links.
  • Others find Kagi “no worse” than Google, which is sufficient to justify paying for an ad‑free, user‑funded model.
  • Some users barely notice which engine they’re on, beyond lack of ads.
  • A few say Kagi’s results skew heavily to certain sites (e.g., Reddit) or feel limited, sometimes returning “no results” where Google returns noisy but broader coverage.

Customization and Features

  • Raise/Pin/Lower/Block domain controls are praised; one user found results improved after removing extensive filters.
  • There’s interest in stronger controls to downrank commercial/monetized sites and surface “non‑commercial passion projects.”
  • Universal Summarizer and result customization (favicons, site boosts) get positive mentions.

LLM Integration

  • Kagi offers an AI assistant and direct access to multiple “premium” LLMs (Claude, GPT‑4o, Gemini, Mistral, Llama).
  • Users can define custom “assistant flavors,” toggle web access, and apply search lenses.
  • Some see the LLM bundle alone as worth the subscription; others prefer cheaper pay‑per‑use APIs.

Pricing, Teams, and Adoption

  • Individual “Ultimate” vs “Team Ultimate” are effectively feature‑equivalent; differences center on billing (no annual discount on Teams, per‑active‑user billing, central management).
  • Teams can mix search‑only and LLM‑enabled seats.
  • Some argue $10–25/user/month is trivial if productivity improves; others note that enterprise procurement friction, not price, is the main barrier.

Comparisons to Other Tools

  • Google still wins on fresh news, local/business info, shopping, and Maps.
  • Users combine Kagi with Google via bang shortcuts when needed.
  • Alternatives mentioned: SearXNG, Brave Search, DuckDuckGo, Perplexity (more chatbot‑oriented), and self‑hosted solutions.

Privacy, Tracking, and Anonymity

  • Paid model and lack of ads are valued; some trust Kagi’s leadership with payment‑linked identities.
  • VPN use (e.g., Mullvad) can be blocked at registration/payment, which some accept as fraud‑prevention, others reject on anonymity grounds.

Yandex Integration Controversy

  • Discovery that Kagi pays Yandex (≈2% of subscription cost) for some search/image results sparked strong backlash.
  • Some canceled or won’t subscribe over funding a company now seen as closely tied to the Kremlin and Russian propaganda.
  • Others dismiss this as overblown or engage in “what about” arguments regarding Western companies; several emphasize that degrees of state control matter.

Debian opens a can of username worms

Scope of Debian Username Changes

  • Debian (via shadow-utils and adduser) is loosening username rules, potentially allowing UTF‑8, numerics, and more punctuation.
  • Many see this as risky: it diverges from long‑standing conventions and could break tooling that assumes conservative, ASCII‑only usernames.
  • Others argue the previous Debian‑specific patch was itself a mistake, and aligning with upstream / modern Unicode reality is overdue.

Unicode in Identifiers

  • Several comments note Unicode already defines identifier rules (TR31, RFC 8264/8265) and security guidelines (confusables, spoofing).
  • Libraries like ICU, libunistring, libidn, libu8ident exist, but adoption is patchy; many tools (e.g., grep variants) still handle Unicode poorly.
  • Advocates say: use these standards, apply normalization (e.g., NFKC), and restrict to safe categories (letters, digits) rather than “all of Unicode.”
  • Critics emphasize normalization, bidirectional text, and homoglyphs as a deep well of complexity and subtle bugs.

Internationalization vs ASCII-only Usernames

  • Pro‑Unicode side: legacy codepages were worse; many languages (CJK, Cyrillic, accents) were effectively excluded; it’s unfair and user‑hostile to keep ASCII only.
  • Anti‑Unicode or cautious side: usernames are low‑level identifiers; ASCII is a useful common denominator, especially when logging in from random keyboards or debugging over SSH.
  • Some propose: ASCII‑only for login names, but UTF‑8 for full names / display fields; others insist people should be able to log in with their real‑script names.

POSIX, Standards, and Practicality

  • POSIX “portable username” set is [A‑Za‑z0‑9._-] (hyphen not first). Numeric usernames are allowed there.
  • Some call this outdated and want UTF‑8 everywhere; others say POSIX’s role is to describe existing practice, and a UTF‑8 transition would be a massive, decades‑long, compatibility project.
  • There is disagreement whether standards bodies should “lead” (mandate UTF‑8) or “follow” (codify what major OSes already do).

Security, Shells, and Bug Compatibility

  • Allowing shell metacharacters, spaces, and exotic Unicode in usernames is seen as a security foot‑gun: shell injection, misparsed scripts, ambiguous logs.
  • Real vulnerabilities are reported where unsanitized usernames passed into scripts allowed ;, &, > etc. to execute arbitrary commands.
  • Some argue broken scripts are already wrong and should break so they get fixed; others stress that enterprises care about systems working today, not theoretical correctness.
  • Comparison is made to filenames with spaces: Unix tools historically broke, but Windows forced adaptation by using spaces in system paths.

Numeric Usernames and Identifier Design

  • Purely numeric usernames are criticized for colliding conceptually with numeric UIDs; tools often interpret “all digits” as UID, else as name.
  • This can create confusing or insecure behavior if a numeric name doesn’t match its UID or matches someone else’s UID.
  • Others note POSIX allows it; they propose local policy (e.g., disallow names equal to existing UIDs) or better ID schemes (prefixes, checksums, redundancy).

User Experience Anecdotes

  • Many recount systems failing on:
    • Diacritics in names (é, å, ç), apostrophes, or non‑Latin scripts.
    • Non‑ASCII passwords that can be set but not used to log in.
    • Windows and other systems mishandling Unicode in usernames or profile directories.
  • As a result, even users with non‑ASCII names often deliberately stick to ASCII for usernames and sometimes passwords.

Alternative Ideas and Side Discussions

  • Suggestions include:
    • Punycode‑like encodings for usernames (machine‑safe, user‑friendly display).
    • Treating usernames as opaque byte strings, punting encoding to higher layers.
    • Keeping login identifiers simple and using richer UTF‑8 identifiers only where genuinely needed.
  • A tangential discussion explores graphical / visual programming vs text, concluding that visual systems often become unmanageable “spaghetti,” and text remains the most practical representation.

Ukraine's three nuclear power plants have restored electricity production

Resilience and current role of nuclear power in Ukraine

  • Commenters note that Ukraine’s nuclear plants are now “basically the only functioning power plants,” supplemented by imports from the EU grid and new Western air-defense systems.
  • Several are impressed by the speed of grid repairs: major outages and damaged substations often restored within 48 hours, even in front‑line cities.
  • Nuclear units are seen as hard to physically destroy and politically risky to target; some argue Russia avoids direct attacks on reactor cores but heavily attacks surrounding grid infrastructure.

Decentralization vs. centralized generation

  • One camp advocates decentralization (rooftop solar, local PV, small generators, district heating) to make large‑scale disruption harder.
  • Critics counter that decentralized assets are much harder to protect physically and logistically, and depend on centralized components (substations, control systems, cloud platforms) that remain single points of failure.
  • Nuclear is defended as resilient, high‑output, and relatively well‑protected by air defenses; others highlight its poor maneuverability compared to gas/hydro and its dependence on a stable grid.

Technical protection measures

  • Proposed measures: air‑gapping control systems, strict personnel vetting and training, layered air defense, buried cables, and bunker‑like substations.
  • Others argue many of these are economically or physically impractical at national scale, especially armored substations or “mobile” nuclear plants. Existing floating reactors are cited, but there is disagreement over whether they meaningfully change grid vulnerability.

Attacks on infrastructure and civilians

  • Repeated claims that Russia strikes power infrastructure and civilian housing, hospitals, and cities to spread terror and lower morale; some mention explicit propaganda about “freezing” Ukrainians.
  • A minority suggests many residential hits are misses or due to military targets embedded in urban areas; opponents point to drone videos and documented strikes as evidence of deliberate targeting.
  • There is brief debate over whether attacking power grids is always a war crime, with distinctions drawn between coercive terror campaigns and strikes with clear military purpose.

Deterrence, retaliation, and escalation

  • One line of discussion: whether Ukraine should or will retaliate symmetrically against Russian power infrastructure to deter further strikes.
  • Arguments against: it risks eroding international support, strengthens Russian resolve, and provides propaganda material.
  • Arguments for: mutual vulnerability and clearly signaled “if you do X, we will do Y” threats could deter future attacks, but commenters note such pre‑announced red lines have largely not been used effectively.

The 70% problem: Hard truths about AI-assisted coding

Impact on junior developers and learning

  • Many fear juniors will rely on AI to “paste code that works” without understanding it, slowing their path to senior-level skills.
  • Others argue juniors can still learn by debugging AI-written code, similar to learning from bad Stack Overflow snippets.
  • A recurring concern: AI reduces opportunities for mentorship and may shrink the pool of experienced developers in 5–10 years.
  • Some see AI as an always-available tutor that can accelerate learning for motivated juniors, especially if used to ask “why” questions, not just to generate code.

Code quality, verification, and the “70% problem”

  • Common experience: AI can produce working scaffolding or 70–90% solutions, but fails on tricky logic, edge cases, architecture, and non-functional concerns (performance, security, accessibility).
  • Seniors report spending significant time refactoring, tightening types, adding tests, and removing redundant checks from AI code.
  • Trusting AI-generated tests or bindings without human-written specs is viewed as dangerous; tests may assert the wrong behavior.
  • Some advocate stronger use of property-based testing, static typing, and even formal verification, potentially aided by LLMs.

Productivity gains and their limits

  • Seniors often feel “dramatically faster” at boilerplate, cross-language tasks, and unfamiliar frameworks; juniors often get confused or misled.
  • AI excels at small, well-specified tasks (examples, APIs, “magical incantations”) and at explaining or transforming code.
  • For novel or complex systems, AI tends to loop, hallucinate APIs, or produce verbose, brittle solutions; 12-week projects don’t become 4-week projects, maybe 9–10.

Tools, UX, and integration

  • Chat-style interfaces and copy-paste are seen as major bottlenecks; deeper IDE integration (patch application, multi-file edits, context files like SPEC.md/LESSONS.md) is praised.
  • Some specialized tools (Cursor, Aider, etc.) partially address multi-file refactoring, but users still report friction, stuck agents, and deployment glitches.

Jobs, education, and long-term concerns

  • There is anxiety that AI will replace much “junior work,” reducing entry-level hiring and creating a future senior shortage.
  • University instructors report students overusing LLMs, failing to build foundational skills or even formulate questions.
  • Several see parallels to past hype cycles (4GLs, low-code, CASE tools): big boosts on “accidental complexity,” but essential problem-solving remains human.

Gordon Letwin OS/2 Usenet post (1995)

OS/2 vs Windows: technology and developer experience

  • Many recall OS/2 2.x as technically superior to Windows 3.0: true preemptive multitasking, better DOS support, memory protection, and solid APIs for threads, drivers, and comms.
  • OS/2 1.x was constrained by 80286 protected mode and real‑mode DOS sessions; 2.x was largely a 32‑bit rewrite targeting the 386.
  • Some highlight serious architectural issues: not truly multi‑user and a single input queue for the GUI, seen as a dead end without major rewrites.
  • Memory demands were high: 2.x “worked” with 4 MB but really wanted 8 MB at a time when most PCs had 2–4 MB.
  • Developer tools and ecosystem lagged: Windows had Visual Basic, Delphi, Turbo C++ and later strong Win32 tooling; OS/2 had some Borland support and IBM’s VisualAge, but not at the same breadth.

Business, pricing, and ecosystem

  • Lack of applications and weak IBM marketing/OEM deals are recurring themes.
  • OS/2 was expensive (both OS and suitable hardware), while Microsoft kept DOS/Windows/Office licensing cheaper and friendlier to OEMs.
  • Standardization around Windows drew developers and users; OS/2’s ability to run Windows apps ironically reduced incentive to target OS/2 natively.

Why OS/2 failed: competing explanations

  • One view: OS/2 2.x failed because it could run Windows apps, so developers stayed on Windows.
  • Counter‑view: the real failure was OS/2 1.x on 286; Windows 3.x on 386 exploited its weaknesses (esp. DOS multitasking), gained dominance, and by the time 2.x arrived the market was already decided.
  • Several commenters stress IBM’s corporate inertia and misreading of the PC/home market as at least as important as anything Microsoft did.

Microsoft, IBM, and CP/M/DOS history

  • Long subthread revisits IBM’s original PC OS deal: Digital Research’s CP/M‑86 negotiations, QDOS purchase, and MS‑DOS licensing.
  • Opinions differ on whether Microsoft behaved malignly or just opportunistically; some argue Gary Kildall “blew it,” others emphasize how the “went flying” story harmed his reputation.
  • Broader pattern raised: Microsoft repeatedly leveraging partnerships and legal pressure to its advantage; contrasted with IBM’s own problematic history.

Windows NT origins and VMS connection

  • Discussion covers hiring of the VMS team lead, reusing design ideas from a cancelled DEC project, and how this shaped NT.
  • DEC later sued over similarities to VMS internals and obtained favorable settlements and partnerships.
  • NT is seen as qualitatively better engineered than MS’s OS/2 work, and ultimately the line that displaced both OS/2 and Windows 9x.

Miscellaneous reflections

  • Standardization as a double‑edged sword (praised in OS/2 email; compared to EV charging standards).
  • Nostalgia for OS/2 Warp, RS‑232, Win32s, and early USB; plus side debates on typography (two spaces after periods, long “s”).

Why housing shortages cause homelessness

Housing Supply, Location, and Prices

  • Several commenters use the “musical chairs” analogy: if there are fewer affordable units than people, someone ends up unhoused.
  • Others stress the issue is not absolute unit count but where housing exists and at what price; abandoned or derelict stock in rust-belt cities or China’s ghost districts is not realistically usable for many.
  • Houston is cited as an example where abundant supply helped limit prices but at the cost of extreme sprawl.
  • Some distinguish “shortage” from “scarcity,” arguing regulation (e.g., rent control) constrains affordable supply.

Role of Informal Networks and Family

  • Many agree with the article’s point: when housing is cheaper and larger, family and friends can more easily host people; when it’s expensive, that safety net shrinks.
  • Examples of “informal economies” (couch-surfing, unofficial room rentals, favor exchanges) show how precarious households avoid literal street homelessness.
  • One proposal: allow vouchers to be used for renting a room from relatives.

Homelessness, Addiction, and Mental Illness

  • Thread is divided on causality: some argue unsheltered homelessness is “very clearly” a drug/mental illness issue; others say housing precarity often precedes and worsens addiction.
  • Several comment that living on the street itself drives substance use (e.g., to stay awake, cope with fear and stress).
  • Others counter that addiction can independently erode work, relationships, and housing, regardless of rent levels.
  • There’s concern that conflating homelessness with visible drug use diverts resources from people whose main issue is economic.

Local vs Imported Homelessness

  • SF and LA stats are debated: some highlight high shares of people coming from other cities; others point to survey data that most became homeless locally.
  • Reliability of self-reported origin surveys is questioned; some suggest people move to job centers or where services are available.

NIMBY, Gentrification, and Land Use

  • Strong disagreements over YIMBY vs NIMBY labels; some say “not YIMBY = NIMBY,” others describe being pro-density in general but opposing specific projects in cherished spaces (e.g., parks).
  • Gentrification is defended by some as positive if paired with protections and affordable set-asides; others link anti-density politics and zoning to constrained supply and homelessness.

Pathways Into Homelessness

  • One perspective: barring addiction or severe mental illness, it’s hard to become homeless without “burning” all savings and relationships.
  • Multiple replies rebut this with cascades: job loss, no savings, eviction, lack of transport, medical crises, domestic violence, youth kicked out, and perverse or inaccessible social programs.
  • Several argue a large share of the population is one serious shock away from homelessness, especially in high-cost areas.

Policy Approaches and Tradeoffs

  • Skepticism about large homelessness budgets (e.g., LAHSA) and low perceived impact; some fear spending attracts more unsheltered people.
  • Debate over housing-first vs treatment-first: housing plus intensive services is seen as ideal but extremely resource-intensive; others argue prevention and early support might be more cost-effective.
  • Ethical tension appears between practical constraints and the view that society owes basic housing and dignity, even for people with serious addictions or behavioral issues.

Air Canada to remove free carry-on from basic economy

Policy Details & Definitions

  • Change applies to “basic economy” fares: free overhead-bin carry-on removed, but one smaller “personal item” (handbag, laptop bag, small backpack) still allowed if it fits under the seat.
  • Multiple comments stress that “personal item” ≠ “carry-on,” though some smaller backpacks can count as personal items depending on size and airline rules.

Rationale, Unbundling & “Gouging” Debate

  • Supporters frame this as unbundling: pay only for what you use, enabling lower sticker prices and more options for highly price‑sensitive travelers.
  • Critics argue prices don’t actually drop; instead, the same or higher total cost buys fewer services (“shrinkflation / hidden price hike”).
  • Some emphasize airlines’ thin profit margins and inflation, saying “gouging” is misused; others counter with executive pay and high absolute fares.

Overhead Bins, Checked Bags & Incentives

  • Overhead bins are routinely full; gate-checking is common and stressful.
  • Many avoid checking bags due to lost/lated luggage, theft, damage, and long waits at carousels—problems several say are especially bad with certain carriers/airports.
  • Some think airlines created the bin problem by charging for checked bags, pushing passengers to carry on more. Suggestion: reverse incentives—free checked bag, paid carry-on with guaranteed bin space.

Comparisons to Other Airlines & Markets

  • WestJet and some U.S. and European low-cost carriers already charge for standard carry-ons; this is seen as competitive pressure on Air Canada.
  • Disagreement over how widespread free carry-on remains in Europe; distinction between legacy carriers vs low-cost carriers.

Passenger Experience, Behavior & Extremes

  • Complaints about “gate humping,” oversized roller bags, and cognitive load from complex fare structures.
  • Some would gladly trade comfort and amenities for cheaper fares; others say economy is the only realistic option and is being degraded.
  • Various tongue‑in‑cheek ideas (standing-room tickets, pay-per-use toilets, luggage-loading for points) highlight fears of ongoing “enshittification.”
  • Concern raised about how strict baggage policies might impact travelers with disabilities or temperature‑sensitive medications.