Hacker News, Distilled

Apple IP and “look-alike” concerns

• Several commenters note the direct use of Apple’s logo and stock icons (Finder, Launchpad, Safari, etc.) and see clear trademark/copyright risk.
• Others argue the practical risk is low (tiny user base, non-competing product), but acknowledge Apple has historically issued takedowns for unauthorized use of its assets.
• Dock magnification patents are mentioned; some say those patents have now expired and that the theme’s author doesn’t seem overly concerned with IP anyway.

Technical limits and jank of GTK/GNOME theming

• Many report long-standing “jank” at theme boundaries: some apps respect the theme, others ignore it or render incorrectly.
• libadwaita and GNOME are described as explicitly hostile to deep theming; “fix” often means brittle hacks, and every major GNOME release risks breaking themes.
• Issues include inconsistent padding, fonts, colors, and window controls, plus apps that ship their own styling.
• Extensions and themes have short lifetimes because GNOME’s APIs aren’t stable; authors must constantly chase churn.
• Using mixed toolkits (GTK/Qt) or old apps (e.g., GParted under KDE) often produces mismatched UI.

Appearance vs behavior: macOS vs Linux

• Multiple users stress that mimicking macOS visuals doesn’t reproduce what they actually value:
  • Consistent keyboard shortcuts and menu semantics.
  • A global menu bar as the exhaustive surface for app functionality.
  • Bundle-based app/plugin/library model and disk images (sparsebundles, Time Machine style).
• Some note GNOME lacks a robust global menubar and historically even hid minimize; extensions exist but feel hacky.
• Result: themes can look like macOS, but interaction paradigms remain fundamentally different.

User preferences: defaults, other DEs, and “not caring”

• Several prefer stock themes (Adwaita, Ubuntu Yaru, Mint, Breeze) because they “just work” and stay maintained.
• Others enjoy long-lived niche themes (Chicago95, Orchis), or give up theming entirely in favor of tiling WMs (i3) where most of the screen is app content.
• Opinions diverge on aesthetics: some find GNOME already “mac-like and polished”; others think Windows UI is “objectively atrocious,” while some say it’s just taste.

The broader theming debate

• The GNOME “stopthemingmy.app” stance is referenced repeatedly: devs object mainly to distro-wide theming that breaks apps and generates false bug reports.
• Some see this as reasonable; others argue it conflicts with the spirit of user control and customization on free desktops.

Physical vs digital controls in everyday objects

• Many argue basic actions (lights, doors, gloveboxes, car controls) should default to simple, physical interfaces; phones and touchscreens add latency and failure modes.
• Others counter that digital control is useful as an addition (e.g., turning off lights from bed, “good night” automations, managing many lights) but agree it should not fully replace switches.
• Tesla’s “no buttons” philosophy and phone-only locks/entries are cited as emblematic of ideological over-design.

Smartphones, voice assistants, and “rational” UX

• Disagreement over what’s easier: some find phone apps slow and fiddly compared to buttons or voice; others say system-level widgets and face unlock make phone control very fast.
• Voice assistants are praised for hands-free scenarios but criticized for unreliability, especially with children’s speech.
• Consensus: technology is fine when it adds options; it’s frustrating when it removes robust, low-tech fallbacks.

App‑only ecosystems and erosion of choice

• Strong pushback against environments that require smartphones: app-only parking, QR-only menus, app-based building access, phone-only 2FA, gym entry via rotating QR.
• Some describe real situations where lack of a compatible smartphone effectively excludes people or wastes significant time.
• The thread supports the article’s call for preserving analogue alternatives so choice is meaningful, not a “Hobson’s choice.”

Deliberate minimalism and personal rules

• Several posters describe strict boundaries: no notifications, DND 24/7, phone stored away after work, refusing QR-only restaurants or app-only apartments.
• Amish practices and “digital minimalism” are referenced as models for community or personal gatekeeping of tech.

Bad design, over-engineering, and profit incentives

• Examples of “solutionism”: Bluetooth water bottles needing power and apps, restaurant QR menus that worsen social interaction, clumsy institutional systems that waste time.
• Many feel tech is optimized for monetization rather than human life, leaving lots of low-value but high-friction annoyances unfixed.
• High-level theme: tech should augment, not replace; hardware for reliability, software for flexibility.

Addiction, regulation, and responsibility

• Debate over whether doomscrolling is mainly about environment, availability, or individual choices.
• Some call for stronger regulation of social networks and “garbage information”; others argue anonymity isn’t the core problem.
• General agreement that smartphones are powerful, partly addictive tools that must be consciously managed rather than naively embraced or fully rejected.

State of European Cloud Alternatives

• Many argue Europe “had 20 years” to build its own clouds and office suites and mostly failed; US hyperscalers are seen as years ahead.
• OVH, Hetzner, Scaleway and others are cited as EU options, but often described as:
  • Good for cheap VMs or bare metal, not as full-service clouds.
  • Missing mature managed services (databases, queues, identity, rich networking).
  • Weaker on reliability, support, and long feature roadmaps.
• Attempts at EU-hosted productivity (Nextcloud + OnlyOffice/Collabora, etc.) are said to exist but UX and integration are widely viewed as inferior to Google Workspace / O365.
• Some point out Europe does have strong tech firms (cloud infra vendors, fintech, SaaS), but not consumer megacorps or hyperscale cloud equivalents.

Data Sovereignty, CLOUD Act, and “Sovereign Clouds”

• Repeated emphasis that data residency ≠ data sovereignty:
  • The US CLOUD Act lets US authorities compel access to data held by US companies, even if stored in the EU.
  • Commenters claim any US provider promising “data sovereignty” is effectively misleading unless it’s genuinely out of US control.
• EU privacy law (GDPR, Schrems rulings) already made US cloud usage shaky for personal data; recent US moves (e.g. neutering oversight bodies) are seen as breaking the latest legal fig leaf.
• “Sovereign cloud” models (e.g. Azure/Google tech operated by EU companies) are debated:
  • Pro: operational control and keys in EU hands, US company only supplies software.
  • Con: still dependent on US updates and legal leverage; Cloud Act risk remains.

Cloud Security and Government Secrets

• Strong minority view: it was never safe for any government to put secrets in any public cloud, regardless of country.
• Others frame it as a spectrum:
  • With strong client-side encryption, HSMs, confidential compute, and gov-only regions (GovCloud, Secret Cloud), cloud can be acceptable for some classified or sensitive workloads.
  • Real risk is not just espionage but ability to coerce providers to shut down or degrade critical services.

Trump, Geopolitics, and Trust in the US

