Hacker News, Distilled

Scope of “Recreating Photoshop”

• Many argue the project is far from full Photoshop parity; more like a basic editor or “MS Paint plus filters.”
• Others emphasize that, as an undergraduate thesis from 2006, it’s extremely impressive—especially given the custom UI and feature set for the time.
• Some note that marketing it as “recreating Photoshop” invites criticism, while others don’t see the title as clickbait.
• Comparisons are made to products like Photopea and Krita as closer or better modern alternatives at this feature level.

UI/UX: Photoshop vs GIMP vs Others

• Strong disagreement over GIMP’s UI: some find it “astonishingly bad” and uniquely user-hostile, others say it’s fine or comparable to Photoshop once learned.
• One view: open source projects over-prioritize technical features and under-invest in usability and consistency; feedback on UX is often dismissed.
• Counterview: users should be willing to learn workflows; calling open source “user hostile” is framed as entitlement.
• Several people argue Photoshop’s UI is also a mess—nested menus, conflicting shortcuts, specialized dialogs (e.g., Liquify), and weak 3D/vector/animation tools.
• Krita is generally seen as strong for digital painting but weaker for text, filters, and some workflows. Nostalgia appears for older tools like Paint Shop Pro 7.

Difficulty of UI vs Core Logic

• Some developers say the real challenge in such an editor is the UI, not the image-processing algorithms.
• Others recount how complex it is to hand-roll windowing, dialogs, and layout, especially without higher-level frameworks.

Single Executable, Installers, and the Registry

• The project’s “single EXE, no installer, no registry” approach resonates strongly; many miss that era of Windows software.
• Go is praised for making single-binary distribution easy; Rust/.NET and static linking raise build and licensing complications.
• Debate over installers:
  • Pro: they add Start Menu entries, file associations, proper OS integration.
  • Con: they clutter the registry, scatter data (especially in AppData), and complicate backups and reinstalls.
• Long tangent compares Windows (Registry, AppData, installers) to macOS (.app bundles, .DS_Store) and notes both ecosystems’ messiness.

Academic and Commercial Aspects

• Commenters contrast this substantial thesis project with today’s often simpler CRUD-style theses.
• Some suggest it might have been commercializable in 2006; others think even then competition and free tools would limit viability.
• There’s reflection on how hard open source work often goes unrewarded, and on the desire for better compensation models.

Beatles and Cultural Shifts

• Several comments frame 1964 not just as a musical break but a broader shift in entertainment: from vaudeville-style “acts” and mid‑Atlantic formality toward a more “real” voice and personal expression in rock, film, and TV.
• One view: pre‑Beatles pop and vaudeville were mostly “entertainment,” while 60s rock, folk, and later jazz shifts (Ellington→Coltrane) foregrounded self‑expression and interior life.
• Others push back that similar breaks recur regularly (e.g., Nirvana vs hair metal, later rap, electronic music), and boomers overstate the 60s’ uniqueness.

Comparisons to Other Eras and Genres

• Rap/hip‑hop, electronic music (house, techno, UK garage, trip‑hop), and late‑70s/early‑80s rock are cited as equally or more transformative for their periods.
• Some argue Elvis, Motown, and Black blues pioneers had already globally reshaped music before the Beatles; others say the Beatles’ speed of evolution (early singles to Abbey Road in ~6 years) and worldwide impact remain unmatched.
• There’s debate over whether there “can’t” be another Beatles due to media fragmentation, TV/air travel being new at the time, and music’s diminished centrality vs phones, games, and apps.

Charts, One‑Hit Wonders, and Industry Mechanics

• The spike in 90s one‑hit wonders feels real to people who lived through wall‑to‑wall radio rotation.
• Multiple comments stress the 1991 SoundScan shift: pre‑91 Billboard relied on self‑reported store data and label/DJ manipulation; post‑91 sales and genres (rap, grunge, country, techno) suddenly surfaced more accurately.
• Some argue this means the Beatles/90s “killed careers”; others say it actually opened the field, allowing many artists to get one hit who previously would have had none.

Artist Longevity vs Career “Deaths”

• Examples of extreme longevity (Cliff Richard, Cher, Stones, McCartney, Max Martin) contrast with prolific artists who stop having hits but keep producing worthwhile work or powerful live shows.
• Conclusion from several commenters: trajectories are highly individual; “losing the charts” doesn’t equal artistic death.

Modern Fragmentation and Shared Culture

• Pop charts after ~2000 are seen as much less representative of generational taste; listening is niche and algorithm‑driven.
• Some lament the loss of widely shared “era soundtracks” and monocultural events (e.g., Game of Thrones, MTV hits), others celebrate today’s vast long tail and ease of discovery off‑radio.

DIY YouTube Frontends & Workflows

• Many commenters have built similar personal tools around yt-dlp: simple web/PHP/Flask frontends, Plex/Jellyfin pipelines, bookmarklets, and mpv-based queues.
• Common goals: automated downloading, transcoding to device‑friendly formats, audio-only extraction, playlist handling, filesystem organization, and integration with media servers.
• Several mention this as a fun “small project” space, even for non–web developers.

Motivations: Enshittification, UI, and Control

• Strong dissatisfaction with YouTube’s UI/UX: clutter, dark patterns, shorts, community posts in the subscriptions feed, and poor performance (especially on some Firefox setups and TV devices).
• People want chronological, subscription‑only feeds and fewer distractions. Tips include disabling watch history, using subscription URLs directly, and extensions like Unhook, h264ify, SmartTube, Vinegar, FreeTube, NewPipe.
• Broader theme of “enshittification of the web” and desire for self‑hosted frontends (SearXNG, Matrix, etc.) to regain control and privacy.

Discovery vs. Going Off‑Platform

• Concern: watching via third‑party frontends breaks recommendation feedback loops and may cause YouTube to repeatedly recommend already‑watched videos.
• Some argue discovery is mostly a social problem: a small set of “cornerstone” creators and communities (RSS, HN, niche feeds) can provide more than enough content.
• Others value serendipitous algorithmic discovery and see real loss in leaving the official app.
• Ideas raised: local/custom recommenders using signals from HN/Reddit, third‑party “algorithm engines,” or using the official app only for discovery then sharing URLs to an ad‑free player.

DRM, Ads, Legality, and yt-dlp Risk

