Hacker News, Distilled

Telehealth prescribing and enforcement

• Some see the arrested company as an example of “good concept, bad execution”: telehealth made ADHD care accessible, but aggressive ad campaigns and loose screening created moral hazard.
• Others argue the broader pharmaceutical system is already rife with abuse (e.g., opioids), so singling out telehealth is selective.
• A few note that PayPal’s early success also relied on skirting rules, drawing parallels with “move fast” startup culture.

ADHD diagnosis and overprescription

• Several commenters think ADHD is overdiagnosed, especially in tech, and predict a future scandal over inflated diagnoses used to access Adderall.
• Others counter that ADHD lies on a spectrum; many people have meaningful symptoms, so higher diagnosis rates may reflect unmet need rather than pure abuse.

Lived experiences with stimulants

• Strongly mixed reports:
  • For many with ADHD, stimulants are “life-saving,” enabling basic functioning, planning, and follow-through.
  • Others describe unpleasant effects: somnolence, “zombie” state, emotional blunting, anxiety, or severe crashes.
  • Non-ADHD or recreational use is reported as euphoric, energizing, and motivating, but often with long-term costs and burnout.
• Multiple users find Ritalin/methylphenidate more moderate and less abusable than Adderall; some argue Adderall should be a last-resort drug.

Adderall shortages and DEA quotas

• Many ADHD patients describe monthly struggles to fill prescriptions, with shortages exacerbating executive-function challenges.
• One side blames DEA production caps and rigid controlled-substance rules, calling the shortage largely government-created.
• Others note manufacturers held substantial raw material during the shortage and highlight a spike in new prescriptions, arguing overprescribing and industry behavior also share blame.

Drug policy, access, and liberty

• A major subthread debates whether adults should buy Adderall (and even Xanax) freely, like alcohol or nicotine.
• Pro-legalization voices say the drug war causes massive harm, criminalizes personal choices, and makes quality control impossible.
• Opponents stress high addiction and mental-health risks, argue many people cannot self-regulate, and support prescription-based “sensible checks.”
• Historical and international differences (e.g., Adderall bans in some countries) are cited, but their correctness is contested.

Productivity and “smart drugs”

• Some see stimulants as productivity boosters that governments irrationally restrict.
• Others cite research and personal experience that they can increase motivation but degrade deep work and decision quality over time.

Security, Trust, and “Malicious Cables”

• Several commenters note that any USB-C cable (with or without a display) can hide chips; modern USB-C already requires e-markers in many cases, so visual inspection isn’t sufficient.
• Some recommend “policy controls”: buy from USB-IF members and authorized distributors instead of random low-cost vendors, as a low-effort risk reduction. Others argue this barely moves the needle without deep firmware verification.
• Discussion of known attack cables (e.g., Wi‑Fi-enabled red-team tools) shows such devices are real and fairly usable, though expensive compared to normal cables.
• Data blockers (“USB condoms”) can block data lines, but then you must trust the blocker’s circuitry; minimal, transparent, resistor-only versions are favored by the more paranoid.
• Consensus: if you’re worried about standalone malicious cables, a display doesn’t materially change the risk; it’s fundamentally a trust/supply-chain problem.
• USB authentication / crypto was proposed in the standard and some data is already present in cables, but commenters are unaware of widespread real-world use.

---

Usefulness of Display Cables vs. Dedicated Power Meters

• Many find display cables handy to:
  • Verify fast-charging is active and at roughly what wattage.
  • Debug bad ports, flaky cables, or vague charge indicators (earbuds, controllers, laptops in bags).
  • Check real power draw from chargers, batteries, and small solar setups.
• Others strongly prefer standalone USB power meters, which:
  • Show more parameters (V, A, W, sometimes charge counting).
  • Offer logging, scripting (e.g., Lua), PD protocol inspection, and integration with dummy loads.
  • Are better suited for serious troubleshooting, battery health checks, and transient/overcurrent diagnostics.

---

Reliability, Safety, and Quality

• Multiple reports of cheap display cables popping, smoking, or killing devices; some users warn strongly against low-end versions.
• Counterpoints: others use very cheap AliExpress cables daily at moderate power levels without issues.
• Debate over midrange branded accessories: some see them as “cheap rebrands,” others report good long-term experience and responsive warranty support.

---

USB-C Power & Cable Complexity

• USB-C power standards are described as “a mess”: devices sometimes refuse to charge above low wattages despite seemingly compatible hardware.
• Commenters argue that widespread use of power meters (cables or boxes) would help non-technical users understand charging limits and diagnose weak links (device, cable, or charger).
• There is demand for tools that also test data throughput, but such comprehensive testers are perceived as specialized and expensive.

Preconditions and Pathways for Horse Domestication

• Debate over whether agriculture is a prerequisite:
  • One side argues you need settled, agricultural societies to manage breeding in captivity.
  • Others counter that nomadic or semi-nomadic groups can and did domesticate livestock, citing reindeer and horse-based nomadic cultures.
  • A specific early horse culture is cited as lacking crop evidence, challenging the “agriculture first” view.
• Disagreement on timing: some claim horses were domesticated before agriculture; others correct that agriculture predates horse domestication by several millennia.

North American Horses and Clovis Context

• Horses evolved in North America, coexisted with humans, and disappeared ~10,000 years ago along with other megafauna.
• Causes of extinction are presented as multi-factorial: human hunting, climate change, and disease.
• Modern North American “wild” horses are described as descendants of domesticated European horses introduced in the 16th century.

How Domesticated Are Horses?

• Several participants note horses retain strong flight instincts and can be dangerous despite training.
• Compared to sheep, cattle, and dogs, horses are seen as “more wild,” though others point out many farm animals are quite aggressive or shy when not handled regularly.
• Zebras and moose are invoked as examples of equids/large mammals that have resisted domestication, highlighting horses’ relative tractability.

Definitions and Scope of Domestication

• Distinction drawn between:
  • Domestication of a species vs. taming an individual.
  • Feral vs. wild vs. domesticated populations (dogs, cattle, dingoes, buffalo).