• For many European commenters, the change is qualitative: the US is now perceived as an openly unreliable or even adversarial partner (Ukraine policy, trade threats, rhetoric about annexations).
• They see a realistic scenario where a US administration orders US clouds to cut off or pressure EU states, making cloud a geopolitical weapon.
• Others argue this risk long predates Trump (Snowden, PRISM), and focusing on one president is partisan framing; US surveillance and legal overreach are structural.
• Counterpoint: Europe itself is criticized for speech restrictions, encryption-hostile laws, and surveillance ambitions; no government is truly trustworthy with centralized data.

Feasibility of European Tech and Cloud Independence

• Many doubt Europe can quickly build AWS/Azure-class platforms:
  • Capital is fragmented and risk-averse; management in telco/hosting often described as technically weak and slow.
  • Brain drain to US tech firms is seen as a core structural problem.
• Others argue this is exactly like the Airbus story: painful, expensive, but strategically necessary, and now politically sellable.
• There’s debate on strategy:
  • Full EU hyperscaler(s) with heavy public funding vs.
  • On-prem and colocation with open-source stacks (OpenStack, k8s, self-hosted DBs) vs.
  • Hybrid “local operator + US software” as an interim step.

Beyond Cloud: Deeper Stack Dependence

• Several note that even if infra moves to EU clouds, the edge is still US-controlled:
  • Smartphones (iOS/Android), app stores, browsers, identity providers, and SaaS (O365, Google, GitHub) remain dominated by US firms.
• Some foresee:
  • More self-hosting, Linux desktops, and EU-focused SaaS for government/critical sectors.
  • Legal measures (tariffs, bans, procurement rules) pushing public-sector workloads off US platforms, despite cost and migration pain.

“No Longer Safe” vs “Never Safe”

• Many object to the title: they argue it has never been safe or wise for sovereign states to base critical infrastructure on foreign-controlled clouds; recent US politics only exposed an existing strategic error.
• Others say that while the theoretical risk was always known, its probability and immediacy have changed enough that the cost–benefit calculation for EU governments and enterprises must now flip in favor of local or self-controlled infrastructure.

Adaptation to Smartphones After Long Incarceration

• Several commenters with direct experience say people released after decades adapt to smartphones quickly, especially since many prisons now have tablets for media and messaging.
• The “surprise” isn’t that phones exist, but how pervasively and compulsively they’re used in public life.

Ubiquity and “Addiction”

• Many describe public spaces (buses, cafes, parks) as filled with people “zombified” by their phones, including very young children.
• Phone use is compared to drugs, cybernetics, or an “epidemic,” with specific concern about scrolling during driving, parenting, and social gatherings.
• Some report trying phone-free periods and noticing genuine withdrawal-like discomfort when forced to “just wait” or be bored.

Social and Psychological Effects

• Several say they avoid eye contact by staring at phones, continuing older habits (newspapers, books) of shielding from strangers.
• Others argue we’re more connected digitally but more lonely and isolated emotionally.
• There is debate over whether online interaction “counts” as real socializing; some prefer it for control and clarity, others say this means they haven’t found the right in-person relationships.

Continuity with the Past

• Commenters point out that pre-smartphone commuters also avoided each other, usually with newspapers or books; smartphones are seen as a more powerful continuation, not a total break.
• Nostalgic stories about school buses, books, PDAs, and early mobile tech contrast with today’s constant video feeds and social media.

Coping Strategies and Resistance

• Suggestions include phone boxes at gatherings, removing infinite-scroll apps, turning off notifications, using phones mainly as creative tools, and attending gadget-free retreats.
• Some anticipate a future “anti-phone” or “offline” subculture as a social signal.

Dependence and Infrastructure

• Concerns are raised about needing modern phones for payments, school communications, WhatsApp groups, and basic social inclusion.
• Debates emerge around cashless living, hygiene fears, and how far dependence on corporate platforms has gone.

Overlooked Issue: Wrongful Imprisonment

• A minority note that the truly shocking element is the likely wrongful 30-year incarceration, which the article largely glosses over.

Sticker Price vs. Net Price (and the Missing Loans)

• Many agree sticker prices at U.S. colleges are largely fictitious; only a minority (especially at privates) pay full tuition.
• Commenters cite data that ~16–26% of students pay full price; international students are often described as “funding whales.”
• Multiple people criticize the article for treating all “financial aid” alike and never distinguishing grants from loans.
• Concern: if net price is lower only because of loans, the true cost hasn’t fallen—debt has just been shifted to the future.

Class, Access, and Who Gets Help

• Longstanding pattern: poor/high-achieving students can get large discounts at elite schools, but many self-select out because sticker prices scare them.
• Middle-class families feel especially squeezed: too “rich” for need-based aid, not rich enough to pay, leading to talk of HELOCs, raiding retirement, and regret.
• Some note generous merit packages at lower-ranked flagships (e.g., Alabama, Oklahoma) vs. weak merit aid at “good” state schools.
• There is tension over scholarships restricted by race/gender; some view this as unfair discrimination, others as equity.

Signaling, Status, and School Choice

• Where a child goes to college is framed as a status symbol and “team” identity for parents (bumper stickers, apparel, bragging rights).
• Debate over payoff of prestige:
  • Top-5 schools seen by some as worth very high costs for networks, elite recruiting, and social capital—if students actively leverage opportunities.
  • Others argue public flagships or even community-college–to–state-university paths yield similar outcomes for most careers.
• Small private liberal-arts colleges are repeatedly labeled as bad value and financially risky (closure risk).

Value of College vs. Alternatives

• One camp argues many bachelor’s degrees are rent-seeking credentials; self-taught software engineers and tradespeople often do as well or better.
• Another camp defends college for critical thinking, exposure to diverse ideas/people, and rigorous training in math-intensive fields.
• Several note that U.S. options like community colleges, in-state public universities, and flexible timelines can make higher ed relatively affordable—if you avoid high-debt private paths.

Policy, Incentives, and Skepticism of the Article

• Some suggest shifting loan liability to universities to force cost discipline.
• Others blame federal aid and guaranteed loans for enabling price inflation.
• The article itself is widely viewed as PR-like, cherry-picking post-2014 data, downplaying 40–50 year cost rises, and ignoring student-debt realities.

Core technical explanation

• QR has multiple modes: numeric, alphanumeric, byte, kanji.
• Alphanumeric mode supports digits, space and a 45‑character uppercase-heavy set, encoding 2 chars in 11 bits (~5.5 bits/char).
• Lowercase letters are not in this set, so any lowercase forces byte mode (8 bits/char), producing larger codes.
• QR messages can be split into segments with different modes, but many generators don’t optimize this.

Alternative encodings & efficiency debates