• Debate over DRM: one side calls it useless and punitive; another argues it’s “working as intended” for non‑paying users.
• Some fear popularizing frontends will increase pressure to break yt-dlp (citing youtube-dl’s DMCA issues). Others reject this gatekeeping and blame YouTube’s product choices for demand.
• Use cases beyond “free stuff” are emphasized: archival, fair‑use clipping, public‑domain work, forensic/archival research, and professional creator workflows.
• Discussion of ad funding vs. privacy: whether users have any obligation to watch ads, and whether ad‑tracking practices justify blocking.
• Legal nuances: some countries grant a right to private copies even for copyrighted works; monetizing such tools is viewed as especially risky.

Children, Safety, and Monetization

• Parents report using curated channel whitelists and “safe” apps to shield kids from low‑quality or harmful content.
• There is interest in network‑wide or offline solutions built around yt-dlp, but also warnings that monetizing such systems could make them legal targets.

Technical Notes & Feature Requests

• yt-dlp’s SponsorBlock integration, cookie handling, Docker images, and quality selection are discussed.
• Some want simpler desktop packaging (single executable/Electron) versus self‑hosted servers.
• LLM-based layers (LM Studio/Ollama, Videocrawl) are highlighted for transcripts, summaries, and code/reference extraction from videos.

Kanban, Affordance, and Design

• Several comments connect the milk card to concepts like affordances, mechanism design, and poka‑yoke: physical or process designs that “tell you what to do” and make the right behavior obvious.
• The key shared idea: good systems and objects communicate the next action without extra instructions or emotional friction.

Event-Driven Restocking vs Polling

• The milk card is praised as an event trigger: work is pulled when a condition is met, not by the manager periodically polling cupboards.
• Some propose refinements (reorder box, sensors, NFC, cameras), often jokingly, to illustrate the software instinct to over‑engineer.
• Others note this is only worth it at certain scales; for a single small office, more automation is unnecessary complexity.

Office Manager Role vs Distributed Chores

• Strong disagreement on whether it’s appropriate to “outsource” inventory signaling to all employees.
• One side: employees should focus on their core work; monitoring supplies is the office manager’s job, and walking a card over is an interruption and misuse of expensive time.
• The other side: 30 seconds to move a card that saves many minutes of systematic checking is a good trade; teams should optimize for overall system effectiveness, not individual “importance.”
• Underneath is a cultural question: do people see shared small chores as mutual support or as demeaning “housework”?

Efficiency, Simplicity, and Alternatives

• Critics suggest weekly inventory checks and batched ordering as “more efficient” and less cognitively complex than tickets.
• Defenders argue the Kanban approach avoids constant checking, works even when the purchaser doesn’t use the product, and can encode details (brand, type) on the card.
• The phrase “as simple as possible, but not simpler” is discussed: the card is seen as a minimum viable mechanism that still achieves the goal.

Everyday Kanban Patterns

• Many examples surface of similar “you’re running low” cues: trash bags, receipt paper, toilet paper, rolling papers, plastic wrap, dog‑poop bags, industrial milk coolers.
• These are framed as common, successful applications of visual pull signals in daily life.

Kanban in Manufacturing vs Software

• Several comments contrast original Kanban (replenishment signals, pull systems, WIP limits) with how software teams use “Kanban boards.”
• There’s debate over how well manufacturing metaphors fit creative, variable software work, and whether software “Kanban” has drifted into buzzword territory.

Antitrust motives and political context

• Many commenters support aggressive trust-busting, including vertical integrations, seeing current tech as “feudal” with a few mega-corps controlling everything.
• Others are cynical: DOJ and the administration are viewed as political actors who might extract concessions while preserving core power structures.
• Some argue structural separation (browser vs search/ads) is the only remedy that can’t be easily undermined.

Would forcing a Chrome sale help or hurt the web?

• Pro‑divestment side: Google uses Chrome’s dominance to reinforce its advertising and search monopolies, shape standards, and disadvantage competitors; this is compared to Microsoft/IE and AT&T.
• Anti‑divestment side: Chrome is one of very few entities capable of funding a modern engine; a sale could lead to stagnation, Linux neglect, closed-source forks, or even more user-hostile owners (PE, Meta, Oracle).
• Some argue browsers are already “complete enough” and slower development might even be good (less churn, fewer hostile features like Manifest V3).

Business models and “who pays for a browser?”

• Strong debate over whether a standalone ChromeCo is viable:
  • Skeptics: no one will pay subscriptions; free corporate browsers destroyed the market for paid ones.
  • Others: Chrome could sell the same data it currently feeds Google, or be funded as a non-profit/foundation, or via search-default deals (though these deals are themselves under attack).
• Several note that free, ad-funded models externalize costs onto users and society, but also that many users globally can’t afford to pay.

Privacy, tracking, and advertising

• Repeated criticism that Chrome is fundamentally a surveillance and ad-optimization tool: slow to add privacy protections, hobbles ad blockers (Manifest V3), promotes AMP, and uploads rich behavioral data.
• Some defend Google as “no worse than others” and providing valuable free services; others counter that monetizing personal data at this scale is inherently harmful and anti-democratic.

Chrome’s influence on standards and competition

• Concern that Google’s dominance in browser + ads + major web properties lets it unilaterally push or block standards (e.g., WEI, DRM, cookie replacements, JPEG‑XL, extension restrictions).
• Others highlight the high-quality, open work on Blink and standards as a public good, arguing that without a deep-pocketed “steward,” the open web would lose ground to proprietary app ecosystems.

Impact on other browsers and the broader ecosystem

• Fear that banning default-search payments will financially gut Firefox and reduce Apple’s Safari investment.
• Some think breaking Google’s integration would at least stop it from weaponizing Gmail/Docs/YouTube and Chrome together against rivals.
• Broader view: without structural reform, power will simply shift among big players; lasting change may require stronger privacy law, ad regulation, or even rethinking the web’s economics.

Tor shutdown, censorship, and NYT’s replacement channels

• Many see ending the onion service as symbolic retreat from serving readers under censorship.
• Suggesting WhatsApp/Telegram as alternatives is widely criticized:
  • Governments can and do block those apps.
  • Using them discloses to private companies that you read NYT and which stories, risky where NYT access is itself suspicious or banned.
• Some hope NYT will at least keep SecureDrop over Tor; others assume Tor support declined after key security staff left.

Technical value of an onion service

• Onion services avoid Tor exit nodes and the web PKI, reducing risk of exit-node MITM and deanonymization.
• They also reduce load on scarce exit nodes, modestly strengthening the Tor network.
• One commenter shows how trivial it is to stand up a hidden service; vanity-address mining is highlighted as the only “hard” part.

Paywalls, access paths, and workarounds