• Some argue cats are only semi-domesticated; others report extensive success training and living closely with cats.
• Self-domestication is suggested for cows, dogs, possibly deer, and even humans; linked to reduced aggressiveness and “domestication syndrome” traits.

Multiple Horse Domestications & Occam’s Razor

• Some are skeptical that horses were domesticated twice, invoking Occam’s razor to favor a single origin.
• Others argue that repeated domestication events are plausible whenever humans live alongside a suitable species and that Occam’s razor is misapplied when genetic evidence is available.
• A side discussion references fox-domestication experiments to estimate how many generations meaningful behavioral change might require, with disagreement over whether that implies hundreds or thousands of years for horses.

Yamnaya Expansion and Role of Horses

• Discussion about whether horse use explains rapid Yamnaya/steppe expansions, or whether cultural factors (raiding, warfare, social organization, lactose tolerance) are more central.
• Some emphasize horses’ military advantage; others note large distances can be covered even on foot over generations, so mobility alone may not be decisive.

Nostalgia and Use Cases

• Many commenters love the idea of a tiny Mac running classic System 7, seen as the peak of classic Mac OS.
• Some want a “zen mode” laptop or ultra‑light machine dedicated to System 7–9 era software, with all‑day battery life and minimal distractions.
• Others see it as a great first computer for kids with strictly limited capabilities.

Hackintosh and Modern macOS

• A few hoped this was a cheap Hackintosh running current macOS.
• It’s noted that Hackintosh is still possible on Intel, but support is clearly in decline.
• GPU support is the main barrier for “cheap” builds; older AMD cards or supported iGPUs are commonly used.
• Those who have run Hackintoshes report good results but say OS updates can be painful, often consuming weekends; some cope by staying several versions behind.

Hardware Choices and Emulation

• The standout element for many is using the RP2040’s PIO to generate VGA and act as a quasi‑68k, rather than just running Linux plus an emulator.
• Some argue other MCUs (STM32, ESP32) can do similar video output, but others reply that RP2040’s PIO is unusually flexible compared to single‑purpose peripherals.
• There’s interest in FPGA or ESP32‑based approaches, but some say software emulation is already “good enough” and more flexible than cycle‑accurate hardware.

Displays, CRTs, and X‑Rays

• Commenters want authentic CRT aesthetics; ideas range from curved lenses over flat panels to doubly‑curved OLEDs.
• Others point out that with 4K HDR panels and devices like Retrotink 4K, CRT emulation can already look very convincing.
• There’s debate over CRTs and X‑rays: electron beams do produce some X‑rays in the phosphor, but they’re low‑intensity and shielded by the glass.

Memory, PSRAM, and Performance

• Some wonder about storing emulated RAM in flash to replicate the original 512 KB; others flag flash wear and missing PSRAM support on RP2040.
• Workarounds using PIO or QSPI PSRAM are discussed, and ESP32 is noted as having native SPI‑PSRAM expansion.

Cables, E‑Waste, and Scavenging

• The chance discovery of a street VGA cable resonates; many share stories of finding or hoarding old cables and hardware.
• Thrift stores, surplus/auction sites, and recycling programs are recommended sources.
• Several criticize bundled cables as a major source of e‑waste and argue devices should ship without most cables.

Intuition Behind Bouba/Kiki

• Many associate “bouba” with round shapes and “kiki” with spiky ones because:
  • Soft, rounded things in the world tend to make softer, lower, more “bouba-like” sounds; hard or sharp things produce brighter, sharper, “kiki-like” sounds.
  • Mouth and tongue positions differ: rounded lips and softer closures for /b/ and /u/ vs tighter, more angular gestures for /k/ and /i/.
  • In Latin script, letters in “bouba” (b, o, u) look rounder than those in “kiki” (k, i), though commenters note this is script-dependent and not historically stable.

Sound, Waveforms, and Perception

• Some suggest “bouba” corresponds to smoother, less “spiky” waveforms; “kiki” to noisier, high-frequency spectra.
• Others question whether humans actually intuit waveform “shape” vs just perceiving timbre and frequency.
• Several point out that the auditory system performs a kind of Fourier decomposition, so frequency content does encode aspects of the waveform, but mapping that to visual shape is debated.

Cross‑Modal Perception & Childhood

• Anecdotes from education and art:
  • Children can readily “draw” sounds (e.g., high heels as spiky lines, boots as big waves), seen as evidence of natural cross‑modal mapping.
  • Adults often lose or inhibit this ability, possibly due to socialization, over-analysis, or neural pruning.
• Multiple posters describe synesthesia-like experiences (letters/days as colors, shapes, or textures), often stronger in childhood and fading with age.

Language, Order, and Sound Patterns

• Discussion branches to “irreversible binomials” (e.g., “salt and pepper”, “plus or minus”) and adjective order in English (“Royal Order of Adjectives”), where certain sequences just “sound right”.
• Some argue it’s mostly convention; others point to rhythmic and prosodic preferences.
• A question about German grammatical gender being driven by “what sounds right” is met with skepticism; endings often predict gender, but many cases appear arbitrary.

Cross‑Linguistic Scope & Universality

• Cited work claims the effect appears in many languages, including some without writing, but not in Mandarin; this weakens “universal” claims.
• Another study suggests Chinese- vs English-speakers map shapes differently to tone contours, indicating cultural/linguistic modulation.

Related Naming Patterns & Applications

• Parallels drawn to “mama/dada” patterns, with some attributing them to articulatory ease plus parental interpretation, not deep symbolism.
• Bouba/Kiki inspires:
  • A constructed script, a cooperative board game, and tattoo ideas.
  • Art-teaching exercises to distinguish innate from culturally constructed meaning in images.

Power, DC Use, and Off-Grid Scenarios

• Device uses 30V DC at up to 2A via an AC adapter; running directly from 12V systems (boats, vans, RVs) requires a DC–DC boost or inverter.
• Many mobile users prefer native 12–48V DC support; current approach adds inefficiency (10–20% conversion loss) and complexity, which is significant for small sailboats or tight solar budgets.
• Power draw is estimated around 30–40W nominal, 60W PSU max, plus optional heating for snow melt; some see this as high for “portable,” others note that modern van/boat lithium systems and solar can easily support it.
• Some users already run Starlink off 12V (modding older dishes, using PoE injectors, or inverters) and consider power “annoying but manageable.”