• Data Matrix and some 1D codes (e.g., Code 128) can shift modes inline; QR instead uses explicit segments.
• Some suggest using general compression (Huffman/entropy coding) instead of fixed modes, but others point out you then need shared probability tables, which becomes equivalent to predefined modes.
• Base45 (RFC 9285) is discussed for packing binary data into QR alphanumeric; it has small overhead vs pure byte mode and avoids big‑integer math.
• Others argue numeric or carefully chosen alphabets (via “base‑x”) can be more efficient or simpler.
• There’s a detailed back-and-forth about how to measure “efficiency” (fraction of bit space used vs information-theoretic bits per symbol) and whether base45 or QR alphanumeric is more efficient under realistic constraints.

Tools and visual explainers

• Several links to step‑by‑step and visual QR explainers are shared, with praise for ones that let you input your own data and see every encoding step.
• A video of manually constructing a QR code on a Go board is mentioned as a nice illustration.

Uppercase URLs & compatibility

• Question: is it safe to uppercase the URL scheme (“HTTPS”)?
• Various people report practical success on major phones, but some iOS quirks when omitting the scheme and using non‑.com TLDs.
• Common strategy: keep https:// lowercase, uppercase the domain (and sometimes path), and rely on mode segmentation for size benefits.
• Standards say schemes are case-insensitive but canonically lowercase; real-world scanners generally accept uppercase.

QR bloat, tracking, and usability

• Many real-world QR codes are far larger than necessary because they embed long tracking URLs and query strings; this makes them harder to scan but easier to implement and track.
• Some argue a short domain + simple identifier (possibly uppercase-only) should suffice, with redirects handling complexity behind the scenes.

Human vs machine-readable concerns

• Several commenters dislike the post‑pandemic trend of QR‑only menus and ordering: dependence on phones, poor accessibility, fragile scanning, and hidden tracking.
• Preference for also printing short, human-readable URLs or recognizable names, akin to text under 1D barcodes.
• Discussion of using pixel fonts or OCR‑friendly fonts (OCR‑A/OCR‑B), but others note modern OCR and that barcodes still win for robustness and structured data.

Historical/contextual note

• One commenter notes QR was invented in Japan, where Latin letters—when used—are typically uppercase only, so an uppercase+numeric “alphanumeric mode” aligns with local conventions and helps explain the design choice.

Technology maturity and timelines

• Commenters stress BYD is only at pilot production; low-volume “mass demonstration” is targeted around 2027, with truly large-scale rollout likely after 2030.
• Other players (CATL, Honda, Hyundai, various startups) appear at similar pilot or demo-plant stages; CATL reportedly rates process maturity 4/9.
• Prototypes work, but no one has a proven, low-cost, high-volume manufacturing process yet. Building giga-scale plants will take years and large capital.
• Several people are skeptical of repeated solid‑state announcements, especially from some legacy automakers, and say they’ll only believe claims when cars ship.

Economics, use cases, and current chemistries

• Discussion emphasizes that today’s market rewards low cost per kWh, not maximum energy density; this explains the dominance and expected longevity of LFP cells.
• Early solid‑state packs are expected to be expensive and scarce, so likely first used in high-value niches: aviation, flying taxis, motorcycles, and premium/sports cars.
• Semi‑solid batteries already offer sizeable capacity gains; commenters speculate all‑solid‑state could go further but acknowledge cost is the hard part.

Benefits, risks, and materials

• The main promised advantages: higher energy density, faster charging, and improved safety from replacing flammable liquid electrolytes with solids.
• Others note that any large battery can still release massive energy in a short circuit, so “no flames” is unrealistic.
• There’s curiosity about required metals; one reply points to standard solid‑state material families without a clear consensus on scarcity.

EV range, charging, and user expectations

• Large subthread debates whether better batteries or better charging networks matter more.
• One camp: current ~300 km real-world EVs plus dense, reliable fast-charging is sufficient; extra range mostly adds weight and cost.
• Other camp: real-world constraints (10–80% fast-charge window, winter losses, high-speed driving) mean practical ranges are much lower; many buyers want ~500+ miles equivalent and 350 kW+ charging for ICE-like road-trip ease.
• Range anxiety, multipurpose expectations, and dislike of renting second cars are cited as key adoption barriers.

Energy systems, alternatives, and broader context

• Some see fuel cells (especially liquid fuels like methanol) and redox flow batteries as complementary, but others view hydrogen/fuel-cell pushes as a way to preserve fossil and maintenance-heavy industries.
• Grid-scale batteries are seen as less sensitive to energy density but big drivers of cheaper, more flexible electricity; there’s skepticism whether savings would reach consumers.
• Several argue that breakthroughs in batteries and energy management will have more enduring real-world impact than current AI hype, which some expect to cool.

China’s role and product perceptions

• Multiple comments note China’s strong patenting, academic research, and policy push around batteries and EVs, helped by its lack of a powerful domestic oil lobby.
• Opinions on BYD and other Chinese EVs are mixed: some praise value and quality; others distrust Chinese batteries due to reported fires, while critics respond that non-Chinese EVs also catch fire.

Sign conventions, holes, and historical artifacts

• Several comments focus on the oddity that “current” is defined as positive charge flowing, opposite to electron motion, and that semiconductor theory talks about “holes” moving.
• This is traced to an arbitrary pre-electron sign choice in early experiments; by the time electrons were understood, engineering practice was too entrenched to flip.
• Some argue this convention causes genuine confusion in education and wastes collective time; others insist it’s a trivial, learn-once quirk with negligible practical impact.

Static electricity and triboelectric confusion

• Discussion of Franklin’s rubbing-glass experiments leads into the triboelectric series: which material becomes positive or negative depends subtly on the contact pair and even history.
• Commenters note that triboelectric charging is still not fully understood; experimental orderings can be inconsistent and even cyclic (A> B, B> C, C> A), which challenges simple linear models.

Where energy and “electricity” actually flow

• A recurring theme is whether it’s better to think in terms of electrons in wires or electromagnetic fields in space.
• Some emphasize that energy flow is described by fields (and the Poynting vector) mostly outside conductors, with resistance representing energy entering the material; this connects to high‑frequency behavior, impedance, and transmission lines.
• Others push back that “energy outside the wire” is a misleading teaching model for most practical DC and low‑frequency work, where thinking of current in conductors remains effective.

Speeds: propagation vs drift and thermal motion

• The article’s point that fields propagate near light speed while electrons drift extremely slowly is elaborated: electrons already move very fast thermally in random directions; the field only adds a small net “bias.”
• Commenters distinguish drift velocity, thermal (Fermi) motion, and the speed of electromagnetic disturbances through different media, noting that signals in copper or dielectrics travel at some fraction of the vacuum speed of light.