• Paywall weakens the onion site’s value for at-risk readers; questions arise about how to subscribe anonymously.
• Some note the Tor version was at one point un-paywalled.
• archive.is and similar tools are described as the “de facto” way to read NYT, though:
  • They depend on prior archiving, may be blocked, and include telemetry.
  • Extensions like Bypass Paywalls Clean work locally but raise trust/auditability concerns.

Trust in Tor and practical reachability

• One commenter says they wouldn’t trust Tor for life-or-death anonymity; another argues that, when the alternative is inaction, Tor is still the rational risk.
• Separate discussion notes that NYT’s regular site remains reachable over Tor if exit nodes aren’t blocked; the onion’s advantage is security and resilience, not basic reach.

Broader critique of NYT’s role and bias

• Large subthread uses the Tor shutdown as another data point that NYT aligns with state and corporate power:
  • Allegations include ad-driven incentives, government influence, overuse of anonymous official sources, and long history of amplifying US foreign-policy narratives.
  • Specific examples cited: delayed NSA warrantless-surveillance story, Iraq-war coverage, Venezuela/Bolivia reporting, Holocaust undercoverage, and recent Gaza/Israel stories.
• Others push back, describing NYT as comparatively strong on truth-seeking, noting internal debate on controversial stories, and disputing claims that they acted to re-elect Bush or are “pro-Trump.”

Authoritarianism and self-censorship

• One thread frames dropping the onion site as “obeying in advance” of future speech restrictions, arguing that such preemptive compliance normalizes and eases authoritarian control.

Incident and attack behavior

• A popular GitHub Action (tj-actions/changed-files) was compromised: many v35+ tags were retargeted to a malicious commit.
• The malicious code downloaded a Python script that attempted to dump CI/CD secrets from the runner process memory and print them to stdout, relying on build logs (especially public ones) as the exfiltration channel.
• The external gist hosting the payload was later deleted, which stopped further exfiltration but did not retroactively protect any already-run workflows.
• The repo and org briefly 404’d, then reappeared. The maintainer attributes the incident to a compromised personal access token of a bot account; some commenters doubt or want more detail.

Tags, pinning, and automation bots

• A core issue: Git tags are mutable pointers, not immutable versions. The attacker simply repointed all version tags to the malicious commit, instantly “upgrading” users without config changes.
• Many argue that only commit hashes are safe for uses: in workflows; tags (including v4, v35.9.3, etc.) should not be trusted.
• Others note that even hash pinning can be undermined by automated dependency bots (Renovate, Dependabot) that auto-update hashes and may auto-merge; this is how some projects pulled in the compromised version.
• There’s support for:
  • GitHub-level “immutable tags” or tag-protection policies.
  • A lockfile mechanism for actions, or tooling to auto-“bake” tags into hashes.
  • New “immutable actions” features GitHub is previewing.

Trust in dependencies and the broader supply chain

• Many commenters express growing reluctance to use:
  • Third-party GitHub Actions beyond official ones.
  • Deep dependency trees (npm, NuGet, VS Code extensions, browser extensions).
• Strategies mentioned:
  • Forking or vendoring actions and extensions; turning off auto-updates.
  • Preferring “batteries-included” languages/standard libraries and minimal deps.
  • Copying small snippets instead of pulling whole libraries (“a little copying is better than a little dependency”).
• Others note this is not new; it’s a classic software supply-chain issue exacerbated by cultural norms in some ecosystems (e.g., massive npm graphs) and economic pressures on maintainers.

Sandboxing, capabilities, and CI/CD design

• Strong sentiment that tools and actions should run with sharply limited capabilities:
  • Default-deny network access for most tools/actions.
  • Fine-grained file I/O and network policies (containers, systemd, firejail, bubblewrap, OS capabilities like pledge/Capsicum/Landlock).
• Several argue CI and CD should be separated:
  • CI runners should never hold production-deployment tokens.
  • CI should at most write artifacts; a separate, more tightly controlled system should handle deployment.
• Some already run all dev and builds inside VMs/containers for extra isolation.

Mitigations, tools, and vendor behavior

• StepSecurity’s hardened runner detected the incident via anomalous outbound network traffic and is promoted as a defense; some appreciate the detection, others criticize the surrounding marketing and paywalled features.
• Other vendors push static/ML-based malicious-code detectors; several commenters are skeptical, arguing attackers will adapt and obfuscate once they know the rules.
• Suggestions include:
  • Org-level whitelists for allowed actions, ideally pinned by hash.
  • Disabling or tightly constraining third-party actions for paid orgs.
  • Better defaults and documentation from GitHub (e.g., examples using hashes, not tags).

Impact, response, and unresolved questions

• The action was widely used (tens of thousands of repos), so many organizations are now:
  • Removing the action.
  • Rotating secrets, especially where logs are public or broadly accessible.
• Community members published drop-in forks and mirrors that remove the malicious code.
• Some worry about stolen tokens from prominent public projects and downstream compromise of package registries; the real scope remains unclear.
• A recurring pessimistic theme: the fundamental tension between staying up-to-date (for security fixes) and avoiding malicious updates is unsolved; automation helps with speed but can amplify attacks.

Scope of the Change & “Wasn’t It Already Doing This?”

• Some see the news as scare‑mongering, arguing Echo has always needed the cloud and thus always sent voice to Amazon.
• Others counter that newer models had an explicit “Do Not Send Voice Recordings” setting and on‑device processing, so this is a real rollback of a privacy option.
• Clarification from quoted docs: previously, audio could be processed locally into text, with only the text sent to Amazon and the audio deleted. That setting is being removed on some devices.

Local Processing, Zigbee, and Offline Use

• 2021+ devices with the AZ1 chip could handle wake‑word and some speech recognition locally.
• A small subset of use cases (e.g., controlling Zigbee devices via certain Echo models) can work fully offline when local processing is enabled.
• There’s concern that removing local processing and tying “Alexa+”/GenAI to the cloud could effectively brick current semi‑offline workflows, possibly raising “fitness for purpose” and class‑action questions.
• Unclear how long already‑configured offline Zigbee setups will continue to work.

Privacy, Surveillance, and Trust

• Many say this is exactly why they never bought an Echo (or will now unplug it / cancel Prime).
• Strong comparisons to “telescreens,” Stasi/KGB fantasies, and “surveillance capitalism”; people note we voluntarily pay for always‑on mics.
• Others are resigned: they assume all devices collect as much data as possible to sell ads and aren’t surprised.
• Comparisons across vendors: some trust Apple slightly more, distrust Google and Amazon most; others argue all big tech is bad.
• Tangents highlight broader misuse of data (e.g., medical practices selling patient info with coerced consent).