Portability, Roaming, and Use Cases

• Mini dish size ~29×25 cm, ~1.1–1.16 kg with kickstand; seen as viable for backpacking if power is solved.
• Roam plans allow cross-border use (“global roaming”) but at higher cost; people debate fairness of charging more for ignoring capacity planning and regulations.
• For remote work, many see Mini as attractive backup/roaming gear, especially in RVs, boats, and rural areas.
• Activation can be done ad hoc; accounts can be paused and resumed by month, which some already use for occasional travel.

Performance and Bandwidth Expectations

• Mini is expected (but not confirmed) to offer lower bandwidth than full-size dishes, possibly similar to Amazon Kuiper’s “¼-speed” portable terminal idea.
• Some think this is fine for typical roaming usage (email, low-res video calls, browsing), but potentially limiting for heavy upload workflows.

Competition and Constellation Context

• Several comments frame Mini as an answer to Amazon’s Kuiper portable terminal, though others argue Starlink has long planned such hardware and Kuiper is far behind in satellites launched.
• Debate over whether Kuiper is “vaporware” or just early-stage; some express concern about a Starlink near-monopoly in LEO broadband.

Backup Internet and Pricing

• Many see Starlink (and especially Mini) as a strong backup for rural or unreliable fixed ISPs; concerns remain about paying full-month fees for short outages.
• Pricing varies widely by country and appears tuned to local income, competition (e.g., fiber, 4G/5G), and satellite saturation.

Nature of Expertise

• Several distinguish “expert” from “teacher”: expertise = deep, practiced, executional skill; teaching and communication are separate abilities.
• Others argue that being unable to explain core aspects to non‑experts is a strong negative signal; an expert should at least convey challenges, tradeoffs, and big picture.
• Some stress that expertise exists on a spectrum, not as a binary; only peers in the same domain can reliably judge someone’s level.

Communication, Depth, and Limits

• Ongoing debate around the claim that “if you can’t explain it simply, you don’t understand it.”
• One side: real experts can adjust explanations to the listener, use analogies, and walk down abstraction levels (examples with Rust vs. Python, memory, fire, magnets).
• Other side: many topics (advanced physics, math, niche compiler work) simply cannot be meaningfully explained to true laypeople without years of prerequisite study.
• Good communication is described as its own skill; some experts are poor communicators, and some non‑experts are great explainers.

Distinguishing Experts from Imitators

• Suggested heuristic: keep asking “why” and probe first principles, edge cases, and tradeoffs; experts handle nuance, shift perspective, or admit ignorance, while imitators stall or bluff.
• Counterpoint: skilled bullshitters can improvise plausible answers; interviews and surface Q&A are easily gamed.
• Signs of expertise mentioned: ability to fix real problems, connect technical choices to business/customer value, adapt prior solutions, and recognize unknowns and risks.
• Several note that genuine experts often show humility and clear awareness of what they don’t know.

Titles, Incentives, and Environments

• Many report “senior” or “expert” titles being loosely tied to time served or networking rather than deep knowledge.
• In hiring, “expertise” interviews frequently involve non‑experts evaluating fashionable skills (e.g., AI/ML), leading to mutual pretense.
• Academic incentives (publish‑or‑perish, grants, tenure) shape behavior; tenure can free people to pursue riskier work or to coast.

Imitators, Hype, and Domains

• Commenters compare imitators to current AI systems: good at surface mimicry, weak under probing.
• Some fields (finance, macro predictions) are seen as over‑claiming expertise; luck and marketing may dominate.
• A more charitable view: most “imitators” are just early‑stage learners without access or experience; with guidance, some can become true experts.

Phonological similarities

• Several comments attribute the “Japanese sounds African” effect to similar sound systems: mostly consonant–vowel (CV) syllables, few final consonants, roughly five vowels, and pitch patterns.
• Languages mentioned as sounding surprisingly similar to Japanese include Swahili and other Bantu languages, Finnish, Hawaiian, Māori, Yoruba, and some Nigerian languages.
• Simple syllable structures (CV or CV + limited final consonant) are said to be very common worldwide and contrast with “cluster-heavy” languages like English or Czech.

Vowels, pitch, and phonetic detail

• Discussion of vowel inventories: Spanish and Japanese both have five vowels, but details like exact [e]/[ɛ] quality differ; several speakers say they cannot reliably hear this distinction.
• English vowels are described as atypical and often diphthongal, contributing to mismatch with continental languages.
• There is confusion over whether Japanese is “unpitched”; others note Japanese has pitch accent, and some African languages (e.g., Yoruba) are tonal, making Japanese less alien to their speakers.

Orthography and transcription

• Latin-based transcription compresses diverse sounds into ~26 letters; similarities look weaker in IPA.
• Katakana is criticized as “broken” for rendering English but defended as internally consistent for Japanese pronunciation.
• English spelling is contrasted with languages like German; spelling bees are framed as an artifact of English’s irregularity.

Coincidences, puns, and anecdotes

• Many cross-language puns and near-matches are listed: Japanese with Swahili, Hebrew, Spanish, Shona, Nigerian names, and even brand and place names.
• Some apparent matches involve onomatopoeia or Chinese-derived readings in Japanese.
• Multiple anecdotes show African or European names being misread as Japanese because of similar syllable patterns.

Chance vs deep relationship

• One side argues repeated patterns hint at a “missing link” between language families.
• Others strongly favor coincidence and convergent evolution: human vocal tracts favor certain easy patterns (open syllables, few clusters), so unrelated languages often resemble each other.
• Lexicostatistical work cited in the thread finds <30% of similar-sounding items share meaning, classified as “accidental evidence,” which some still find surprisingly high.

Skepticism about macro-families and the article

• Claims about Ural–Altaic or long-range ties (e.g., Austronesian–Japanese, Bantu–Mongol) are treated as doubtful or lacking strong evidence.
• Several commenters say the linked article mostly lists examples, misjudges which names really sound “Chinese,” and does not convincingly answer “why.”

Perceived purpose and value of SICP