Quantum nature of electrons and charge

• Several comments dig into electrons as excitations of quantum fields rather than little orbiting balls; “orbitals” are probability distributions constrained by symmetry, not miniature planetary systems.
• There is debate over how much of this should be taught early: some want group theory and orbital symmetry presented up front; others say the needed math is too advanced.
• Broader questions arise: what is charge, momentum, or “positive charge” at all? The consensus is that these are deeply tied to symmetries and conservation laws, and that intuition built from everyday experience fails at this scale.

Teaching, analogies, and “lies to children”

• Many note that every educational level introduces useful but wrong models, later refined (“lies to children”).
• Water‑flow analogies, Bohr’s atom, and electron‑as-billiard‑ball are criticized for becoming sticky misconceptions, yet defended as productive scaffolding when clearly labeled as approximations.
• There’s disagreement over whether we over‑prioritize “intuitive” stories instead of teaching the hard, abstract truth, especially at university level.

Superconductivity, resistance, and materials

• A side thread explains superconductivity qualitatively: lattice vibrations (phonons) mediate Cooper pairs that condense into a collective quantum state, eliminating resistance below a critical temperature.
• Others add that ordinary resistance reflects electrons scattering off a vibrating lattice; reduced lattice motion at low temperature lowers resistivity even without superconductivity.

Philosophical limits and models of reality

• Multiple commenters reflect that as you dig deeper into electricity, explanations become less intuitive and more purely mathematical, leading to a sense that “nothing underpins reality” beyond equations.
• This is linked to the idea that all our concepts are internal models tuned for survival, not faithful mirrors of the underlying physics; all models are incomplete, though some are extremely useful.
• Jokes, quotes, and anecdotes underline a shared feeling: we can predict electrical phenomena very well, but what electricity “really is” remains philosophically elusive.

Half-Life vs. Black Mesa (Which to Play Now)

• Many recommend Black Mesa as the easiest modern entry: better visuals, reworked encounters, strong soundtrack and sound design, revamped boss fights, especially Gonarch.
• Others insist it does not replace Half-Life:
  • HL1 is faster, more “run-and-gun” and Quake-like; Black Mesa feels slower and more tactical.
  • AI behavior differs; Black Mesa’s soldiers are more aggressive, further slowing pacing.
  • Numerous level changes are divisive: some feel they add polish, others say they’re “different for the sake of different.”
• Xen is a major flashpoint:
  • Some loved original Xen’s empty, oppressive alien feel and find Black Mesa’s version pretty but less atmospheric.
  • Others think Black Mesa’s Xen is far superior mechanically but too long and padded.
• Consensus: both are good but distinct; HL1 is still fully playable and worth experiencing on its own terms.

Movement, Jumping, and Engine Feel

• Some readers strongly reject the article’s implication of “sloppy” movement, citing extremely tight, reproducible physics exploited in speedruns, bunnyhopping, surf, and KZ maps.
• Others note that while controls are responsive, platforming can be frustrating due to cramped geometry and unclear jump targets (especially in Xen).
• Discussion of quirks: non-physical acceleration tricks, FPS-dependent behavior, and early driver/renderer issues affecting latency.

Pacing, Linearity, and Genre Blend

• A subset never clicked with Half-Life, preferring Doom’s pure action and looser, more “honest” level goals.
• Others praise Half-Life’s deliberate alternation of combat and puzzle segments as its core design insight, making both more satisfying.
• Some dislike the strong “authored path” compared to the exploratory freedom of older shooters, while others feel the linearity is justified by the strong story and memorable AI encounters.

Modding, Community, and Legacy

• Huge nostalgia for the Half-Life mod era: Counter-Strike, Team Fortress Classic, Day of Defeat, Natural Selection, Science & Industry, Action HL, The Specialists, “rats” maps, surf/kz, etc.
• Built-in tools like Worldcraft made modding approachable, spawning clans, servers, and careers in software and game development.
• Several lament modern multiplayer games’ locked-down architectures and monetization (anti-cheat, cosmetics, DLC) as hostile to that kind of grassroots creativity, though note thriving mod scenes still exist in some genres.

Industry & Historical Impact

• Commenters emphasize Half-Life’s role in:
  • Proving story-driven FPS could succeed commercially.
  • Popularizing heavy scripting, AI companions, and more cinematic single-player design that later influenced Halo and Call of Duty.
  • Showing that supporting mods and fan projects (e.g., Counter-Strike, later Black Mesa) can pay off creatively and commercially.

Scope and Definition of “School Shooting”

• Database uses a very broad definition: any gun brandished, fired, or bullet hitting school property, regardless of time, motive, or whether students are involved.
• Includes: late-night parking-lot disputes, homeless people shooting each other on campus, off-site shootouts where a stray bullet lands on school grounds, accidental discharges, and police drawing/firing guns.
• Some argue this is appropriate: it captures all scenarios where students or staff could be harmed and can be filtered later into subcategories.
• Others say it conflicts with common usage, where “school shooting” implies an on-campus, school-hours, multi-victim attack targeting students/staff (a “Columbine-like” event).

Classification vs. Emotional Framing

• One side sees attempts to exclude parking-lot/gang/homeless incidents as minimizing gun violence or “arguing away” the problem.
• The other side sees the broad definition as rhetorically manipulative—leveraging the emotive power of “school shooting” to inflate numbers and push gun-control narratives.
• Several suggest clearer terminology, e.g., reserving “school massacre” for multi-victim targeted attacks while still tracking all gun incidents on school property.

Trends and Possible Causes

• Commenters note a sharp rise in incidents from ~2018 and especially post‑2020; 2021–2024 reportedly exceed all prior years combined.
• Hypotheses (no consensus): return from COVID school closures, social isolation, worsening teen mental health, economic stress, social media and online radicalization, and a copycat/contagion effect amplified by media coverage and online “mass-shooting fan” communities.
• Some speculate about changing reporting standards or definitions; others attribute it to broader increases in gun violence.

Risk, Comparisons, and Perception

• Some argue broad inclusion doesn’t change the big picture: the US remains an extreme outlier in gun violence around schools, however defined.
• Others emphasize that mass-fatality events are still statistically rare and that public fear may be disproportionate to the individual risk.
• Several note that definitional debates can distract from the “elephant in the room”: pervasive gun availability and violence, especially affecting marginalized communities.

Other Data Points and Reactions

• 2% of shooters being school police is seen as unsurprising given who routinely carries guns on campus; many of these incidents may be accidental.
• Roughly 40% of perpetrators escaping is explained as typical for brief, dispute-driven shootings (e.g., after games, in parking lots) where no one talks.
• Some are more shocked by homelessness and armed conflict on campus than by the classification issue, tying it to housing costs and weak social safety nets.