Legal / Consent Concerns

• Questions about two‑party consent states: guests in a home haven’t affirmatively agreed to be recorded.
• Some wonder if this shift could be legally challenged, but no clear answer emerges.

Alternatives & Local LLMs

• Interest in offline/open‑source replacements: Home Assistant Voice, ESP32 boxes, Wyoming protocol, local STT/TTS/LLMs.
• Desire for a simple local “LLM appliance” for home automation, but skepticism that there’s a mass market beyond enthusiasts; concern that hardware would obsolete quickly.

Smartphones vs Speakers

• Several note smartphones are functionally similar surveillance devices, yet far more socially accepted; others say they dislike phones too but see them as a pragmatic necessity.

Impact Scope & “Non‑News?” View

• One commenter points out local‑only processing was limited to a few US/English models; for most users nothing is changing.
• From this perspective, the story is framed as a small technical regression inflated into “evil oligarchs” rhetoric, though others disagree because it removes an important privacy promise.

Overall Reception of the Series

• Many commenters call Age of Resistance an outstanding or even “hidden gem” series: gorgeous, lovingly crafted, and worth watching for both fans and newcomers.
• Others like it but balk at the “masterpiece” label, seeing it as very good but not exceptional.
• A substantial minority actively dislike it, criticizing the writing as shallow, overworked “writers’ room” fare with heavy-handed themes and flat, didactic narration.

Comparison to the Original Film and Other Fantasy

• Several argue the original film is the true masterpiece: more morally complex (duality, unity of Mystics/Skeksis), more practical effects, and a less conventional good-vs-evil frame.
• The series is criticized for leaning more on CGI and simplifying morality; defenders say it’s a respectful prequel that sets up the film well and explores how the Gelfling are destroyed.
• Some viewers find it too reminiscent of Lord of the Rings–style fantasy (pretty heroes vs ugly villains, standard quest structure) and lose interest early.

Puppetry, Medium, and “Dark vs Adult” Debate

• Multiple comments note that puppets/animation cause many adults to dismiss the show as “for kids,” echoing experiences with other series (e.g., Yonderland, Gravity Falls, Andor, Scavenger’s Reign).
• One thread critiques the article’s conflation of “dark” with “adult,” arguing that grim tone or violence doesn’t equal mature storytelling; light, nuanced works can be more adult than grimdark spectacles.

Cancellation, Streaming Economics, and Discoverability

• Strong disappointment over its cancellation; some call it “criminal” given the artistry involved.
• Others note that the budget was unusually high and unlikely to be matched elsewhere; we’re lucky to have even one season.
• Age of Resistance is grouped with other “weird” or ambitious shows (Scavenger’s Reign, Altered Carbon) that were cut despite dedicated fanbases.
• Commenters criticize streaming “bean-counter” logic: shows must be instant hits, algorithms fail to surface them, and detailed metrics are used short-sightedly to justify cancellations, undermining long-tail, cult TV potential.

Access and Legacy

• Some wish they could buy and own it outright; one commenter links an Internet Archive copy.
• A few argue that knowing the tragic endpoint means one excellent season is a fine place to stop.

Allegations of Fraud and Judicial Pushback

• Commenters highlight the judge demanding actual evidence of fraud before allowing climate grants to be halted or clawed back, and ordering DOJ to substantiate its claims.
• Many see a pattern of the administration labeling things “fraud” without proof, and view this as political abuse rather than legal process.
• Some argue courts should respond more aggressively: jailing law enforcement for perjury, disbarring government lawyers who knowingly advance baseless claims, and ending automatic “good faith” deference to prosecutors and police.
• Others note that in an adversarial system, lawyers are expected to make the strongest case for their side, and disbarment/discipline is intentionally rare so the system can function.

Weaponization of Law Enforcement and Partisan Comparisons

• One side describes this as a major escalation: using FBI/EPA/Treasury to freeze nonprofit funds and target political opponents without evidence.
• Others attempt to relativize it, comparing it to past investigations (e.g., Trump-era probes, Obama/Biden-era actions) and even the Iraq War, arguing U.S. politics has tolerated far worse.
• A lengthy subthread debates Trump investigations (Crossfire Hurricane, Mar‑a‑Lago search) vs. Biden’s and others’ document mishandling, Hunter Biden’s conviction/pardon, and Jan. 6 pardons.
• Each side accuses the other of hypocrisy, selective outrage, and creating false equivalences.

Constitutional and Checks‑and‑Balances Concerns

• Several commenters stress that the Inflation Reduction Act is a statute, not an executive order: Congress appropriated the funds, so the president is constitutionally obligated to execute the law, not unilaterally undo it.
• Freezing grants without evidence is framed as an attempt to usurp Congress’s “power of the purse,” likened to exempting allies from taxes by fiat.
• Others counter that elections were held, the current administration won, and Congress is explicitly backing many of these moves—so, in a narrow formal sense, the system is “working as intended,” even if outcomes are disliked.
• Critics respond that Congress can also undermine checks and balances, e.g., by limiting its own ability to challenge executive actions.

Nonprofits, Climate Grants, and “Conflicts of Interest”

• Critics of the grants cite examples from the complaint: a “new” nonprofit with minimal reported revenue receiving a multi‑billion‑dollar award, and an executive applying for funds while on a White House advisory council, as signs of favoritism and embedded conflicts.
• Defenders point out that the “new nonprofit” is a coalition of large, long‑standing organizations (including Habitat for Humanity, United Way, and others), and that the alleged “ties” (e.g., advisory work at one member group) are tenuous.
• This is characterized as classic McCarthy‑style guilt by association: start from the political conclusion (“kill this program”) and work backward to find any link that can suggest corruption.

Broader Distrust of NGOs and Government

• Some argue that NGOs and nonprofits are structurally ripe for abuse: politicians’ allies create entities with virtuous names, receive huge grants, then use them for high salaries and political work that government couldn’t openly fund.
• Others counter that U.S. nonprofits must publicly file detailed financial disclosures, often with mandated audits, making them more transparent than, for example, large defense agencies.
• A specific nonprofit’s Form 990 is dissected as an example of “doing very little for a lot of money,” while a rebuttal notes it is primarily an advocacy/research body, funded by private foundations rather than government, and judged by its policy impact, not “widgets produced.”

Democracy, Autocracy, and Meta‑Discussion

