0:00 / 0:54ai A hands-on guide to building a local LLM super-rig
James O’Beirne published a detailed GitHub guide to running local LLMs, ranging from a roughly $2k dual-RTX-3090 path for Qwen and local Whisper speech-to-text to a much more expensive four-RTX-PRO-6000 setup with 384GB of VRAM. The repo covers the hardware bill of materials, PCIe switch setup, BIOS and kernel tuning, GPU power limits, Docker runner configs, and measured GPU peer-to-peer performance. It matters because it gives unusually concrete guidance for people who want private, self-hosted AI — while also exposing how expensive and finicky “state of the art” local inference still is.
Discussion: Mixed — HN liked the detailed, practical nature of the build, especially for privacy, token freedom, local speech-to-text, and experimentation. But the dominant mood was caution: commenters questioned the real all-in cost, the quality hit from quantization and pruning, the economics versus subscriptions or cloud GPUs, and the maintenance burden of a high-power multi-GPU box. (Privacy and control are the strongest arguments for local inference, Sticker shock: the high-end build is closer to a serious workstation budget than a hobby purchase, Quantization, pruning, and context handling make “almost Opus” claims contentious)
0:00 / 0:53ai Mistral’s Leanstral 1.5 pushes open AI toward machine-checked proofs
Mistral released Leanstral 1.5, an Apache-2.0 model for Lean 4 proof engineering with 119B total parameters and 6B active parameters. The company reports major benchmark gains, including saturating miniF2F, solving 587 of 672 PutnamBench problems, and achieving stated state-of-the-art results on FATE-H and FATE-X. Mistral also says the model helped verify code properties and found 5 previously unknown bugs across 57 tested repositories, positioning formal verification as more practical for real software work.
Discussion: Mixed — HN is broadly interested in the release, especially the idea of a relatively small, open, specialized model that can help with Lean proof engineering. But the discussion is skeptical of some marketing claims: commenters challenged the bug-finding example, questioned comparisons against older models, and emphasized that formal verification still requires users to understand the properties being proved. (Enthusiasm for specialized, low-cost, open models, Skepticism about the bug-finding and fuzzing claims, Interest in practical formal verification workflows)
0:00 / 0:49ai AMD inference gets cheaper per token, but HN wants the watt bill
Wafer says it served GLM-5.2 on AMD MI355X hardware with MXFP4 quantization and reached 213 tokens per second in a single-stream test, plus 2,626 aggregate tokens per second per node at 2.4 requests per second on a long-context workload. The company argues this is about 80% of its measured B200 performance while using much cheaper AMD GPUs, and says the remaining gap is increasingly about framework support rather than an unbridgeable CUDA moat. The work involved choosing sglang, fixing speculative decoding support on ROCm, and tuning MoE kernel selection for GLM’s FP4 shapes rather than writing custom kernels.
Discussion: Mixed — Commenters were interested in AMD as a real alternative to scarce and expensive Nvidia capacity, but the thread was notably skeptical of the framing. The biggest objections were that performance-per-dollar is incomplete without power, cooling, and datacenter constraints, and that FP4 quantization may reduce model quality in ways benchmark tables do not fully capture. (Demand for performance-per-watt, not just performance-per-dollar, Skepticism about headline benchmarking and cherry-picked cost framing, Concern that FP4/MXFP4 quantization can degrade frontier-model quality)
0:00 / 1:10ai Satire hits a nerve on ChatGPT in academia
This 2025 satire resurfaced on HN today, presenting a fictional academic job candidate who claims discrimination after being barred from using ChatGPT during a chalk talk. The piece mocks total dependence on LLMs for research writing, grant drafting, and even explaining one’s own work, while framing the chalk talk as an outdated test of unaided cognition. It matters because HN readers saw the joke as uncomfortably close to real debates about AI use, academic incentives, and what expertise means when drafting and synthesis are increasingly automated.
Discussion: Mixed — HN mostly recognized the piece as satire and found it funny, but the discussion quickly turned serious. Commenters debated whether AI-heavy research and writing are already normal in academia, whether institutions are pretending otherwise, and whether unaided whiteboard-style evaluation still tests something essential. (Satire and Poe’s Law: many argued it needed to be labeled because the premise feels too plausible online, Anxiety about LLM dependence causing deskilling or loss of foundational knowledge, Criticism of academia’s output-and-citation incentives as encouraging tool-assisted gaming)
0:00 / 2:14science Stale meeting-room air gets the blame for bad decisions
A blog post argues that closed meeting rooms and home offices can quickly reach CO2 levels high enough to hurt decision-making, citing a personal reading above 2,000 ppm and studies from Lawrence Berkeley National Laboratory and Harvard that found cognitive-score declines as CO2 rose. The practical takeaway is simple: treat ventilation as part of the work environment you measure, and try opening a door or window before blaming the people in the room. The story resonated because it reframes air quality as a productivity and decision-quality issue, but commenters repeatedly questioned how strong the underlying evidence is at normal office levels.
Discussion: Mixed — HN was interested in measuring indoor air quality, but far from unanimous on the headline claim. Many commenters shared anecdotes from classrooms, offices, bedrooms, cars, and home offices where CO2 monitors changed their behavior; others pushed back hard on whether office-level CO2 has proven cognitive effects, citing replication concerns, submarines, calibration issues, and the gap between collecting data and fixing ventilation. (CO2 as a proxy for stale or poorly ventilated air, Calls for better HVAC, standards, and regulation rather than just personal sensors, Interest in phone, watch, car, classroom, and home-office CO2 monitoring)
0:00 / 1:13science Giant tropical trees may not be hydraulically maxed out after all
A new Science paper led by the University of Exeter and Cardiff University reports that very tall Dipterocarp trees in Malaysian Borneo compensate for height-related water-transport challenges. Studying trees from 7 to 71 meters, researchers found wider water-carrying vessels near the base and leaves better able to tolerate water stress, with no height-linked loss of growth during the 2023-2024 El Niño drought. The finding matters because the tallest 1% of trees store more than half of above-ground forest carbon, and some climate-impact models assume tall trees are especially drought-vulnerable because of weaker hydraulics.
Discussion: Mixed — HN was intrigued but cautious. Many commenters enjoyed the plant-physics angle and used the story as a springboard into botany, horticulture, and computational biology, while others pushed back on the headline and questioned how the finding squares with known limits on tree height. (curiosity about plant hydraulics, cavitation, and capillary action, skepticism about broad claims from trees measured up to 71 meters, debate over whether water transport or other factors limit maximum tree height)
0:00 / 0:48software ProseMirror’s creator plants a new rich-text editor
Wordgard is a new MIT-licensed JavaScript library for building in-browser rich-text editors, positioned as a structured, schema-based system rather than a free-form HTML editor. It advertises modular extensions, accessibility, right-to-left support, structured content like tables and nested lists, and collaborative editing. The HN discussion treats it as a serious successor or sibling to ProseMirror, but developers are asking what justifies the migration cost and how it will stack up against options like Lexical.
Discussion: Mixed — The thread is broadly impressed and respectful, especially toward Marijn Haverbeke’s track record and the site’s artwork, but the developer reaction is not uncritical. The main hesitation is practical: why switch from ProseMirror, TipTap, or Lexical, especially with no easy migration path and early mobile issues reported by commenters. (Admiration for ProseMirror and confidence in the author’s craft, Questions about the rationale and switching cost versus ProseMirror or Lexical, Interest in schema design, extension APIs, collaboration, and typed document representations)
0:00 / 0:46software A classic htop explainer gets a fresh HN run↻ from 2019
This 2019 explainer resurfaced on HN today, walking through what htop and top show on Linux and where those numbers come from. It explains uptime via /proc/uptime, load averages via /proc/loadavg, process IDs and process trees via /proc, and the important caveat that load average is not the same thing as CPU utilization because it also includes uninterruptible tasks. The value is practical: it turns familiar dashboard numbers into kernel-facing concepts that help people debug real machines instead of just staring at colored bars.
Discussion: Positive — The thread is broadly appreciative: readers liked the practical demystification of htop/top and shared their own defaults, shortcuts, and companion tools. The mood gets more mixed where commenters debate btop, memory metrics, and whether CPU-focused tools are becoming less central as GPU workloads grow. (Appreciation for clear Linux systems explanations, Personal htop/top configuration tips, Recommendations for btop, nmon, powertop, pgrep, and procs)
0:00 / 0:51software Odin’s Wikipedia deletion turns into a fight over what counts as notable
A Katamari64 post digs into Wikipedia’s deletion of the Odin programming language article through an Articles for Deletion process, where editors argued it lacked in-depth coverage from reliable independent sources. The controversy grew after Odin creator GingerBill and programmer Casey Muratori criticized Wikipedia’s standards, while Jimmy Wales said the deletion looked reasonable and asked for better sources. The story matters because it exposes a real tension between Wikipedia’s verifiability/notability model and how modern programming communities establish credibility online.
Discussion: Mixed — HN was split but leaned more sympathetic to Wikipedia’s constraints than the article’s outrage frame. Many commenters said Odin may be real and useful, but Wikipedia’s notability standard depends on independent secondary sources, not primary claims or community familiarity. Others argued Wikipedia’s sourcing rules are outdated for programming languages and specialist internet communities, and several users said deletion-heavy culture discourages contribution. (Wikipedia verifiability versus truth, whether programming-language notability needs domain-specific rules, primary sources and company claims not establishing notability)
0:00 / 0:50software A 16-year SQLite WAL bug gets the TLA+ treatment
SQLite recently fixed a long-standing Write-Ahead Log checkpointing bug that could lead to database corruption, though the Canonical authors say its real-world impact is very low and reproducing it is difficult. The dqlite team modeled SQLite WAL behavior in TLA+ to reason about the exact interleaving of appending and checkpointing, then compared that against how dqlite uses SQLite. The piece matters as a concrete example of formal methods helping explain rare storage/concurrency failures that are hard to trigger with ordinary tests.
Discussion: Mixed — The thread is mostly interested and positive about TLA+ and formal modeling, with the article author appearing to answer questions. The main substantive pushback is that the title may imply the SQLite bug was found by this work, while commenters read the post as a dqlite impact analysis after SQLite’s separate fix. There are also side discussions about TLA+ syntax, Lean, and whether this style of modeling could pair with LLM-generated code. (Interest in TLA+ as a practical formal-methods tool, Curiosity about how such a rare SQLite corruption bug was originally found, Concern that the title overstates what the article did)
0:00 / 1:09software Postgres as the workflow engine’s safety net
DBOS argues that durable workflow state should often live in the same Postgres database as application data, not merely in a separate workflow engine that happens to use Postgres. The key claim is that workflow checkpoints and application updates can then commit in the same transaction, eliminating failure windows for database-only workflow steps and simplifying idempotency. The post extends the idea to enqueueing workflows via a Postgres UDF in the same transaction as an application update, replacing some manual transactional-outbox plumbing while still leaving external side effects to asynchronous workers.
Discussion: Mixed — HN is engaged but cautious. Commenters broadly like the practical value of transactional outbox-style designs and “just use the database” simplicity, but many push back on any implication that this solves distributed atomicity in the general case; the dominant mood is technical debate rather than hype. (Outbox pattern turns atomicity failures into retry and idempotency problems, Skepticism about exactly-once semantics once external systems are involved, Support for keeping queues and workflow state inside the database for many workloads)
0:00 / 2:31security F-Droid blasts Google’s Android developer verification plan
F-Droid published a sharply worded attack on Google’s Android Developer Verification program, arguing that a system Google says is meant to fight malware will instead let Google block apps from developers who have not registered centrally. The post says rollout begins September 30 in Brazil, Indonesia, Singapore, and Thailand, with broader rollout expected later, and warns that F-Droid’s open-source distribution model may be incompatible with Google-controlled verification. The core issue is whether Android remains a user-controlled platform where sideloading is possible, or becomes a more centrally permissioned ecosystem.
Discussion: Negative — HN reaction is overwhelmingly hostile to Google’s Android Developer Verification, framing it as a loss of user control and a step toward centralized gatekeeping. The discussion is more mixed on F-Droid’s presentation: several commenters agree with the concern but think the “virus” and “malware vendor” rhetoric weakens the case. Much of the thread turns practical, with users debating whether GrapheneOS, mobile Linux, or other alternatives can realistically replace mainstream Android given banking, government ID, messaging, and app-compatibility constraints. (User ownership versus platform control, Fear that Google will become the sole arbiter of allowed Android software, Skepticism that developer verification meaningfully stops malware)
0:00 / 0:18security Pegasus Hit the Pegasus Investigators
Citizen Lab says it found high-confidence evidence that former MEP Stelios Kouloglou’s iPhone was infected with NSO Group’s Pegasus in October 2022 and March 2023, while he was serving on the European Parliament’s PEGA committee investigating spyware abuses. The infections overlapped with hearings, country-visit planning, draft-report work, and final deliberations, raising the possibility that non-public parliamentary communications were exposed. Citizen Lab does not attribute the hacking to a specific government, says it found no indication the Greek government was responsible, and notes overlap with a previously reported Pegasus campaign against Russian and Belarusian-speaking exiled journalists and activists in Europe.
Discussion: Negative — HN is disturbed and cynical: commenters see the timing as outrageous, but also debate whether this is just how state espionage works. A lot of the thread focuses on practical questions around Apple threat notifications, whether warnings could be missed or suppressed, how ordinary users can check phones, and the difficulty of attributing Pegasus activity to a specific government. (Alarm over spyware targeting a lawmaker investigating spyware, Skepticism about Apple’s delayed and possibly missable threat notifications, Debate over attribution, including Greece’s separate Predator scandal)
0:00 / 0:45security Ask Studio prompt injection could leak private YouTube titles
A researcher says YouTube Studio’s Ask Studio assistant can be influenced by ordinary video comments: a malicious comment can tell the model to prepend fake YouTube-style notices or include attacker-controlled links in its answer. The post claims the attack becomes more serious because suggested prompts automatically feed comments to the AI, and a proof of concept got the assistant to place a private video title into a URL parameter if the creator clicked the link. Google reportedly responded that this was not a security bug because it required social engineering, a classification the author disputes because the creator is interacting with YouTube’s own assistant, not knowingly trusting a random commenter.
Discussion: Mixed — HN is broadly concerned about the trust-boundary problem and critical of Google reportedly classifying it as social engineering rather than a security bug. A major side thread debates big-tech incentives, ownership, and security triage, while a smaller group questions the exploit’s practical impact and argues the bigger issue may be authority laundering rather than direct data theft. (prompt injection in AI tools, untrusted user-generated content, Google/YouTube security triage)
SearXNG is an open-source metasearch engine that aggregates results from multiple search services and databases while saying users are neither tracked nor profiled. The GitHub project is AGPL-licensed, Python-heavy, and has drawn significant adoption signals, with 33.3k stars and 3.1k forks shown in the repository snapshot. The HN discussion frames it less as a new product launch and more as a mature privacy tool finding new relevance as a search backend for self-hosted stacks and AI agents.
Discussion: Mixed — HN is broadly favorable toward SearXNG as a practical, self-hostable privacy layer for search, with several commenters saying they use it as a daily default. The enthusiasm is tempered by recurring complaints about slower or weaker results, provider rate limits, CAPTCHAs, and the inherent limits of metasearch privacy when queries still go out to upstream engines. A large part of the discussion also veers into adjacent personal-search and local-indexing tools, especially Hister, and into using SearXNG as a search backend for local AI agents. (Self-hosted privacy search as a daily driver, Tradeoff between privacy and result quality, Rate limits, CAPTCHAs, and provider blocking)
0:00 / 0:57security Claude Code bug report sparks session-leak worries
A GitHub issue on Anthropic’s Claude Code alleges a possible session or cache mix-up: while authenticated to an Enterprise ZDR workspace, the agent suddenly asked what kind of bricks the user wanted for a Minecraft temple and recapped that it was building one. The reporter notes an unusual local setup involving a .claude directory and work in a different directory, but says that does not explain a Minecraft-related prompt leaking into the session. On HN, a commenter identifying themselves as from the Claude Code team said they are confident it is a hallucination but are investigating.
Discussion: Mixed — The thread is uneasy but not convinced there was an actual data leak. Many commenters argue the Minecraft behavior could be a long-context hallucination or context contamination, while others say any apparent cross-session response in an enterprise ZDR product deserves a serious postmortem-level investigation. (enterprise data isolation concerns, hallucination versus infrastructure failure, long-context and project-memory fragility)
0:00 / 2:10hardware Valve open-sources a DIY e-ink faceplate for the Steam Machine
Valve has published the files and instructions for a Steam Machine front e-ink display accessory, now called the “Inkterface,” under the MIT license on its GitLab. Valve is not selling the display itself, but the project documents parts such as an Adafruit ESP32 Feather, an eInk Breakout Friend, and a 5.83-inch monochrome e-ink panel, so users or accessory makers can build one. The move matters because it turns a teased hardware feature into an open modding opportunity, and could encourage vendors to offer prebuilt versions if demand is there.
Discussion: Positive — The discussion is broadly pleased with Valve making an optional hardware add-on open and hackable instead of locking it down. Commenters also dig into practical details: the Adafruit panel, ESP32/Bluetooth approach, e-ink refresh behavior, airflow and reliability concerns, and whether third-party vendors will ship finished versions. (Praise for Valve’s openness and community-friendly hardware posture, Interest in DIY and third-party accessory ecosystems, Technical discussion of e-ink refresh rates, partial updates, and maintenance cycles)
0:00 / 2:21hardware CarPlay is becoming a car-buying dealbreaker
Casey Liss argues that Rivian’s refusal to support CarPlay is misguided, responding to Rivian software chief Wassym Bensaid’s claim that screen-mirroring solutions take over every pixel in the car. Liss points out that standard CarPlay does not have to occupy the full display, distinguishes it from CarPlay Ultra, and says the key point is that CarPlay is optional: drivers can use Rivian’s native UI if they prefer. The broader issue is whether automakers should control the in-car software experience, or offer phone-based interfaces that many buyers now treat as a baseline feature.
Discussion: Mixed — The HN thread leans pro-CarPlay and broadly agrees that optional phone projection is valuable, especially for consistency, rentals, navigation, media, and keeping older cars feeling current. But there is a sizable countercurrent from Tesla and Rivian owners, phone-mount users, and people who dislike phone dependence or see CarPlay as a sign that car infotainment has failed. (CarPlay as table stakes for vehicle purchases, Consistency across makes, models, rentals, and drivers, Long car lifetimes versus fast-moving phone software)
0:00 / 0:48hardware Factories Are Just Rooms—and Kids Should Know It
Matt Webb describes visiting his child’s school to show seven-year-olds how his AI clock went from sketches and CAD to breadboards, PCBs, plastic parts, packaging, testing, and factory assembly in Shenzhen. His core argument is that manufacturing should not be presented as distant spectacle: everyday objects are invented, designed, and made by people, and children should see themselves as potential participants. The piece matters as a compact argument for early manufacturing literacy and for replacing awe with agency.
Discussion: Positive — HN mostly embraced the essay’s maker-education message, with many commenters sharing childhood memories of books, workshops, factories, and hands-on tinkering that made technology feel human-made and approachable. The pushback was pragmatic rather than hostile: several commenters noted that real factories, scaling, tooling, financing, regulation, and industrial complexity can make manufacturing far harder than the slogan suggests. (Demystifying manufacturing for children, Nostalgia for hands-on learning and books like The Way Things Work, Respect for factory work, jigs, assembly, process improvement, and shop-floor skills)
0:00 / 0:58hardware Starlink finds demand where African internet is hardest to build
The Economist reports that Africans are turning to Starlink because existing internet infrastructure is failing to meet demand, especially in places where terrain and distance make fiber or tower backhaul expensive. The article’s example is Ekiti state in south-western Nigeria, where officials say poor connectivity has hampered economic plans and the government’s own connection has improved with Starlink. The significance is that low-Earth-orbit satellite broadband is becoming a practical workaround for regions that mobile broadband and fixed-line networks have not served well.
Discussion: Mixed — HN was broadly impressed by Starlink’s usefulness in underserved and rural areas, with many commenters sharing anecdotes from rural America, Alaska, Japan, and remote travel. But the enthusiasm was tempered by debates over affordability, whether satellite is a substitute for fiber or 5G, and unease about Elon Musk, military uses, misinformation, and dependency on a private foreign network. (Rural and hard-to-reach connectivity, Leapfrogging missing infrastructure, Affordability and long-term competition with fiber or 5G)
0:00 / 2:58startups A startup parable about shipping the oven before it bakes
Weli.dev’s “Half-Baked Product” is a satirical startup story about a founder who raises money to build a smarter industrial oven, an engineer who wants to build the perfect version, and a sales motion that keeps promising features before the core product works reliably. The oven’s basic algorithm still burns bread and cakes, but the team gets pulled into enterprise customizations and novelty buttons because those promises help close deals and support fundraising projections. The piece lands because it turns familiar startup failure modes—oversized market slides, weak validation, sales-driven roadmaps, and mounting technical debt—into a simple product allegory.
Discussion: Positive — HN strongly liked the essay’s writing and found the startup dynamics painfully familiar. The mood was amused but uneasy: many commenters treated the oven story as an accurate allegory for VC-backed product drift, sales-led roadmaps, and unresolved core reliability problems. (Praise for the satire and storytelling, Founder ambition without domain expertise, Sales promises outrunning engineering reality)
0:00 / 1:00policy A campaign to keep local AI legal
Right to Intelligence is an advocacy site urging people to oppose laws that would require permission or licensing just to own, run, study, modify, or share local AI models. It argues that harmful uses like fraud, CSAM, cybercrime, harassment, and deepfakes should remain illegal, but that the tool itself should not be put behind a license. The issue matters because it draws a line between AI as a cloud service controlled by platforms and AI as general-purpose software people can run on their own devices; however, the extracted page does not identify the specific state bills behind its warning.
Discussion: Mixed — HN is broadly sympathetic to the idea that people should be able to run AI models locally, but the thread is skeptical and anxious. Commenters worry about regulatory capture, licensing framed around safety harms, and cloud lock-in, while others doubt such laws would pass or be enforceable given OEM and hardware-industry incentives. A recurring criticism is that the site’s claim about new state laws is not backed by specific bill citations in the visible content. (support for lawful local AI ownership and open models, fear of licensing regimes and regulatory capture, skepticism that bans are politically or technically enforceable)
0:00 / 2:22general PeerTube’s pitch: video without the platform lock-in
PeerTube is an AGPL-licensed, decentralized and federated video platform from Framasoft, positioned as an alternative to centralized services like YouTube, Dailymotion, and Vimeo. It supports federated discovery, following via the Fediverse and RSS, livestreaming, embeds, support links for creators, and load sharing through WebRTC peer-to-peer streaming plus instance-level caching. The significance is not a new feature drop so much as the recurring question it raises: can open federated infrastructure provide a viable video commons when the incumbent’s biggest advantages are audience, hosting scale, and monetization?
Discussion: Mixed — HN was broadly sympathetic to the idea of a federated, ad-free video web, but skeptical that it can compete with YouTube for professional creators. The dominant split was between commenters who see the lack of built-in monetization as a fatal creator-economy problem and others who see that same absence of ads and commercial incentives as the point. (creator monetization versus ad-free distribution, network effects and audience scarcity, nostalgia for early, amateur YouTube)
0:00 / 0:41general Costco’s low-tech logistics make it Amazon’s opposite
Phenomenal World argues that Costco is the “anti-Amazon”: instead of infinite assortment and fast home delivery, it uses a limited catalog, bulk in-person shopping, pallet-scale cross-docking, and very low overhead. The piece says that constraint is part of Costco’s value proposition: around 4,000 SKUs per warehouse, high membership renewal, fast-moving inventory, and a simpler logistics system that can support lower prices and relatively higher wages. It frames Amazon’s logistical sophistication as impressive but socially costly for everyday goods, while still acknowledging that fast delivery can be genuinely valuable for things like medicine and accessibility.
Discussion: Mixed — HN was broadly appreciative of Costco’s model, especially its curated selection and problem-avoiding simplicity, but commenters heavily challenged the article’s last-mile logistics argument. The main split was contextual: Costco looks elegant for suburban bulk shopping, while Amazon or delivery services may be more efficient for dense cities, remote workers, specialty items, or people without cars. (admiration for Costco’s constrained SKU model and buyer curation, skepticism that in-person bulk shopping is always more efficient than delivery, urban versus suburban retail logistics)
0:00 / 0:59general The case for learning something, even badly
Marginalia’s essay argues that adults can still learn practical skills—music, languages, drawing, typing, modeling, crafts—if they make space for short, consistent practice. Its core point is expectation-setting: early practice often feels bad, progress may happen between sessions and during sleep, and the goal is to get through the painful beginner phase into useful mediocrity. The piece matters because it frames learning less as a productivity hack and more as a long-term way to build agency and a richer life.
Discussion: Mixed — HN largely liked the essay’s push toward deliberate, low-stakes learning, but the discussion quickly complicated the simple “replace scrolling with practice” framing. Commenters emphasized mental energy, anxiety, parenting interruptions, and the difference between consuming tutorials and actually practicing; several also pushed back on the idea that AI or translation tools make personal knowledge obsolete. (Time versus energy and uninterrupted attention, Learning by making mistakes, not just consuming material, Anxiety, burnout, and psychological readiness)