What IQ Measures (and Doesn’t)

• Repeated emphasis that IQ is at best a rough proxy for certain cognitive skills, especially around the average range.
• Many argue “intelligence” is multidimensional (verbal, numerical, spatial, memory, metacognition, executive function, etc.), so forcing it into a single scalar (IQ) is misleading.
• Several posters stress that high IQ ≠ genius, accomplishment, or even competence; it mainly reflects how well you do on IQ‑like tasks.

Scale, Linearity, and Distribution

• Debate over “linearity”: some note IQ is ordinal, not a linear or ratio scale (100 isn’t “twice” 50), and shouldn’t be treated like height.
• Others counter that you can still rank people on a line of IQ scores, and both IQ and height are roughly normally distributed.
• Disagreement about “by definition IQ is normal”: some say test norms enforce an approximate normal distribution; others point out real tests are calibrated episodically and can deviate, especially at the tails.
• Consensus that measurements become unreliable above ~120 and at very low scores due to sparse calibration data. Claims of 160+ or 170+ are widely treated as noise or outright bogus.

Practice vs. Innate Ability

• Many anecdotes about specific cognitive talents (visualizing equations, perfect pitch, remembering names or conversations, spatial navigation).
• One camp stresses practice, enjoyment, and training can build impressive abilities; another highlights “hardware” differences (e.g., prosopagnosia vs. super recognizers) that practice can’t fully overcome.
• Discussion that fMRI and brain-structure findings are hard to interpret because training itself reshapes the brain.

Clinical and Practical Uses

• Strong support for IQ batteries as diagnostic tools for learning disabilities, ADHD, and atypical profiles (large subtest gaps).
• Stories of people with mixed strengths/weaknesses whose IQ testing led to useful diagnoses and coping strategies.

Correlation with Life Outcomes

• Some argue IQ strongly tracks education, income, learning speed, and even athletic performance.
• Others respond that socioeconomic context (zip code, parental income) and non-IQ traits (motivation, organization, mental health) often dominate outcomes.

Cultural and Social Critiques

• IQ obsession and boasting are mocked; Mensa is described as a poor filter for wisdom or character.
• Several note Goodhart’s law: once IQ is treated as a status metric, its meaning degrades.

Background and Trigger Events

• Commenters note Thailand’s power cutoff to Myanmar scam hubs began weeks earlier and is part of a broader China–Thailand–Myanmar crackdown.
• A widely discussed incident: a Chinese actor lured by a fake casting call, trafficked into a Myanmar scam center, and rescued after public outcry. This is seen as a key political catalyst for serious action.
• Thailand is also motivated by fears that Chinese social‑media coverage of trafficking via Thailand will deter Chinese tourists.

Who Runs the Scam Hubs, and Who Is Targeted?

• Many describe these as Chinese-run operations in Myanmar (and similar setups in Laos and Cambodia), originally casino complexes that pivoted to online fraud.
• Victims include both Westerners and Asians, but several comments stress that Chinese citizens are primary targets because scammers and coerced workers speak Chinese.
• These hubs are depicted as forced-labor camps/dorms where trafficked workers are abused, confined, and coerced into “pig butchering” and other scams.

Debate on CCP Involvement

• One camp argues the scam complexes are effectively backed or tolerated by elements of the Chinese state, given scale and profits, and their targeting of geopolitical rivals.
• Others counter that:
  • China is cracking down (airlifts, extraditions, militia offensives against scam zones).
  • Chinese citizens are major victims, making state sponsorship illogical.
  • Some hubs are tied instead to historic triad networks and anti‑communist groups.
• Several people emphasize the Chinese state is internally fragmented; “Beijing knew and directed it” is seen as an oversimplification.

Effectiveness of Cutting Power

• Skeptics say grid power cuts are “old news”: operators have shifted to diesel generators, Starlink, and new locations (e.g., Cambodian border).
• Others argue that even if technically bypassed, cutting power, gas, and internet:
  • Signals serious state pressure.
  • Punishes local enablers and raises the cost of hosting scam centers.
• Concern is raised that civilians and trafficked workers also lose basic services (e.g., cooking gas).

Myanmar as Failed State and Regional Proxy

• Multiple comments describe Myanmar as effectively a long‑running failed state with fragmented control, chronic ethnic wars, and extreme junta corruption and superstition.
• There is debate:
  • Some locals say the country briefly improved in the decade before the recent coup and is now in civil war, with people’s defense forces and ethnic armies regaining territory without Western help.
  • Others frame Myanmar as a Southeast Asian “Congo,” where China, India, and Thailand arm and back different factions and warlords in border regions for strategic depth and influence.
• Speculation about future interventions:
  • Some imagine Chinese or Thai military action if things worsen; others insist Thailand will stay strictly on its own side of the border and China will mainly support the junta.
  • There is disagreement over how much external powers “control” versus merely trade with or arm ethnic armed organizations.

Human Cost and Prospects for Victims

• Commenters repeatedly highlight the “hellhole” conditions: kidnapping via fake overseas jobs, confinement, violence, and forced scamming.
• Several hope that victims can escape rather than just be moved to other hubs, and that more resources exist for survivors.

Scam Industry Scale, Crypto, and Tech Angle

• An Economist podcast is cited describing a massive scam industry (hundreds of billions of dollars), with Myanmar hubs as a central node.
• Crypto is portrayed as a key enabler:
  • Use case lists include financing North Korea’s missile program and facilitating large transnational scams.
  • Some note crypto’s irreversibility and pseudonymity as helpful to criminals, though others stress it also leaves on‑chain traces.
• There’s a side debate whether crypto is actually necessary for everyday crime, with several saying domestic drug markets already run on apps like Venmo and conventional web storefronts.
• Some posters tie this to a broader cyberpunk/AI dystopia: AI-enhanced scamming, weak states, and criminal enclaves becoming a core “use case” of modern tech.

Normative Reactions

• Many endorse cutting off utilities and connectivity to scam hubs and, more broadly, “cutting services to internet fraudsters” until host states enforce laws.
• Others warn that without deep political change in Myanmar and coordinated international pressure, scammers will simply relocate, retool, and continue exploiting both victims and local chaos.

Scope and “spirit” of the game

• Many argue that once “any mathematical operation” or arbitrary functions are allowed, the puzzle becomes trivial and loses its spirit.
• Others counter that all operations (+, −, ×, ÷, powers) are functions anyway; the real issue is which functions count as acceptable, not whether “functions” are allowed.
• Several comments emphasize that this is a game, not a formal competition, so rule choices should prioritize fun rather than rigor.