• Multiple commenters see this episode as part of a broader slide toward autocracy: threats to members of Congress via primaries, politicized courts, and an executive willing to ignore or rewrite laws.
• Others insist that frequent elections, party competition, and the ability to reverse executive policies still constitute functioning democracy.
• Ideas are floated for stronger structural checks (e.g., judiciary‑controlled marshals, “anti‑agencies” inside the bureaucracy), with counterarguments that such setups would mainly incentivize sabotage of long‑term projects.
• There is some meta‑reflection on Hacker News itself: shifts in user demographics, rising wealth, and how that may have changed attitudes toward regulation, establishment power, and political discussion.

Walkability, Distance, and Infrastructure

• Many commenters say the depicted 2‑mile walk would be fine with a path, but note that in much of the US there are no sidewalks, hostile road design, and high-speed traffic, making walking or biking genuinely unsafe.
• Several highlight that, per the article, 80% of US students now live too far to walk (3+ miles) due to school consolidation, large “campus” schools at the edges of town, and car-centric suburban planning.
• Dead-end streets, cul‑de‑sacs, and “no trespassing” barriers often turn short crow‑flight distances into multi‑mile road routes.

Cars, Safety, and Culture

• Heavier, taller vehicles (SUVs, pickups) and widespread distracted driving are seen as major pedestrian risks. Some say even adults fear crossing near schools.
• Others argue US fears of trespassing, guns, and crime also discourage kids from cutting through fields or walking alone, though there’s debate: some cite data showing stranger abductions are extremely rare; others point to lived experience of violent neighborhoods.

School Policies, Liability, and Parental Fear

• Many schools require children to be released directly to an adult, often via numbered car lines with radios. Commenters trace this to liability anxiety, lawsuits/CPS fears, and post‑Columbine/post‑COVID security theater.
• Some districts resist letting even older kids walk or bike home without signed waivers; in extreme cases, parents have been investigated or arrested for allowing independent walking.

Buses and Alternatives

• Buses are widely seen as the most practical mass solution, but quality varies: long, convoluted routes, bullying, unreliable service, and funding cuts (e.g., California/Prop 13, post‑COVID labor shortages) push families into cars.
• Others call for dense networks of sidewalks, protected bike lanes, and “bike buses”; a few suggest robocars, but are reminded they don’t solve congestion.

Child Independence and Social Norms

• Strong nostalgia for walking/biking alone, making friends on the way, and learning autonomy; many contrast Europe/Japan (and some walkable US neighborhoods) where unsupervised school trips are normal.
• Others counter with experiences of real urban violence or hostile CPS/neighbor behavior, leading them to keep kids in cars despite hating the pickup line.

Proposed Fixes

• Frequent suggestions: rebuild walkable neighborhoods, shrink roads and vehicle sizes, add traffic calming and cameras, restore/expand buses, legally protect “free-range” parenting—and culturally normalize kids getting themselves to and from school.

What “Productivity” Means Here (and Why People Objected)

• Paper uses labor productivity = real sales per employee, not “same meal cheaper/better.”
• Many commenters argue this reframes a business-mix shift (toward takeout) as a “productivity surge,” which sounds misleading or celebratory.
• Some note the measure ignores unpriced service value (ambience, lingering, friendliness); productivity rises partly because that labor-intensive component shrinks.
• Others defend the paper: the value is in quantifying an obvious-seeming hypothesis with large-scale data.

COVID, Takeout, and Persistent Behavior Change

• Core empirical claim (widely accepted in the thread): short visits (<10 minutes), i.e. takeout/pickup, rose sharply during COVID and never reverted, even at fast food chains.
• Restaurants can now sell more meals with the same kitchen staff by offloading seating, dishwashing, and cleanup onto customers’ homes and delivery drivers.
• Some note that dine‑in areas have been repurposed for staging takeout orders; a few places dropped dine‑in entirely.
• Several see this as a major, probably permanent, COVID‑driven shift in habits, overlapping with WFH and greater comfort with app ordering.

Dine‑In Decline, Social Life, and “Third Places”

• Multiple comments lament loss of bars and dining rooms as social spaces and the rise of eating alone at home, often tied to loneliness and reduced “third spaces.”
• Others push back: many people simply prefer home comfort, lower COVID risk, or avoiding poor service, noise, or discrimination.
• There’s debate over whether restaurants were ever strong “community hubs” versus nostalgia/romanticization.

Delivery Apps, Costs, and Labor

• Visible surge of delivery‑app drivers aligns with the short‑visit data; some want demographics on who uses these expensive services.
• Concerns that measured restaurant productivity ignores gig‑worker costs, externalities (packaging waste, traffic, app fees), and risks (uninsured drivers).
• Several criticize tipping norms and “self‑service plus QR code” models where customers still face 18–25% tip prompts.

Economics, Measurement, and Scope

• Some accuse mainstream/Chicago‑style economics of fetishizing productivity and ignoring quality, worker welfare, and social impacts.
• Others counter that measuring sales/employee and linking it to dwell time is exactly what economists should do; broader welfare questions are separate.
• Thread notes the study covers mainly limited‑service chains (fast food, cafés), not mid‑ or high‑end full‑service restaurants, leaving that segment’s experience unclear.

What a “modern” database vs Postgres would mean

• Some argue that Postgres’s 1980s origin doesn’t matter: it’s still actively developed and best-in-class for relational + ACID.
• Others want a “new” DB that is:
  • Natively horizontally scalable (multi-writer, not just bigger boxes).
  • Postgres-compatible but with first‑class NoSQL/JSON support that avoids JSONB race conditions.
  • Under a permissive, non-telemetry, non-“bizarro” license.

Vertical vs horizontal scaling of Postgres

• Several commenters say 99.9% of companies can live on one large Postgres node plus a replica; availability is usually a bigger issue than raw scale.
• A detailed example: a single 16TB/100B+ row Postgres instance on beefy bare metal (EPYC, 1TB RAM, NVMe+ZFS) handles ~150k inserts/s, 40k tx/s, 4M reads/s with “nothing weird” beyond:
  • ZFS, non-standard Postgres block size, aggressive autovacuum tuning.
• Clarification that “Postgres doesn’t scale” usually means “you can’t just add more machines for writes.” Reads can be scaled with replicas, but fully consistent reads and multi-writer setups still need sharding or another system.
• Elastic, on-demand scaling (cloud-style) is distinguished from simply being able to handle high sustained load.

Sharding / external scale-out approaches