• Many see SICP as a foundational text on how computation and abstractions work (procedures, data, interpreters, evaluators, types as tags), not an algorithms reference.
• Readers report long‑term changes in how they think about language constructs, problem decomposition, and DSLs.
• Some argue the main gains are conceptual (e.g., understanding interpreters, OO from first principles), which later transfer well to other languages.
• Others think its influence has encouraged over‑abstraction and inefficient software.

Suitability for beginners vs experienced programmers

• Several commenters read it after years of professional work and found it eye‑opening, especially if their background was mainly in mainstream imperative/OOP languages.
• Others found it redundant with a solid CS education or prior experience with interpreters/FP.
• Some say it’s a poor first book: too mathy, abstract, or “quixotic,” and better as a second‑pass or capstone text.
• A few report bouncing off early chapters and never returning; a minority say it nearly put them off programming entirely.

Scheme/Lisp vs mainstream languages (esp. JavaScript)

• There’s extensive counterfactual debate about “what if the web had chosen Scheme instead of JavaScript.”
  • Pro‑Scheme side: simpler core, proper tail calls, call/cc, macros, clearer semantics.
  • Skeptical side: browser language success depends on syntax familiarity, ecosystem, and corporate needs; Lisp syntax would likely have limited adoption and not fixed JS’s design‑in‑a‑rush problems.
• Discussion of Erlang vs Elixir is used as an example: same VM, but more familiar syntax and tooling helped Elixir spread.

Syntax, cognition, and structural editing

• Long argument over whether curly‑brace / Algol‑style syntax is “innate” or just historical accident.
• Some stress redundancy and varied delimiters as helpful for human error correction; others value Lisp’s uniformity and ease of macro‑based extension.
• Parentheses complaints are challenged with structural editors (paredit, smartparens, parinfer) and IDE support, but critics still find S‑expressions visually noisy or cognitively heavy.

Lisp in practice: power vs maintainability

• Praised features: REPL‑driven development, macros, interactive introspection, DSLs, stable standards, named arguments and documentation in Common Lisp.
• Criticisms: fragmentation, small ecosystems, “everyone invents their own abstractions,” divergent styles, making large projects hard to maintain and onboard to.
• Some argue other languages have absorbed many Lisp innovations (GC, higher‑order functions) except S‑expression syntax, which remains niche.

Pedagogy and course design

• Conflicting TA reports:
  • One camp says Scheme’s small, uniform core lets courses spend minimal time on syntax and focus on ideas; students handle it well.
  • Another camp says “everything looks the same” causes persistent confusion; abstractions are taught before students have concrete needs for them.
• Debate over whether intro courses should prioritize conceptual depth (SICP, Scheme) or more “extroverted” projects tied to real systems (Python, robots, web).

Related works and resources

• Comparisons to “Paradigms of Artificial Intelligence Programming” (PAIP): SICP is more academic and language‑agnostic; PAIP is more Common Lisp‑ and GOFAI‑focused, with more practical software design.
• Multiple links mentioned: new official SICP HTML site, third‑party EPUB, JS and Python adaptations, and classic lecture videos.

Book content & focus

• Described as an academic but readable history and technical study of SimCity and related “Sim” games.
• First part: historical antecedents of simulation and city models (tabletop, analogue computers, systems thinking, cellular automata, artificial life).
• Second part: design and implementation of SimCity, Maxis’s history, and play experience. Includes detailed diagrams of clocks, tile encoding, main loop, and map-scan algorithms; no code listings.
• Scope is pre-EA SimCity: original, SimCity 2000, and SNES version. Later titles only appear as context, e.g., SimCity 3000’s troubled development and role in weakening Maxis.

Reception and expectations

• Several readers are enthusiastic, calling it engaging, deeply researched, and historically rich, while stressing it is “academic” rather than purely anecdotal.
• Some are attracted by its origin-story angle and technical detail; others compare it to more “fun” narrative histories and hope to read it later or via libraries.

Pricing and formats

• Multiple comments note odd pricing: ebook more expensive than paperback, high prices for related MIT Press titles, and confusion about size/format.
• Some lament lack of bundled ebook with print purchases.

Simulation vs game debate

• Extended debate on whether SimCity is meaningfully a “simulation” or “just a game.”
• One side: it’s a toy model with many shortcuts tuned for fun, still a simulation on a spectrum.
• Other side: its design goal was fun, not realism, so extrapolating to real-world cities is misleading; analogies are drawn to Monopoly.
• Counterpoints note all models simplify, many games are simulations to some extent, and that even very simple economic models influence real policy.

Simulation, learning, and rhetoric

• Discussion of “Simulator Effect”: players mentally overestimate model depth, filling gaps with imagination; designers deliberately offload complexity to the player’s mind.
• Example from The Sims: zodiac signs are purely cosmetic, yet testers perceived behavioral effects.
• Cited rule of thumb: don’t simulate more than one layer below what the player can actually observe.
• Comments reference “procedural rhetoric” and how simulation rules can convey ideology or propaganda, intentionally or not.
• Thread explores how simulations can teach concepts that are hard to grasp via equations alone, including historical analog mechanical models and classroom city-building exercises.

Maxis, Spore, and SimWorld

• The book’s author appears in-thread, answering questions about covering SimEarth, SimAnt, SimLife, and especially The Sims to explain Maxis’s broader arc.
• Some comments recount a shelved “SimWorld” vision to interconnect Sim games (e.g., zooming from SimCity into The Sims), influencing The Sims’ architecture and expansion model.
• Spore is discussed as a bold but compromised project; pre-release talks are praised, and there is curiosity about how marketing vision diverged from shipped game.

Related resources and talks

• Numerous links shared: historical talks on simulation UI, early The Sims demos, long-form interviews, an academic anthropology book on artificial life communities, and essays on SimCity in education.
• There is interest in similar works that blend history, ethnography, and technical depth; a few related books and MIT Press series are suggested.

Indie city-builder project & nostalgia

• An indie developer presents a retro-style city builder aiming for deeper simulation, with features like player-designed buildings, visible interiors, citizen-level modeling, and mixed-use zoning. Community responds positively and requests creative modes and GOG release.
• Several reminiscences of formative experiences with Sim games (SimEarth, SimAnt, SimFarm, paper-and-pencil “SimCity”), emphasizing their impact on thinking about systems, sustainability, and even career choices.