Which operations are allowed?

• Debate over allowing “fancy” functions: gamma, square root, logarithms, floor/ceiling, trig, primorial, etc.
• One camp wants to restrict to integer→integer functions to stay close to the traditional “four fours” puzzle. This excludes sqrt and log but allows +, −, ×, factorial, exponentiation by integers.
• Others are fine with square roots, logs, rounding, etc., especially if they’re “common” or appear on a basic calculator.
• The gamma function and Dirac-style constructions are viewed by several as too obscure or too powerful for a kids’ puzzle.

Hidden constants and notation

• Strong criticism that sqrt hides an implicit 2 (root degree), just as log and ln hide bases like 10 or e. Some see this as using extra twos “for free.”
• Counterpoint: all notation hides structure (e.g., + hides repeated successor; factorial hides a whole product), so this line is inherently arbitrary.
• Some propose forbidding any letters/digits other than “2”; others say letters are just symbols too and the distinction is fuzzy.

Unary operators and trivialization

• Repeated unary operations (successor S(n)=n+1, increment ++, repeated sqrt) can generate all integers, making the puzzle trivial.
• Observation: if you restrict to only a finite set of n‑ary operators (n≥2) and exactly four 2s, the number of expressible values is finite, so you can’t reach all integers; at least one “useful” unary operation seems necessary.

Need for explicit rules

• Several commenters think the article’s initial rules (“any mathematical tools”) are too vague; they’d prefer a fixed, explicit operator set up front.
• Others enjoy that part of the fun is precisely pushing and renegotiating those boundaries.

Related puzzles and curiosities

• References to the classic “four fours” puzzle, Knuth’s “one 4” constructions, and mobile/online games based on similar ideas.
• Some share floating-point based constructions where expressions involving √2 and rounding artifacts yield large integers, highlighting implementation quirks rather than pure math.

Endowments and Why They “Can’t Just Pay”

• Many commenters start from “Penn has a $22B endowment, why not use it?”
• Others explain endowments as restricted, long‑horizon trust funds: principal is legally locked, returns are mostly pre‑earmarked (chairs, scholarships, specific fields), and schools typically spend ~4–5% annually.
• Several note that even endowment income is often too constrained or small (1–2% practically spendable for research), so it can’t simply backfill large, sudden federal cuts.

Grad Students, Stipends, and the PhD Pipeline

• Strong criticism that universities work grad students “to the bone” for poverty stipends while taking large overheads.
• Some argue low stipends can still be attractive for certain students, but others emphasize mental‑health crises, slum‑like living conditions, and exploitative dynamics.
• Debate over whether the US produces “too many PhDs” (especially in some fields) versus the need to maintain a robust, relatively cheap scientific workforce and pharma pipeline.

Indirect Costs (Overhead) and the 15% Cap

• Confusion and argument over what a 59% indirect rate means; multiple comments clarify it is 59% on direct costs (so ~37% of total), and many expenses (equipment, tuition) are exempt.
• Supporters of the cap see 50–90% rates as proof of waste and cross‑subsidy; critics say indirects pay for labs, utilities, compliance, IT, safety, core facilities, and shared staff that enable research.
• Several point out that current rates are painstakingly negotiated with NIH/NSF and governed by regulation; abrupt across‑the‑board cuts are described as likely illegal and highly disruptive.

Administrative Bloat vs. Necessary Staff

• Widely shared data on explosive growth of non‑faculty employees fuels anger that universities cut PhD spots instead of administrators.
• Counterarguments: much “admin” is actually scientific staff, compliance, IRB, immigration, tech transfer, research computing, etc., driven by regulatory and service expansion.
• Some note genuine bloat (multiple IT silos, amenities arms race), but argue blunt overhead cuts will mostly hurt essential support and push more burdens onto faculty and grad students.

Political Motives and Legality

• Many see the NIH indirect cuts and grant slowdowns as a deliberate, shock‑and‑awe move by the current administration to weaken universities and the scientific establishment, not a good‑faith efficiency reform.
• Others welcome a chainsaw approach, arguing that gradual, consultative reform has failed and entrenched institutions will otherwise block change.
• Legal discussion centers on appropriations law, NIH regulations, and court orders temporarily restraining aspects of the policy.

Consequences for Research, Industry, and Equity

• Reports of multiple programs (biochemistry, biostatistics, “bio‑” departments) admitting zero PhD students; individual PIs are freezing hiring to protect current trainees.
• Concerns that US biomedical and biotech leadership will erode, with talent and research shifting to Europe/Asia and private foundations or foreign governments.
• Worries that access to advanced education will skew further toward the rich as funded PhD paths shrink, and that research slowdowns (e.g., in mRNA, Alzheimer’s) carry large long‑term social and economic costs.

Core Idea & Variants

• Thread centers on reframing approvals from “please say yes” to “I plan to do X unless you object by time Y.”
• Related concepts mentioned:
  • “Ask forgiveness, not permission.”
  • “Radiate intent” / UNODIR / “silent procedure” (announce actions, invite objections).
  • “Tell, don’t ask” / “creating sane defaults” rather than forcing decisions.
  • Sales/negotiation patterns (offering constrained choices, “no‑oriented” questions).

Perceived Benefits

• Bias toward action in environments where emails get ignored and approvals stall.
• Reduces decision fatigue for managers; they react only if they see a problem.
• Helps mid/senior ICs show initiative, think through tradeoffs, and sound more senior (“I intend to…” vs “What should I do?”).
• Creates a paper trail showing others were informed and had a chance to object, useful against later blame or foot‑dragging.
• Fits many “two‑way door” decisions (reversible, low–medium impact) and internal changes that otherwise languish.
• Can empower teams and reduce micromanagement when there’s existing trust and competence.

Risks, Failures, and Limits

• Many view the “deadline” framing as confrontational or manipulative—an ultimatum rather than help.
• If something important breaks, “nobody approved this” can be career‑ending; silence is not reliable consent.
• Dangerous or illegal in high‑risk/regulated domains or for one‑way‑door changes (safety, compliance, production‑critical).
• Can be abused as CYA, or as a way to pressure busy stakeholders who simply didn’t see the message.
• Several managers say they’d see this style (without trust) as a liability or insubordination.

Culture & Context

• Works best in high‑trust, bias‑for‑action cultures; may backfire in rigid hierarchies or where independent action is seen as insubordinate.
• Experiences differ by country and company type (startups vs large orgs; US vs Europe/Scandinavia vs others).
• Recognized parallels to change advisory boards and RACI: shifting from “Consult” to “Inform” for appropriate decisions.

Application & Wording Nuances