• Classic approach: application-level sharding via stored procedures (e.g., PL/Proxy) has been proven at very large scale.
• Citus: works very well if schema is designed around a shard/distribution key (multi-tenant is a sweet spot), but retrofitting existing schemas can take months; cross-shard FKs and some patterns remain hard.
• PgDog (topic of the article):
  • Rust-based proxy that shards, load-balances, and pools connections in front of regular Postgres nodes.
  • Positioned as “Vitess for Postgres,” avoiding Azure lock-in and aiming for easy migration from “one big DB” (treating 1 shard as base case).
  • Better replica handling noted vs Citus, but currently limited cross-shard aggregates; GROUP BY and basic aggregates are being implemented, postgres_fdw suggested as interim fallback.

Alternative databases & trade-offs

• Aurora (PG/MySQL): some report it being significantly slower than community Postgres for small queries; Aurora DSQL is mentioned as a promising, but early, distributed Postgres-compatible system.
• CockroachDB: praised for transparent distribution and Postgres-like SQL, but:
  • Multiple reports of very high resource usage and substantially higher cost vs self-hosted Postgres.
  • Frustration with changing licenses, telemetry/phone-home requirements, and aggressive enterprise focus.
• Oracle DB: cited as an example that already delivers horizontally scalable, fully transactional SQL + NoSQL features, but proprietary and not aligned with “fully open” desires.

Other technical subthreads

• JSONB: concurrent updates to different fields update the whole document; correctness may require row locks or version columns, unlike Mongo’s per-field writes.
• Stored procedures: some advocate stored-proc-only access for safety, encapsulation, and SECURITY DEFINER; others find dev experience poor despite PL/Python, PL/Perl, PL/Rust, etc.

Remote updates and ownership

• Many see this incident as evidence that internet-connected appliances undermine ownership: a company can effectively destroy a product in customers’ homes.
• Comparisons are drawn to cars, TVs, printers, and Tesla-style OTA updates; fear that “you don’t really own it” becomes the default.
• Some argue automated updates are necessary for security, but others say vendors are now a bigger real-world risk than hackers.

Corporate behavior, liability, and arbitration

• Several comments speculate Samsung is in “radio silence” due to legal advice, prioritizing liability mitigation over transparency.
• Discussion of forced arbitration clauses: widely viewed as an anti-consumer tactic to avoid class actions and public scrutiny.
• Some suggest law should increase liability for withholding information or bricking hardware, including mandatory refunds or even criminal penalties.

Smart devices, privacy, and tracking

• Strong skepticism toward connecting TVs, soundbars, and appliances to the internet; many keep them offline or on firewalled VLANs.
• Concerns that “smart” audio gear could track listening habits or even room conversations and feed broader ad/analytics ecosystems.
• Smart TV platforms (Samsung, LG, Roku, etc.) are criticized for ads, telemetry, and degrading UX over time, seen as de facto planned obsolescence.

Firmware engineering and update design

• Multiple engineers outline best practices largely absent here: staged rollouts, dual partitions / “golden” firmware, last-known-good rollbacks, and robust recovery paths (USB flashing, physical reset sequences).
• Debate over allowing downgrades: security/DRM vs. user freedom and right-to-repair; e-fuse “anti-rollback” is widely condemned as anti-consumer.
• Some note that big firms often underinvest in firmware platforms and testing, with time-to-market and BOM cost trumping reliability.

User coping strategies and alternatives

• Common tactics: never enabling WiFi, blocking Samsung domains via Pi-hole/NextDNS, using external streamers (Apple TV, Chromecast, PC, AVR) and treating TVs/soundbars as “dumb” endpoints.
• Many vow to avoid Samsung (or “smart” anything) in future, favoring discrete receivers + passive speakers or cheaper “dumb” displays plus replaceable boxes.

Perceptions of Samsung

• Numerous anecdotes of buggy updates, slow and ad-heavy UIs, unresolved defects, and poor customer support across TVs, phones, appliances, and storage.
• A minority report satisfactory Samsung TV experiences, but even they often disable tracking and ads.

Trolling culture, 4chan nostalgia, and its consequences

• Several comments riff on the “dubs” joke and reminisce about early-2010s 4chan/imageboard culture: pushing boundaries, ironic trolling, and ambiguity between sincerity and trolling.
• Others argue this nostalgia is rose‑tinted: /b/ was already toxic and harmful very early, and “it was never good.”
• A recurring theme: ironic bigotry and idiocy gradually became sincere; communities pretending to be Nazis or idiots attracted real Nazis and real idiots.
• Some describe serious personal harm from that era (shock content, radicalization, social withdrawal). Others hold this up as a cautionary tale whenever people miss the “wild west” internet.
• There’s discussion of where this culture moved: Discord, X/Telegram, Instagram Reels, TikTok. Short‑video platforms are criticized as intense echo chambers that reinforce beliefs via comment-ranking algorithms.

Security vs. fun in a 2FA app

• Many like the idea as a playful side project and appreciate someone building an app simply “for fun.”
• Others strongly object to any “cute” features or Easter eggs in security‑critical tools, seeing them as red flags for process, professionalism, and insider‑threat risk.
• Trust concerns: QR-based TOTP setup often includes service name and username, so a malicious app could link secrets to identities; there are precedents of 2FA apps sold and turned into ransomware.
• Some note open source and reputation as partial mitigations but still prefer established vendors for 2FA.
• Lock‑screen notifications are debated: author says notifications show only the number and require unlock; critics still dislike codes surfacing passively rather than via explicit user action.

Randomness, patterns, and probabilities

• Several anecdotes of “impossible‑looking” codes or odometer readings lead into discussion that many different patterns (123456, 111111, 112233, birthdays, etc.) feel special, so the probability of some notable pattern is higher than it first appears.
• Commenters work through probability estimates showing such events are unlikely but not fantastical, matching the article’s theme about perceived vs. actual randomness.

Side tangents and reactions

• Brief linguistic tangent about “voilà/viola/violé” in French, with nitpicking over spelling, conjugation, and accents.
• Multiple readers say the post brought them joy or helped with burnout, and a few propose extra pattern features (e.g., Euler’s number, birthdays, digits of π).

Hydrogen vs. Battery Buses in Practice

• Many commenters argue hydrogen buses are intrinsically less efficient and more expensive per mile than battery‑electric, even when hydrogen is “green,” due to conversion, compression, transport, and fuel‑cell losses stacking up.
• Case data cited (e.g., AC Transit) show:
  • Hydrogen infrastructure, fuel, and maintenance costing more than for battery buses.
  • Both hydrogen and battery buses still less reliable than diesel, but battery buses have the lowest per‑mile operating cost.
• Others note hydrogen buses can, in theory, replace diesel 1:1 on range and refuel time, while early battery buses sometimes needed 2:1 fleet replacement or careful charging design. Critics respond that current BEB ranges and opportunity charging (at layover stops or depots) mostly solve this.