Scope of Edinburgh’s Ban

• Ban targets ads on council-controlled sites only; private property and media remain unaffected.
• Prohibited categories include airlines/airports, fossil fuel companies (including petrol stations and fuel ads), cruise holidays, and most car ads.
• For cars: bans petrol, diesel, hybrids, PHEVs, and all SUVs; allows battery-electric and hydrogen cars that are not SUVs.
• Some see the headline focus on “SUVs” as misleading since the policy is broader.

Arguments in Favor

• Seen as a modest but positive step to reduce demand for high-carbon products.
• Compared to existing restrictions on alcohol/tobacco ads.
• Framed as addressing a “tragedy of the commons” where voluntary action is insufficient.
• Supporters argue perfect solutions shouldn’t block incremental progress.

Free Speech and Governance Debate

• Critics call it censorship and a violation of free speech and basic rights.
• Others respond that:
  • It limits commercial advertising, not individuals’ speech or product availability.
  • Corporations should not be treated as rights-bearing speakers in the same way as people.
• Some worry about “ruling class” hypocrisy if politicians still use banned products.

SUV Proliferation and Regulation

• One view: environmental and fuel-economy rules created an “SUV loophole,” making trucks/SUVs more attractive to manufacturers.
• Counterview: consumers choose SUVs for flexibility (towing, cargo, rough weather), and crossovers now get mileage close to sedans.
• Several note that modern “SUVs” are mostly crossovers on car platforms, not truck-based, with smaller MPG gaps.
• Others argue marketing plus looser standards steered demand.

Safety, Urban Form, and “Car Obesity”

• Pedestrians describe feeling less safe around larger vehicles and in streets where oversized cars barely fit.
• Discussion of an “arms race”: people upsize to feel safe against other large vehicles, worsening danger to pedestrians and smaller cars.
• Some attribute larger sizes partly to safety regulations (thicker structures), others to fashion and poor urban design that prioritizes cars.
• Disagreement over how “dangerous” roads really are; US per-capita fatality rates are cited as far higher than peer countries.

PHEVs and Vehicle Emissions

• Policy’s exclusion of PHEVs is questioned; some argue typical trip lengths make them very effective.
• Defenders of the exclusion cite studies and reports that many PHEV owners rarely plug in, leading to modest real-world savings.
• Others counter that home-charging incentives are strong and that PHEVs can “strategically dominate” EVs in some use cases (battery use, towing, infrastructure limits).
• Some suggest that if car ads are restricted at all, perhaps all car ads should be, since manufacturing, tires, and roads also emit.

Plastics, Single-Use Goods, and Externalities

• One thread questions whether bans on single-use plastics are “sensible,” arguing alternatives like paper or cotton can be environmentally worse over their life cycle.
• Others push back: plastic’s ocean pollution and microplastics are distinct harms; source-critical reading of pro-plastic opinion pieces is urged.
• Proposal to tax environmentally harmful materials instead of banning them, though skeptics note regulatory capture and weak taxation due to industry influence.

Heating and Building Efficiency Side Discussion

• Edinburgh’s old, protected buildings often use electric storage heaters and single glazing.
• Some praise storage heaters for using off-peak electricity; others say they perform poorly, overheating at night and running cold in the evening.
• Heat pumps are cited as far more efficient; insulation and timing of heat delivery are emphasized as key to efficiency.

Overall framing

• Many see the article as an apples-to-oranges comparison: Pi is primarily an embedded / education platform, while tiny mini PCs are small general-purpose x86 computers.
• Others argue this comparison is fair for common real-world use (home servers, media boxes, small lab machines), where GPIO isn’t used.

Where Raspberry Pi still shines

• Strong points: GPIO header, well-documented hardware, big hobbyist ecosystem, easy flashing of OS images, lots of tutorials, and education focus.
• Ideal for: hardware hacking, sensors/relays, robotics, GPIO-heavy projects, solar/battery-powered setups, ultra-low-power DNS/DHCP/“always-on” appliances.
• Some run multi-function home automation or solar-monitoring stacks entirely on Pis and are satisfied with stability and performance.
• Pi Zero / Pico class boards and ESP32-type MCUs are seen as better fits for many simple “IoT” tasks than full Pi 4/5s.

Where mini PCs / N100 / thin clients win

• Used enterprise “tiny/minimicro” PCs, thin clients, and new N100-based boxes often:
  • Offer far higher CPU performance, x86 compatibility, better media codecs, QuickSync/Quicksync-like hardware transcoding.
  • Have built-in SSD/NVMe, more RAM, more I/O, and run standard Linux/Windows without ARM quirks.
• Frequently used as:
  • Home servers (containers, VMs, photo management, NVR, media, Kubernetes labs).
  • Quiet routers/firewalls and general homelab nodes.
• Many report idle power of ~4–10 W, which narrows the traditional ARM-vs-x86 efficiency gap.

Power, thermals, and noise

• Pi 4/5 often need active cooling under load; Pi 5’s official heatsink includes a fan (though idle is usually fanless).
• Some mini PCs are fanless or can be moved to a closet; others have unavoidable fan noise.
• Debate over power: some say N100/low‑TDP Celerons idle near or below Pi 4/5; others cite measurements where Pis are still lower, especially older 2/3 models.

Price, storage, and reliability

• Once you include case, PSU, and decent storage, a Pi 5 (especially 8 GB + NVMe) approaches or exceeds low‑end mini PC pricing.
• Many complain about SD cards as system disks on Pis: corruption, wear, and sensitivity to bad power; SSD/NVMe on x86 is viewed as more robust.
• Others counter that you can boot Pis from USB SSD and that cheap used PCs can have unknown-quality power supplies.

Software and ecosystem debates

• Pi ecosystem is praised for documentation, community, and “things just work,” especially around GPIO.
• Critics note:
  • x86 has vastly more general-purpose software.
  • Pi’s mainline Linux support has historically lagged and still relies on a vendor kernel for full features, especially on Pi 5.