• Safer phrasings suggested:
  • “I’m planning to do X on [date]; please let me know if you have any concerns.”
  • “We’ll proceed with X on [date] unless this conflicts with [constraint].”
• Emphasis from multiple commenters:
  • Use only within your remit, for reversible/low‑risk items.
  • Do real homework first (alternatives, risks, rollback plan).
  • Often better to seek team consensus, then inform the boss.
  • Tone, trust, and track record are decisive; abuse quickly erodes credibility.

Headline numbers and “average” vs reality

• Commenters note the study’s ~$513/week and slight increase in hours translates to roughly $13/hour before expenses, contradicting platform claims of “$30/hour on average.”
• There is extended criticism of using averages in highly skewed, power‑law distributions; median or bottom‑decile metrics are seen as more honest.
• Several argue platforms use creative accounting (e.g., counting only “active” time) to inflate hourly earnings.

Net earnings after costs

• Many emphasize that gross earnings ignore fuel, maintenance, insurance, depreciation, and self‑employment taxes; some estimate net as low as ~$10/hour or worse.
• Examples from the US and Norway suggest that, after costs, full‑time gig work can land well below local median wages and near or below minimum wage.
• Some say it only makes sense as “beer money,” not as a sustainable livelihood.

Flexibility vs pay and worker classification

• A recurring theme: flexibility (choosing when/where to work) is the main appeal; some drivers report being happy with autonomy despite low pay.
• Others counter that “make your own hours” is overstated, as real earnings cluster around peak demand times dictated by the platform/market.
• Debate over whether gig workers are truly independent contractors if they can’t set prices; some see them stuck with the worst of both worlds (no benefits, no rate control).

Broader economic and policy context

• Some blame legislation like Prop 22 for cementing low‑protection status; others point to stagnant minimum wage, rising living costs, and inequality.
• There is discussion of CPI understating real inflation (housing, food), further eroding gig incomes.
• One thread argues gig work may suppress pressure to raise minimum wage.

Automation, immigration, and platform dynamics

• In SF, riders report switching to robotaxis and expect human drivers to “fight over scraps” as automation spreads.
• Several claim large shares of delivery drivers may be undocumented or using borrowed accounts, potentially increasing labor supply and pushing down wages; others challenge the evidence and assumptions.
• Some see gig apps as part of a “sinkhole” in the labor market, externalizing risk onto workers while platforms and investors capture value, even if many platforms have historically run at a loss.

Normative takeaways

• Viewpoints range from “don’t be a gig worker” to “it fills a useful niche for those prioritizing flexibility.”
• Many agree the core problem is less the existence of gig work and more inadequate social safety nets, high costs, and weak protections for low‑wage workers.

Pledge/Unveil and Sandboxing

• Many felt pledge/unveil deserved more prominence, calling them standout innovations.
• Clarified threat model: not distrusting the program itself, but limiting damage if it’s compromised mid-run by tightening syscalls and filesystem access after startup.
• Some argued sandboxing should be configured externally (like Docker) rather than in-app; others countered that developers understand their program’s lifecycle better than admins.
• Linux analogues (seccomp, Landlock) and unikernel ports were discussed; there was some confusion then correction about who inspired whom.

Security Mitigations and External Assessments

• The isopenbsdsecu.re site was cited as a detailed, if harsh, assessment: critical in tone but explicitly praising malloc, atexit hardening, and pledge.
• Concerns raised there about outdated packages (e.g., Firefox, Tor) were rebutted as outdated FUD, with references to active maintenance.
• Newer mitigations mentioned: mimmutable/mseal, execute‑only memory, BTI/IBT, and random-data sections (e.g., for RETGUARD).
• Some worry execute‑only on ARM conflicts with PAN; others argue OpenBSD’s priorities differ and EPAN support is coming.

Daily Use, Performance, and Hardware Support

• Several run OpenBSD daily on ThinkPads and some Dells, reporting solid stability but weaker power management and battery life than Linux.
• Performance views differ: some call it “incredibly slow”, others say only disk I/O and browsers (without GPU accel) are notably slower; SMT is disabled by default for security.
• Major limitations noted: no Bluetooth stack (removed for quality/security reasons), no HDMI audio, fewer ports. For some, that disqualifies it as a laptop OS; others accept wired peripherals and see this as a deliberate trade-off.
• Used successfully as a home router/firewall (pf, CARP, HAProxy), with console-based administration; a few GUI frontends exist but are niche.

Funding, Licensing, and Open Source Economics

• Debate over whether large companies using OpenSSH “owe” OpenBSD funding: permissive licensing grants total freedom, but many see an ethical duty to contribute to a shared commons.
• Some argue capitalism structurally favors taking without giving; others say reciprocity should be encoded via copyleft or commercial licensing, not moral appeals.
• Broader argument: open source both depresses some categories of paid work (no one paid to re‑implement JPEG, kernels, databases) and enables higher-level work and new products.
• Burnout and underfunding (e.g., XZ, OpenSSL/Heartbleed) used as evidence that relying on volunteer labor has real security costs.

Languages, Implementation, and Kernel Architecture

• Critique: a “security-obsessed” OS still written in C inherits avoidable memory bugs; suggestion to move userland or more components to safer languages.
• Pushback centers on: Rust’s heavy toolchain, POSIX compatibility gaps, incomplete 1:1 replacements for core utilities, and OpenBSD’s “base builds base” rule; also portability to obscure architectures.
• Alternatives like Zig or OCaml were mentioned but seen as immature or unsuitable (e.g., GC in kernels).
• Kernel locking: the historic “giant lock” is being steadily removed; network stack still has work in progress but performance has improved notably.

Choosing and Using OpenBSD vs Other BSDs

• For newcomers, FreeBSD is described as closer to Linux, with broader hardware support, ZFS, better performance, and more ports.
• OpenBSD is framed as the “correctness and security first” BSD, with excellent man pages and a tightly integrated base system, but with deliberate feature omissions and rougher edges for desktop use.

Text vs. Icons: Which Is “Better”?

• Many argue text is fundamentally clearer: we’ve spent years learning words; icons are often app-specific, ambiguous, and slower to decode for anything beyond a tiny set of standard symbols (play, pause, close, search, trash).
• Others push back on “strictly superior”: some users recognize icons faster and they save horizontal space, especially on crowded UIs or mobile.
• Several note that icons are fine for a handful of common actions; beyond ~5–10 actions, unlabeled pictograms become “mystery meat navigation.”

Discoverability, Learning Curve, and Cognitive Load