Hydrogen Production, Greenwashing, and Influence

• Strong theme: grey and blue hydrogen (from fossil gas, with or without CCS) are framed as “green” but largely serve fossil‑fuel interests and prolong gas infrastructure.
• Several see transit hydrogen pushes as driven by lobbying, conflicts of interest in industry‑linked research consortia, and political optics, not lifecycle economics.
• Historical reference: US hydrogen initiatives in the 2000s are portrayed by some as a deliberate distraction from EVs; others dispute this or call it hindsight bias.

Battery Buses, Trolleybuses, and Grid Constraints

• Many argue batteries have “won” for city buses: fixed routes, stop‑start driving, depot charging, and big vehicles mitigate weight concerns; noise and local air quality improvements are praised.
• Counterpoints:
  • Hilly cities and cold climates can stress range and charging infrastructure.
  • Depot power upgrades (multi‑MW connections, substations) can be slow and capital‑intensive.
• Trolleybuses are cited as technically excellent, especially on hills, but suffer from high wire infrastructure cost, NIMBYism, and inflexibility. Hybrid trolley‑battery buses are mentioned as a compromise.

Emissions and EV Effectiveness

• Disagreement over “EVs just move the tailpipe”:
  • Some say EVs are only as green as the grid and short‑term just shift emissions to smokestacks.
  • Others cite lifecycle analyses showing EVs beat ICE even on fossil‑heavy grids, plus major gains in local air quality and their role as flexible load to enable more renewables.

Hybrids and Other Alternatives

• Parallel hybrids (e.g., Toyota‑style power‑split) are praised as highly efficient and mechanically simpler than conventional transmissions; series hybrids and range‑extender concepts spark debate on complexity vs benefit.
• CNG/biogas and LPG get some support as transitional fuels, but many see them as overtaken by battery buses.
• A few advocate streetcars/trams as the “real” long‑term solution where demand is high enough.

Broader Hydrogen & Aviation Tangents

• Hydrogen’s poor volumetric energy density, storage challenges, and pipeline embrittlement are repeatedly raised.
• Electric aviation is viewed by many as limited to trainers and short hops for now; some point to emerging eVTOL and regional projects as counterexamples, but consensus is that long‑haul remains fossil‑based for the foreseeable future.

Visa options for workers and founders

• Common employment options mentioned: H‑1B, O‑1, L‑1, E‑1/E‑2, TN (for Canadians/Mexicans), and E‑3 (for Australians). Choice depends heavily on nationality, qualifications, type of work, and whether you’re founding your own company.
• Founders can often incorporate and raise money while in visitor status (or on another visa), as long as they avoid “productive work for compensation.” Activities like fundraising, meetings, hiring, and incorporating are generally seen as permissible but the line is gray.
• For solo or cofounder‑founders, structures such as boards that can “fire” the founder are used to satisfy H‑1B/O‑1 employer–employee rules. E‑2 is highlighted as a good fit for Canadian and other treaty‑country founders who can invest and hire U.S. workers.
• Australians are often steered first to E‑3; Canadians to TN/E‑2/O‑1; experienced scientists and executives to O‑1 or EB‑1 paths.

Working, side projects, and digital nomads

• On most work visas (H‑1B, TN, E‑3), you’re only authorized to work for the sponsoring employer. Side consulting, streaming, or active work in your own U.S. company is generally not allowed unless separately authorized.
• F‑1 students on OPT/STEM‑OPT can sometimes work for their own startup if structured correctly, but schools vary widely; lawyers often advise students before talking to DSOs.
• Short, incidental remote work for a foreign employer while visiting the U.S. (e.g., brief Zoom calls on a vacation) is described as tolerated if the trip is truly a visit, not de‑facto residence.

Green cards, backlogs, and status changes

• Indian EB‑2/EB‑3 backlogs are described as catastrophic: only ~7,500 visas/year per category versus huge demand, leading to projected waits of decades for many.
• Marriage‑based green cards are still relatively fast but expected to slow as in‑person interviews return.
• Reentry permits can let green‑card holders live abroad for up to ~5 years cumulatively, after which intent to reside in the U.S. is scrutinized.
• Laid‑off H‑1Bs are often advised to file B‑1/B‑2 or H‑4 changes of status to preserve the ability to transfer H‑1B later without re‑entering the lottery.

Denaturalization, First Amendment, and enforcement climate

• Commenters debate how broad denaturalization statutes really are: some emphasize aggressive interpretations of “material misrepresentation”; others cite Supreme Court precedent narrowing causality.
• There is clear anxiety that an administration could weaponize vague “good moral character” standards and past form errors to revoke citizenship or green cards, especially for politically disfavored groups.
• Several threads recount harsh CBP/ICE behavior at borders, preclearance, and interior checkpoints, including detention of Canadians and Europeans, with disagreement on how “extraordinarily unusual” these cases are versus a new normal.

Policy, fairness, and system design

• Some worry H‑1B is politically unpopular and may face only “tinkering” rather than structural reform despite economic reliance on foreign workers.
• Others push back on the “cheap labor” narrative for high‑end tech roles, saying serious employers compete on talent, not rock‑bottom wages.
• The immigration code is frequently compared to the U.S. tax code: complex, vague, and full of “trap doors.”
• Several expect AI tools to rapidly automate form‑filling, drafting, and evidentiary assembly, with lawyers focusing more on strategy, risk, and edge cases.

Platform support and iOS constraints

• Many notice Briar is Android-only and question lack of iOS and recent public updates.
• Several argue Android focus is rational given limited resources and Briar’s target audience.
• Technical explanations: iOS aggressively kills background apps and forbids the kind of persistent background networking Briar and Tor need; also no JIT for JVM-based code and no process forking for a separate Tor process.
• Some note that a few iOS apps can run in the background via specific APIs (audio, location), but this is seen as a narrow carve‑out, not a general solution for Briar‑style messaging.

Security model and cryptography

• Users like Briar’s strong threat model, Tor integration, and metadata minimization; it’s described as “insanely privacy focused.”
• There are questions whether Briar uses a double ratchet; docs claim forward secrecy but don’t clearly mention ratcheting.
• A side thread debates PGP vs modern protocols: critics call PGP outdated for messaging (no default forward secrecy), recommending Signal‑style ratchets instead; others highlight ongoing work to add forward secrecy to PGP.
• One commenter critiques reliance on “standard cryptographic primitives” and suggests nonstandard schemes; others push back, emphasizing public scrutiny and competitions over “homebrew” crypto.