• Some argue other ARM SBCs with Armbian/DietPi now have decent support; others say they still lag Pi in polish.

Broader context and concerns

• Several note Pi’s role drift: from cheap teaching tool toward more expensive, general-purpose “little PC,” where it compares poorly to mini PCs.
• Friction points: price increases, supply-chain era preference for industrial customers, odd Pi 5 power-supply requirements, and ongoing SD/thermal quirks.
• Consensus pattern:
  • If you need GPIO, tight integration with physical hardware, or very low-power always-on nodes → Pi / microcontrollers.
  • If you want a small, quiet, capable server or desktop-like box → used mini PC / N100 / thin client is usually a better fit.

AMD GPU Software Stack vs. NVIDIA CUDA

• Many commenters argue AMD’s core unsolved “hard problem” is its GPU software stack (ROCm, drivers) for ML, which is viewed as fragile, poorly supported, and far behind CUDA.
• Users report ROCm crashes, awkward installation (especially on Debian/Ubuntu), limited “official” GPU support, and long‑standing instability in past APIs (OpenCL, Vulkan compute, OpenGL).
• Others note ROCm has improved noticeably since the Frontier supercomputer work; on supported hardware with the recommended kernel it can be usable, and some consumer cards work via environment overrides.
• Consensus: NVIDIA’s stack is “least bad” and generally “just works,” from low‑end cards to data‑center parts, whereas AMD often requires hacks and has inconsistent support matrices.

HPC Focus vs. AI/ML Market

• Several posts stress AMD historically targeted HPC and FP64 workloads (national labs, Frontier, El Capitan), not deep learning.
• ROCm was initially optimized for DOE supercomputers and MI‑series accelerators, not consumer GPUs; this explains narrow “official” support.
• Critics counter that AMD underinvested in GPGPU software for more than a decade, even while spending heavily on acquisitions and buybacks, and missed visible “dense compute” and AI trends.

Lisa Su, Software Reticence, and Interview Takeaways

• Some readers see the interview as revealing a deep hardware bias: Su repeatedly frames herself and AMD as semiconductor‑focused and downplays software shortcomings.
• Her denial that AMD ever had a software problem, and lack of explicit contrition or strong “software-first” messaging, is read as bearish by skeptics.
• Others defend her track record, noting AMD was near bankruptcy pre‑Zen, and turning it into a profitable multi‑line semiconductor company is itself a major “hard problem” solved.

x86, ARM, and Long‑Term Prospects

• Debate on whether AMD’s x86 strength is a “Titanic” in a world moving to ARM (Apple M‑series, Graviton, Snapdragon X, in‑house cloud CPUs).
• Some argue ISA matters less than execution; AMD already has ARM experience and sees itself as a “compute company.”
• Others fear commoditization: as ARM spreads and hyperscalers design their own chips, AMD’s CPU margins and moat may erode, making missed software bets more damaging.

Salting, union rights, and lying about work history

• Many were surprised that “salting” (getting hired to organize a union) and lying about union-related employment can be protected activity.
• Clarification from the thread: protection is narrow — you can misstate or omit union-affiliated employers, but not fabricate skills, degrees, or entire careers.
• Rationale argued by supporters: if employers can fire for “lying” about union work, they can indirectly punish protected union activity and make salts unemployable.
• Critics find this counterintuitive or “ridiculous,” worrying it legitimizes lying; others respond that it’s analogous to lying about pregnancy or union affiliation where disclosure would enable illegal discrimination.

Scope and process of the NLRB ruling

• This is an Administrative Law Judge (ALJ) decision, described as a strong recommendation to the NLRB, not final law.
• A 3‑member NLRB panel must accept or modify it; then it can be appealed to a federal circuit court, which has final say.
• Several commenters expect challenges, especially given the Supreme Court’s hostility to broad administrative power and Chevron deference.

Economics and fairness of non-competes

• Widespread sentiment: unpaid or broad non-competes, especially for junior or hourly workers, are unfair and anti–free market.
• Some argue they create a labor monopsony, suppress wages, and resemble historical “enclosures” that convert open opportunities into rent-extraction.
• Support for requiring pay (e.g., garden leave) and strict limits on duration and scope; some propose making enforcement extremely expensive to employers.
• Others note that overbroad non-competes are already often unenforceable, though practice varies by state and industry and creates chilling effects.

Industry practices and garden leave

• Finance: garden leave (paid non-work period) is common; seen as tolerable at 3–6 months, but 12–18 months becomes highly punitive despite pay.
• Private equity in medical and veterinary practices reportedly uses non-competes to lock in staff and raise prices; even some conservative states are moving to curb this.

Non-solicitation and references

• Non-solicitation clauses can be extremely long (e.g., 5 years), raising fairness concerns.
• Some companies bar managers from giving any references to avoid defamation suits; critics see this as another mobility- and wage-suppressing practice, though others argue it’s a rational legal risk response.

International comparisons

• Commenters contrast the U.S. with Europe:
  • Germany: certain questions (pregnancy, union status) can be legally answered with lies; employers must provide work certificates, but they’ve evolved coded positivity.
  • UK: non-competes often seen as hard to enforce if they prevent earning a living, but there are moves to formalize caps (e.g., 3 months).

Kindness vs. Intelligence

• Many agree you don’t need to choose between being smart and being kind; the issue is ego-driven displays of smartness.
• Several argue that genuinely listening, being solution-oriented, and showing empathy are themselves forms of intelligence (emotional or social).
• Others worry a kindness-first framing can devalue technical competence in environments already skewed toward “HR values” over engineering rigor.

Defining “Kind,” “Nice,” and “Too Kind”

• Repeated theme: kindness ≠ niceness.
  • Kindness includes honesty, boundaries, and sometimes hard feedback.
  • Niceness is seen as conflict-avoidant, enabling poor performance and gossip.
• Examples raised: “tough love” vs. “ruinous empathy,” “clear is kind,” and firing someone respectfully vs. letting them fail slowly.
• Some note that “kindness” is being used vaguely and conflated with generic collaboration skills.

Kindness, Honesty, and Performance

• Strong view that you can be kind while:
  • Calling out bad work, giving blunt feedback, or firing someone.
  • Protecting the team and customers from chronic underperformance.