• Users describe hunting through monochrome toolbars (macOS Markup, Pixelmator, Obsidian, JetBrains IDE redesign) and having to hover each icon and wait for a delayed tooltip.
• This creates ongoing friction, especially across many different apps each with 5–10 unique icons; people forget meanings between sessions.
• A proposed heuristic: a GUI is “good” if you can easily guide someone verbally (“click ‘Share Screen’”) rather than “the grey thing with an arrow.”
• Overly “intuitive” icon-only UIs often end up needing more explanation in popups, docs, or videos.

Best Practice: Combine Text and Icons, With Structure

• Many prefer text + icons: text explains; familiar icons act as visual anchors and speed scanning; both support different cognitive styles.
• Example praised: older Windows/Word menus using icons only on common commands, giving the menu a distinctive “shape.” Criticized: sidebars where every item has a similar vague icon, producing a blur.
• Grouping actions by topic and using icons selectively is seen as better than hiding “unimportant” actions or reordering menus, which breaks muscle memory.

Accessibility, Diversity, and Internationalization

• Visual limitations (low contrast, color blindness, large cursors) and age make icon-only UIs harder; labels also help screen readers.
• Color can aid recognition but cannot be the sole differentiator.
• Internationalization is cited for icons, but commenters note: icons themselves are culturally loaded and you need alt text/translations anyway; auto-translation makes simple labels cheap.
• Analogies to traffic signs: Europe leans icon-heavy due to language diversity; people are trained on those icons—software rarely gets that level of training.

Platform and Design Culture

• On phones, icon-only nav is sometimes accepted due to limited space; on desktop, commenters see little justification for removing labels and menu bars.
• Criticism falls on both “devs doing UX” and visually focused designers chasing aesthetics and trends (flat, monochrome, Chrome-style static toolbars) over guidelines and usability.
• Many want OS- or app-level toggles to choose icon-only, text-only, or both, plus search/command palettes for complex apps.

Ownership vs. License Language

• Many argue that showing “license to view” under a “Buy” button is deceptive; they want “Rent” or similarly explicit language.
• Several say the disclosure isn’t very informative: what matters are concrete rights (revocability, transfer, time limits, offline backup), not just the word “license.”
• Some contend that true “purchase” for digital goods should mean a perpetual, irrevocable, transferable license with DRM‑free files; others claim digital “ownership” is inherently different from physical.

Trust, Revocation, and Platform Power

• Users cite past removals of digital content (e.g., Kindle’s 1984 incident, shutdowns of ebook/music stores, Sony video removals) as proof that access can disappear despite payment.
• Amazon’s removal of the “download via USB” option is seen as tightening lock‑in and disqualifying it from “permanent offline” exemptions in new laws.
• A minority trust Amazon/Steam‑style platforms and are comfortable with account‑tied access; others explicitly distrust Amazon’s incentives and future behavior.

Piracy: Ethics, Legality, and Practice

• Many say Amazon’s licensing model “legitimizes” piracy or makes it the “lesser evil,” especially when no DRM‑free option exists.
• Counter‑arguments stress that piracy undermines authors’ livelihoods and that license terms, though disliked, don’t justify infringement.
• Some adopt hybrid ethics: buy a copy (ideally non‑Amazon) to support the author, then pirate or strip DRM for a usable archival copy.
• Technical discussion covers Calibre + DeDRM, jailbreaks, KOReader, torrenting with VPNs, and the DMCA’s anti‑circumvention rules (notably, fair use doesn’t clearly protect DRM removal).

Alternatives and Workarounds

• Strong interest in DRM‑free sources: Kobo (with DRM‑free labeling), some publishers’ own sites, Humble Bundle (often), Ebooks.com filters, Libro.fm for audiobooks, library apps (Libby), and piracy sites.
• Several are migrating from Kindle to Kobo, or at least bulk‑downloading and de‑DRMing their Kindle libraries before Amazon’s deadline.
• Others highlight library use, used/physical books, and open collections (Project Gutenberg, Standard Ebooks) to avoid these issues.

Impact on Authors and Publishers

• An author in the thread explains that Amazon royalties are often very low; buying directly from publishers or local bookstores yields more income for them.
• Libraries are generally portrayed as positive for authors (building readership) but more ambivalent for publishers.
• Some argue current IP and DRM regimes benefit large intermediaries more than authors, blocking a “Bandcamp for books”‑style market.

Current use of Dreamweaver today

• Several commenters still use Dreamweaver, but mostly in narrow roles:
  • Updating or maintaining legacy personal or client sites.
  • Using old perpetual versions (e.g., Dreamweaver 8) under Wine or on older systems.
  • As a convenient FTP client, template editor for WordPress, or for advanced multi-file find/replace and HTML table generation.
• There are anecdotes of institutional/legacy use:
  • A school library system on an air‑gapped Windows XP box using Dreamweaver + FileMaker.
  • Hearsay (explicitly unverified) that some government sites still depend on Dreamweaver licenses.

Perceptions of quality and role

• Strong disagreement over whether it was ever “professional”:
  • Some say it was essentially a toy, mostly for students and hobbyists, with poor code output and weak support for modern workflows.
  • Others report it being used as the primary tool in agencies and real jobs, including classic ASP, PHP/MySQL CRUD apps, SharePoint themes, and image maps, arguing it was powerful for its era.
• Consensus that today it’s ill‑suited for modern JS‑heavy frontends and that subscription pricing makes even less sense for small static sites.

Successors and modern alternatives

• For non‑technical users: Squarespace, Wix, and WordPress are seen as having absorbed Dreamweaver’s market (“edit button” over HTML editor).
• For designer‑dev workflows:
  • Webflow, Bootstrap Studio, Pinegrow, Wappler, Coda/Nova and various WYSIWYG/CMS tools are named as successors or partial replacements.
  • Some still use Seamonkey Composer, Kompozer, and older tools like HomeSite.
• One view is that Tailwind + code editors replaces the need for visual layout tools for many developers.

Nostalgia and learning impact

• Many learned HTML/CSS, MySQL, and early web dev through Dreamweaver (often pirated copies), reversing from WYSIWYG to source view; some credit it with starting their careers.
• Strong nostalgia for the broader Macromedia/Adobe era (Dreamweaver, Flash, Fireworks, ColdFusion, etc.) and the sense that tooling then made basic CRUD and page design simpler than today’s stacks.

Related tangents: Flash and HTML editors

• Flash’s demise sparks debate: some blame Apple’s iOS policy, others Adobe’s security/performance failures; some miss Flash’s capabilities, others are glad to see its ads and battery drain gone.
• Several note how hard it remains to build good WYSIWYG HTML editors, despite modern open‑source browser engines, and lament the poor HTML output of tools like Word and email clients such as Outlook.
• Speculation appears about a “new Dreamweaver” built around Figma, React components, and LLMs, but it’s seen as complex and commercially risky.