P2P, mesh, and offline communication

• Briar’s ability to sync over Bluetooth, Wi‑Fi, and even SD cards is widely praised, especially for censorship, disasters, or no‑internet scenarios.
• Real‑world stories: it worked well as Bluetooth chat on a plane for some, poorly for others.
• Clarification: despite marketing language, Briar today is not a full mesh network; phones relay only within limited topologies, partly due to OS changes and DoS/metadata concerns.
• There’s an extended debate about whether large‑scale, relay‑based mesh over short‑range links can practically scale without flooding or routing problems.

Alternatives and ecosystem comparisons

• Comparisons include DeltaChat, Signal, Session, SimpleX, Ricochet, Cwtch, Secure Scuttlebutt, Firechat, Meshtastic, and Reticulum.
• DeltaChat and Session get praise for usability and multi‑platform support, but are critiqued for PGP‑style crypto or lack of forward secrecy.
• Meshtastic and Reticulum are cited as more “network‑layer” approaches (LoRa, radio, multi‑interface overlay); some find Reticulum especially promising but worry it’s mostly a one‑person Python project.
• Android’s openness (F‑Droid, de‑Googled ROMs, sideloading) is viewed as aligning better with this ecosystem; iOS is seen as a hard wall for truly decentralized tools, though network effects of iOS still hurt adoption.

Usability, adoption, and missing features

• Adoption is perceived as low, limiting any P2P/mesh benefits; many peers simply don’t run Briar.
• Pain points: no multi‑device account, limited “one‑to‑many” broadcast features, forum UX (no edit/delete, weak threading), and QR‑only pairing.
• Others praise Briar’s simplicity and offline app‑sharing feature (Wi‑Fi hotspot / local APK) as a strong preparedness tool if installed in advance.

Legal and trust discussions

• Some worry about funding links (e.g., Open Technology Fund / US‑state‑related bodies), while others note many respected privacy projects share similar funding.
• On legality, commenters generally believe strong end‑to‑end crypto and P2P messaging remain legal in most “Western” jurisdictions, though vendors may face cooperation orders and, in the UK, compelled key disclosure.

Why Stoicism is (Again) Popular

• Several see Stoicism’s HN/tech boom as cyclical and driven by evangelists: startup culture (YC talks), self‑help marketers (Ryan Holiday, Tim Ferriss), and YouTube/podcast ecosystems.
• Others tie it to a broader trend of tech elites cycling fads: New Atheism → Stoicism → “trad” Christianity/Orthodoxy.

What Stoicism Is Supposed to Be

• Supporters frame it as a practical toolkit: focus on what you can control (your judgments, actions), accept what you can’t, and cultivate virtues (wisdom/prudence, courage/fortitude, justice, temperance).
• Many compare it to CBT/logotherapy: a way to manage anxiety, depression, conflict, and high‑stakes decision‑making.
• Multiple commenters stress Stoicism is not emotional numbness or passivity, but regulating reactions and acting justly regardless of outcome.

Class, Power, and the Status Quo

• Critics argue Stoicism tells the underclass to accept exploitation (“you can’t control working conditions”) and gives elites a moral gloss: whatever exists is “fated” and ultimately fine.
• Others reply this is a caricature: Stoics historically include both slaves (Epictetus) and emperors; the core ideas are class‑agnostic and can coexist with activism and justice.
• Some left‑wing commenters explicitly oppose Stoicism with Marxism, calling the former “serf ethics” and the latter “first philosophy of the proletariat.”

Wealth, Guilt, and Inequality

• Thread branches into whether the prosperous should feel guilt in an unequal world.
• One camp: wealth is mostly luck/privilege, and retaining excess while others suffer creates moral responsibility and often guilt.
• Opposing camp: no guilt is owed for inherited or earned wealth; only specific unjust actions matter. Stoicism can motivate charity and justice without paralyzing guilt.

Marcus Aurelius and Historical Debates

• Big fight over Marcus Aurelius: “good emperor” vs “tyrant, mass murderer” by modern standards.
• Some see Meditations as honest self‑therapy, sometimes bitter and depressive; others see it as a humane, fallible but valuable philosophical text.
• Several note that modern “pop Stoicism” often cherry‑picks and sanitizes the historical context and imperial violence.

Religion, Other Philosophies, and Misreadings

• Repeated pushback against the article’s claim that Stoicism (and then Christianity) teaches “everything is already perfect” and all evil is secretly good; many say that’s neither accurate Stoicism nor mainstream Christian theology.
• Comparisons surface with Buddhism, Hindu meditation, Epicureanism, Nietzsche’s critique, and Marxism; consensus is that Stoicism is best treated as one tool among many, not a complete moral‑political program.

Perception of “Up or Out” vs Reality

• Several commenters say “dead-end” roles are actually common; constant promotion pressure is more typical in big tech, high-growth startups, and some corporate environments.
• Others report that even in megacorps, no one is punished for not climbing, as long as they meet expectations; pressure often comes more from managers’ metrics and ambitious peers than from policy.
• Some organizations explicitly treat mid-levels as “up or out” but accept “senior” as a terminal, stable level.

Jobs and Sectors with Low Advancement Pressure

• Small / non-tech companies: Internal dev teams at utilities, manufacturers, law firms, and other non-tech-first businesses often use legacy systems, change slowly, and don’t push advancement.
• Government and adjacent: Federal/state/local agencies and some defense labs are seen as classic “do your job and stay forever” environments, especially on legacy systems.
  • Supporters emphasize extreme stability and long, deep technical tracks.
  • Critics note bureaucracy, mediocre pay, and say recent political changes and budget cuts have made some roles less secure.
• Finance / trading / Bloomberg: Many report flat structures where “Senior” or equivalent is effectively terminal and people sit in the same role for decades.
• Small/medium SaaS & private companies: Often happy to keep effective seniors in place long-term, with modest raises and little formal ladder movement.
• Contracting / consulting: As an IC contractor or senior consultant, there’s typically no promotion track—only rate changes.

High-Growth Environments and Startups

• VC-backed startups and PE roll-ups are described as highly unstable, with long hours, high risk, and strong advancement/impact expectations.
• “Up or out” cultures are framed as tools to open slots for climbers and ensure senior roles go to trusted high-performers, but can push out solid, content ICs.

Career Strategy and Personal Fit

• Many advise explicitly signaling contentment with an IC/senior role, seeking managers who value “bedrock” employees.
• Others suggest job-hopping between senior roles, or deliberately targeting companies where managers have held the same title for 10–20 years.