• Others stress that “not being unkind” is different from actively being kind, and that kindness must not turn into enabling or ambiguity.

Motives: Utilitarian vs. Principled Kindness

• Some endorse kindness because it improves trust, productivity, and career prospects.
• Others press a moral question: Is kindness only a tool, or good in itself?
  • Thread touches on altruism vs. self-interest and deontological ethics.
• A few are openly cynical: advice like this can be used to make employees more exploitable or to “change the rules” for the less smart.

Culture, Power, and Failure Modes

• Reports from “kind” cultures: feedback is suppressed, problems fester, and conflicts surface via blowups and back-channel gossip.
• Other experiences: unkind, aggressive cultures drive attrition, fear, and technical dysfunction.
• Several emphasize balance: be competent, clear, and fair; don’t be a jerk, but don’t be a doormat.

Background Internet Noise and Attack Patterns

• Many report that any exposed service (SSH, HTTP, SMTP) is probed within minutes; logs quickly fill with thousands of attempts.
• Common HTTP noise: WordPress /wp-login.php and plugin exploits, old Apache/Nginx CGI paths, generic scrapers, and referrer spam.
• SMTP servers see near-constant brute-force login attempts and relay abuse attempts.
• SSH sees large-scale credential stuffing against root and common usernames, often from Chinese, Russian, and hosting-provider IP ranges, coordinated via botnets.

How Dangerous is Exposing Ports?

• One camp: exposing 80/443 is “normal”; main risk is the web apps, not the web server, especially when serving static content with up‑to‑date nginx/Caddy.
• Another camp is wary of any direct exposure, preferring VPNs, reverse tunnels (Cloudflare), or mesh VPNs (WireGuard/Tailscale), treating “no public port” as the safest default.
• Some argue it’s fine to self-host if you patch diligently, understand your stack, and accept residual zero‑day and DoS risk.

SSH Hardening Practices and Debates

• Widely recommended: disable password auth, use key-only logins, keep OpenSSH updated, and often move SSH off port 22 or behind VPN/port knocking.
• Fail2ban and similar tools are polarizing:
  • Pro: reduces log noise and CPU use; blocks obvious brute forcers; helpful for juniors.
  • Con: offers little real security against modern, distributed attacks; can be DoS’d or misconfigured; seen by some as “security theater.”
• Strong random passwords are considered technically safe, but less practical and more error‑prone than keys; bots tend to stop probing servers that refuse password auth.

Blocking and Filtering Strategies

• Techniques include: IP blocklists, ASN- and country-level blocks, tarpits (e.g., endless SSH banners), and dedicated honeypots.
• Supporters say broad geoblocking and blocking “internet scanners” significantly reduce unwanted traffic and protect limited resources.
• Critics note collateral damage: CGNAT and VPNs mean you may block entire ISPs or countries, harming legitimate users and travel use cases.

Security Philosophy and Self‑Hosting

• Ongoing argument: “no truly secure software” vs. “defense in depth can make systems robust enough.”
• Some view widespread breaches as proof most software is insecure and emphasize isolation, monitoring, and not over-trusting any single layer.
• Others warn against excessive paranoia, arguing that basic hardening and auto‑updates are sufficient for small personal/home servers.

Definitions and Conceptual Confusion

• Many commenters argue “consciousness” is ill‑defined; people mix up consciousness, self‑awareness, sentience, intelligence, free will, and moral agency.
• Several say we can’t rigorously test consciousness even in other humans (p‑zombie problem, blackout drunkenness, anesthesia), so animals are even harder.
• Some propose spectrums or multidimensional models (awareness, metacognition, theory of mind, language, spatial sense) rather than a binary yes/no.

Evidence and Arguments That Animals Are Conscious

• Strong experiential arguments from pet owners: dogs and cats clearly show emotions, dreams, play, planning, jealousy, mourning, trust, and individual personalities.
• Empirical examples discussed:
  • Dogs and rats dreaming and replaying maze runs.
  • Bees counting, using tools, playing with balls, social learning via mimicry.
  • Whales, dolphins, corvids, octopuses, elephants showing complex communication, culture, tool use, or social behavior.
• Many invoke evolutionary continuity and similar nervous systems: the “default” should be that mammals (and likely many others) have subjective experience.

Skepticism and Methodological Issues

• Some caution against inferring consciousness from behavior; complex stimulus–response mechanisms might suffice.
• Others argue current evidence is suggestive but not decisive until there is a worked‑out scientific theory of consciousness.
• Debate over how far down consciousness might go: insects, worms, single‑celled life, plants, rocks, LLMs—views range from strict anti‑panpsychism to full panpsychism.

Moral and Societal Implications

• Large focus on factory farming and animal experimentation: if animals are conscious, current practices become morally troubling.
• Some extend compassion (or legal protection) based on sentience indicators; others maintain that killing animals, even if conscious, can be morally acceptable under certain frameworks.
• A few fear that expanding “consciousness” status to animals and machines could instead downgrade how we treat humans.

Religion, History, and AI Comparisons

• Historical references to Descartes, behaviorism, and changing views on infant and animal pain; claims that earlier denials were partly religious or convenience‑driven.
• Some religious traditions are cited as long having treated animals as conscious or ensouled.
• Several draw analogies to LLMs: language alone is not sufficient evidence of consciousness, but it also shouldn’t be the sole criterion to deny it in animals.

Use Case & Hardware Design

• Designed primarily for an underwater robot; priorities are low cost, very small footprint, and integration into existing 12 V / 3.3 V systems.
• 5‑port, 10/100 Mbps unmanaged switch using Molex Picoblade connectors instead of RJ45 to minimize size; cable is spliced from standard Ethernet.
• Magnetics are implemented on the board (“external to the chip, integrated on PCB”), allowing very compact “ports.”
• Layout and schematics are open source; boards designed in KiCad (nightly) and viewable via kicanvas.

Performance & Feature Set

• 100 Mbps Fast Ethernet was chosen because the robot’s tether bandwidth is the bottleneck and higher speeds would add cost, pins, and board area.
• 100 Mbps is defended as still common and appropriate in embedded and industrial contexts.
• The switch IC supports VLANs, QoS, LACP, mirroring, etc., but these require an EEPROM that was removed in V2 to save cost and space; V1 supported them.
• Line‑rate switching is believed but not rigorously characterized; throughput tested at 100 Mbps with iperf.
• Auto‑MDIX behavior is unclear; team hasn’t fully characterized it.

Cost, Size & Market Positioning

• Claimed BOM is around $4–5; small production run cost about $7 per assembled board. Others argue BOM “in reality” is whatever you pay at your volume.
• Commodity 10/100 and even gigabit desktop switches with cases and PSUs can be had for $7–10, so cost leadership is disputed.
• Size leadership is refined: positioned as “world’s smallest 5‑port unmanaged switch,” noting smaller 3‑port commercial modules exist.
• Several comments stress that desktop switches are not suitable for robotics or tightly constrained embedded spaces; this board targets that niche and the open‑hardware community.

Power & Thermal Considerations

• On‑board LDO stepping down from up to 12 V to 3.3 V runs hot (~60°C) at load; heatsinking and thermal vias are used, and an upstream buck is recommended in practice.
• Some suggest moving to a buck converter or shared 5 V rail for efficiency, while others note LDOs’ simplicity and low noise.

Open Source, Tools & Learning

• Full design files are published; team emphasizes democratizing hardware and showing that advanced boards can be built without formal degrees.
• Discussion branches into PCB tools, simulation/DFM (e.g., Quilter), and general learning resources.
• Multiple commenters praise the educational value, expressed interest in buying boards, and suggest selling via hobbyist platforms.

Support for Age Limits

• Many see gerontocracy as dangerous; argue leaders in their 70s–80s are often out of touch with current realities and tech.
• Some want far lower caps (60–70), equating eligibility for retirement benefits with loss of generational relevance.
• Age caps are compared to mandatory retirement for high‑stakes professions (e.g., pilots) where health decline can quickly become a risk.
• Supporters say incumbency and re‑election advantages keep very old politicians in office despite declining health or relevance.

Opposition & Concerns About Ageism

• Critics call explicit age caps “arbitrary” and “ageist,” arguing individuals age at different rates and some remain highly capable into their 80s and beyond.
• They note existing age minimums are tied to expected experience; maximums don’t map cleanly to competence.
• Emphasize that voters, not laws, should remove unfit officials; better tools for evaluating performance are preferred.

Term Limits, Incumbency & Lobbying

• Some argue term limits attack the real problem (career politicians and incumbency) better than age caps.
• Others counter that term limits can empower lobbyists and special interests, since rotating legislators become short‑timers reliant on long‑tenured lobbyists for expertise and post‑office jobs.
• There is disagreement whether long experience in office mainly benefits governance or entrenches corruption.

Constitutionality & Legal Constraints

• Several note Supreme Court precedent that states cannot add qualifications for federal office beyond the U.S. Constitution; many expect the ND law to be struck down.
• A few argue Congress or a constitutional amendment could impose an upper age nationally; state‑level attempts are seen as legally weak but potentially a “test case.”
• Some suggest precedent could be overturned, but this is speculative within the thread.

Generational Relevance & Culture

• Strong theme: very old leaders don’t “live in the same world” as younger generations, lacking lived experience with digital life, identity issues, modern work, and economic pressures.
• Some say society should respect elders’ wisdom but resist being “ruled” by them; power should rotate as generations change.

Voting Age & Political Maturity

• A side debate argues for raising the voting age (closer to 30) due to brain maturation and life experience.
• Others defend lower ages on liberty grounds and cite past conflicts where people could be drafted but not vote.
• Mixed views on whether changing the voting age would materially affect participation or outcomes.

Broader Systemic Critiques

• Multiple comments blame party gatekeeping, money, gerrymandering, and a two‑party duopoly for giving voters unappealing, elderly choices.
• Some see demand for age caps and term limits as a symptom of deeper structural failures rather than a true fix.

Shift in Big Tech’s stance & power dynamics

• Many compare this to the SOPA/PIPA era “internet blackout,” noting that big tech once loudly opposed DNS tampering but now quietly complies.
• Several argue the earlier protests were about maintaining control, not principle; now that tech firms are entrenched in the establishment, they’re more willing to cooperate.
• Others say companies have become legally and reputationally vulnerable (privacy, antitrust, tax), so they “play nice” to avoid harsher regulation.

Legal authority, sovereignty, and corporate compliance

• One camp: if you operate in a country, you must obey its laws or leave; France is exercising legitimate sovereignty.
• Another camp: unjust laws should be resisted, even by corporations, via civil disobedience or exiting the market.
• There’s concern about a precedent enabling broader censorship and about courts using easy piracy cases to normalize tools later used against dissent.

Effectiveness and circumvention of DNS blocking

• Many think DNS poisoning will be trivially bypassed: VPNs, alternative DNS, hosts files, direct IPs, social media/word-of-mouth for new domains.
• Others note that casual users may not circumvent easily, so blocking could still reduce piracy.
• Examples from Italy and other regimes show escalation to IP blocking and fast, automated takedowns, suggesting a “whack‑a‑mole” arms race.

Centralization, censorship, and alternative infrastructure

• Heavy reliance on a few public DNS providers (Google, Cloudflare, Cisco, etc.) is seen as a structural risk; compliance by a small set enables wide censorship.
• Suggestions include running self-hosted recursive resolvers (often with DNSSEC), using smaller/foreign resolvers, or creating decentralized/alternative naming systems (GNS, ENS, DHT-based, blockchain-style).
• Skeptics argue all infrastructure ultimately sits in some jurisdiction and can be pressured or blocked at IP level.

Technical implementation details

• Discussion of Anycast, geolocation-based blocking, and DoH/DoT as partial protections.
• Google is reported to return a REFUSED response with an Extended DNS Error code “censored” plus a link to Lumen, which some praise as technically correct but note most users won’t see.

Debate over piracy and copyright

• Some see sports-streaming piracy as organized theft that should be stopped.
• Others argue piracy often doesn’t displace real sales, can act as marketing, and that harsh enforcement mainly protects entrenched profit models and subscription “moats.”