Jun 14Monday, June 15, 2026 · all days
1.Your ePub Is fine(andreklein.net)
618 points by sohkamyung 12 hours ago | 207 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Adobe's poor stewardship of RMSDK and Flash damaged the ecosystem and ePub tooling
  • Kobo's KePUB renderer and upgrade workflow offer a better reading experience than Adobe's pipeline
  • The ePub spec itself is problematic due to W3C tying it to living HTML standards, making validation messy
  • Recommendations for alternative devices and ecosystems like PineNote and PocketBook that avoid Adobe/locked-in tooling
  • Informational updates on RMSDK's sale to Wipro and Kobo rewriting their reader software
2.Even more batteries included with Emacs(karthinks.com)
213 points by signa11 9 hours ago | 40 comments | permalink
tl;dr: Third installment in a series highlighting lesser-known built-in Emacs features, requiring no packages and minimal learning curve. Highlights include `dictionary-tooltip-mode` for hover definitions, wildcard support in `find-file`/Dired, `compare-windows` as a lightweight diff, `kmacro-edit-lossage` for retroactively turning keystrokes into macros, `scroll-all-mode` for syncing window scrolls, `refill-mode` for actual auto-wrapping, and `emacs-lock-mode` to prevent buffer/Emacs termination. The author also shares Elisp snippets to extend `vc-diff` to work with backup files and improve other commands.
HN Discussion:
  • Emacs is stable in practice and its ecosystem is better than alternatives like Neovim
  • Blog posts won't help Emacs adoption; the real problem is out-of-the-box experience, not discoverability
  • Emacs breaks frequently on updates, making it impractical for getting actual work done
  • The real issue is package stability and combinations, not discoverability as the article implies
  • Appreciation for learning new built-in features highlighted in the post
3.Curl will not accept vulnerability reports during July 2026(daniel.haxx.se)
425 points by secret-noun 5 hours ago | 167 comments | permalink
tl;dr: The curl project is pausing vulnerability report submissions during July 2026 (dubbed the "summer of bliss"), with Hackerone closed and security emails ignored from July 1 to August 3. Maintainers cite burnout from a heavy influx of reports over recent months and want a real break. The 8.22.0 release is pushed to September 2, 2026, though GitHub issues/PRs remain open and paid support contracts are unaffected.
HN Discussion:
  • Praises the decision as a clever business model combining vacation and enterprise support incentives
  • Appreciates the human, refreshing stance maintainers are taking against burnout
  • ~Highlights the unhealthy dependence on unpaid maintainers with no backup as a systemic problem
  • Argues the security risk is minimal since curl is mature and urgent issues can be handled out-of-band
  • Criticizes the paid-contract carve-out as ineffective since unreported vulnerabilities still affect everyone
4.Show HN: Kage – Shadow any website to a single binary for offline viewing(github.com)
566 points by tamnd 18 hours ago | 111 comments | permalink
tl;dr: Kage is a Go tool that clones websites for offline viewing by rendering pages in headless Chrome, snapshotting the final DOM, stripping all JavaScript, and localizing CSS/images/fonts to disk. Mirrors can be served locally, packed into a standard ZIM archive (compatible with Kiwix), or bundled into a self-contained executable or double-clickable desktop app—optionally with a native WebView window instead of opening in a browser. Crawls are polite (respecting robots.txt), resumable, and deterministic.
HN Discussion:
  • Curiosity about the demo tooling reveals appreciation for author's related projects
  • ~Sees practical use cases like offline company wikis but wants serverless single-file output
  • Skeptical of marketing claims like 'no tracking, no surprises' in the README
  • ~Questions why a server is needed if output is static, suggesting browser-only opening
  • Suggests SingleFile as a more robust existing alternative
5.Bitsy(bitsy.org)
203 points by tosh 3 days ago | 6 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • Recommends similar alternative tool Playdate's Pulp for those who like Bitsy
  • ~Questions whether Bitsy games are real games or just interactive poems/stories
  • Nostalgic enthusiasm recalling Bitsy's popularity in past communities
  • Appreciates Bitsy games for their refreshing yet retro aesthetic
  • ~Found Bitsy fun but limiting for larger projects with more text or features
6.Firewood Splitting Simulator(screen.toys)
834 points by memalign 5 days ago | 242 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Simulator lacks realism compared to actual firewood splitting experience
  • It's meant as mindless fun, not a serious simulator
  • ~Real firewood splitting is meditative, satisfying exercise worth trying IRL
  • Appreciation for visual/audio details and design choices in the toy
  • Technical engagement through automation scripts or related tangents
7.Rio de Janeiro's "homegrown" LLM appears to be a merge of an existing model(github.com)
355 points by unrvl22 20 hours ago | 189 comments | permalink
tl;dr: Rio de Janeiro's IplanRIO claims its Rio-3.5-Open-397B is an original homegrown LLM, but Nex-AGI provides evidence it's actually a static element-wise weight merge (~60% Nex, 40% Qwen3.5-397B-A17B base) with no apparent additional training. When the hardcoded system prompt is stripped, the model identifies itself as "Nex" 79% of the time and reproduces Nex-AGI's backstory verbatim, while tensor-level analysis confirms a uniform 0.6/0.4 blend across all 60 layers.
HN Discussion:
  • ~Offers an alternative explanation that the merge was intentional and undisclosed distillation was the missing piece
  • Marvels at the technical robustness of deep learning models surviving linear weight blending
  • Confirms and summarizes the article's findings about the undisclosed merge
  • Dismisses the issue, suggesting similar practices are rewarded elsewhere without scrutiny
  • Agrees this undermines trust and calls for better provenance and transparency standards
8.Ask HN: What are you working on? (June 2026)
238 points by david927 19 hours ago | 866 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • Indie game developers sharing progress and struggles with visibility/marketing
  • Developers building productivity tools and APIs to solve personal or business pain points
  • Hobbyists exploring hardware, PCB design, and physical maker projects
  • Developers creating new programming languages and developer tooling
  • Creators building community-oriented projects like maker spaces and open datasets
9.Formal methods and the future of programming(blog.janestreet.com)
276 points by eatonphil 23 hours ago | 95 comments | permalink
tl;dr: Jane Street, long skeptical of formal methods due to their high cost (e.g., seL4 required 25 person-years to verify 8,700 lines of C), is now building a team to pursue them because agentic coding has shifted the cost/benefit calculus. LLMs lower the barrier to writing proofs, while simultaneously increasing the need for verification of AI-generated code and benefiting from the strong feedback signals formal methods provide. Jane Street believes its control over OxCaml and its receptive user base position it well to make formal methods as pervasive as type systems.
HN Discussion:
  • Language design's hard problem is adoption, and AI agents bypass this resistance, validating the article's thesis
  • Personal experience confirms LLMs are surprisingly effective at completing formal proofs in tools like Coq/Lean
  • Expressive type systems combined with AI agents prevent quality degradation and test sprawl
  • Formal specs are just restating implementation/tests and suffer from the same bugs, offering limited value
  • Formal methods only work where postulates map cleanly to the domain, limiting applicability outside deterministic algorithms
10.Windows 11 users are tired of MS account requirements creeping into everything(windowscentral.com)
364 points by josephcsible 14 hours ago | 247 comments | permalink
tl;dr: Windows 11 users continue to push back against Microsoft's removal of the local account option during OOBE setup, arguing that workarounds like Rufus miss the point—they want Microsoft to restore user choice. The requirement ties into security features like BitLocker, where recovery keys are stored in the MS account, but many users don't realize this until they're locked out. Despite internal pushback from employees like VP Scott Hanselman and Microsoft's "Windows K2" trust-rebuilding initiative, the company hasn't committed to restoring a straightforward local account option.
HN Discussion:
  • Sticking with Windows 10 as it's now stable and less invasive than Windows 11
  • Abandoning Windows entirely for Linux or macOS due to these issues
  • Account requirement creates dangerous data lock-in risk via BitLocker
  • Personal horror story confirming the account entanglement problems described
  • Windows 11 actually works well after some tweaking, no major complaints
11.Write for One Person(wizardzines.com)
234 points by evakhoury 2 days ago | 71 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Writing for oneself as the single audience is fulfilling and authentic
  • Tailoring content to a specific individual or persona produces better writing/talks
  • Famous authors like Vonnegut and C.S. Lewis endorse this same principle
  • ~Writing for one person should be balanced with accessibility aids like links and expanded acronyms
  • Persona-based design/writing can be misguided when it ignores practical user needs
12.How to earn a billion dollars(paulgraham.com)
643 points by kingstoned 23 hours ago | 1652 comments | permalink
tl;dr: Paul Graham argues that becoming a billionaire through startups doesn't require exploitation, just exponential growth: a startup growing 15% monthly will be worth ~4,384x more in five years, making founders billionaires without cheating. The key is building something users love enough to tell their friends about, which is best achieved by young founders making things they and their friends want, often via side projects rather than deliberate idea hunting. The two variables that matter are growth rate (driven by user love) and duration (driven by market size)—neither of which cheating can meaningfully affect.
HN Discussion:
  • Critics are unfairly negative and ideological; startups creating jobs is preferable to alternatives
  • PG is out of touch with reality due to decades of wealth and isolation from material concerns
  • Sustained exponential growth rates assumed by PG are mathematically unrealistic in practice
  • PG ignores what 'earning' actually means and disregards luck, inheritance, and economic rent
  • Billionaire wealth inherently requires exploiting employees or causing societal harm regardless of founder intentions
13.I indexed 669 GB of my GoPro videos using my M1 Max computer and local ML models
373 points by iliashad 20 hours ago | 95 comments | permalink
tl;dr: The author built a local pipeline to index 628 GoPro cycling videos (669 GB, 15+ hours) on an M1 Max using open-source ML models, enabling semantic search for interesting moments without cloud services. Matching clips can be sent directly to a DaVinci Resolve timeline for editing. The post includes detailed metrics on processing performance and indexing results.
HN Discussion:
  • Similar projects have been done, sharing related work and validating the approach
  • Curious about technical implementation details like models used and costs
  • Excited about local ML for indexing personal media collections generally
  • DaVinci already offers built-in AI indexing, reducing novelty of this work
  • ~Processing time/scale concerns suggest cloud GPUs may be more practical
14.Lisp's Influence on Ruby(blog.tacoda.dev)
240 points by tacoda 3 days ago | 74 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Article inspired curiosity to try Ruby over other languages like Python
  • Ruby's joyful design qualities are indeed attributable to Lisp influence
  • ~Listed features aren't uniquely Lispy anymore; callcc is the real Lisp inheritance
  • ~Functional chaining in Ruby is actually more readable than traditional Lisp style
  • Influence is indirect, coming via Smalltalk and Perl rather than directly from Lisp
15.The Birth and Death of JavaScript (2014)(destroyallsoftware.com)
225 points by subset 23 hours ago | 129 comments | permalink
tl;dr: Gary Bernhardt's 2014 PyCon talk is a sci-fi/comedy/serious presentation tracing JavaScript's history from 1995 to a speculative 2035, where asm.js and related technologies effectively replace the OS-level process boundary with a JavaScript VM sandbox. While candid about JavaScript's flaws, the talk argues its long-term impact on the industry is overwhelmingly positive.
HN Discussion:
  • Predictions about JS as a compilation target came true via WebAssembly and Electron
  • Bernhardt's predictions largely played out, awaiting full browser/WASM-based OS
  • ~WebAssembly isn't progressing fast enough to replace JS due to DOM limitations
  • Praise for Bernhardt's other work (Wat talk), tangential admiration
  • ~Ironic observation about JS ecosystem constantly reinventing itself via transpilation
16.Not everyone is using AI for everything(gabrielweinberg.com)
465 points by yegg 20 hours ago | 502 comments | permalink
tl;dr: Despite media narratives that "everyone is using AI for everything," data from Gallup, Microsoft, Datos, and others shows roughly one-third of Americans actively use AI, one-third use it occasionally, and one-third don't use it at all—with adoption stalling and negative sentiment rising. Concerns about job loss, privacy, and misinformation are driving deliberate avoidance, and AI's net positive societal rating sits at just +8%, comparable to social media. The author draws an analogy to meat consumption, suggesting companies should offer a spectrum of AI options rather than assuming universal adoption.
HN Discussion:
  • ~Defining 'using AI' is ambiguous, which complicates adoption statistics cited in the article
  • AI usage will grow invisibly by being baked into existing software, undermining the article's adoption numbers
  • AI is genuinely useful in some domains (coding) but underwhelming elsewhere, supporting selective adoption
  • ~AI will become ubiquitous due to laziness and convenience, not quality, contradicting deliberate avoidance narrative
  • Promised AI productivity gains haven't materialized, reinforcing skepticism about universal adoption
17.Linux 7.1(lore.kernel.org)
295 points by berlianta 19 hours ago | 112 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • Excitement about specific technical improvements like WiFi fixes and new NTFS driver
  • Approval of removing obsolete code to reduce AI-generated bug report noise
  • Skepticism that the version number bump is meaningful or noteworthy
  • Anticipation about when the release will reach distributions like Arch and Debian
  • Curiosity about AI's role in kernel development
18.GLM 5.2 Is Out(twitter.com)
749 points by aloknnikhil 1 day ago | 473 comments | permalink
tl;dr: Zhipu has released GLM-5.2, its most capable open-source model to date, featuring a 1M context window and strong performance on long-horizon agent tasks and coding. The announcement explicitly frames the release as a response to recent restrictions on frontier models, positioning open-source AI as essential to global AGI development. It launches tonight for GLM Coding Plan users (Lite/Pro/Max), with API access coming next week.
HN Discussion:
  • Open-source Chinese models are vital counterweight to US restrictions on frontier models
  • Open weights threaten closed labs' business models through price competition and distillation
  • ~Release was rushed to capitalize on Fable/Mythos drama, lacking proper benchmarks and documentation
  • Curious about practical workflow integration and how it compares to existing coding tools
  • Hoping for smaller/flash variants suitable for local coding use
19.Every Frame Perfect(tonsky.me)
839 points by ravenical 2 days ago | 274 comments | permalink
tl;dr: Borrowing Wayland's "every frame is perfect" goal, the author argues UI quality should be judged by whether a screenshot at any moment—including mid-animation—still makes sense. Examples from Safari, Photos, YouTube, and Preview show common failures: desynchronized animations, snapping vs. tweening mismatches, and bizarre transition paths that betray underlying technical limitations. The takeaway: polish the in-between states, not just start and end, because sloppy animations erode user trust.
HN Discussion:
  • Animations can legitimately use 'wrong' frames like smear frames since motion perception differs from static viewing
  • The article's premise is weakly argued and the 'every frame perfect' maxim is untenable
  • ~Latency matters more than animation polish; animations should be minimized or skipped
  • ~Article would be stronger with positive examples or solutions to illustrate the ideal
  • Agrees UI quality has regressed and polished in-between states matter
20.Pac-Man, but you're the ghost(garrit.xyz)
205 points by mindracer 1 day ago | 80 comments | permalink
tl;dr: A developer built an inverted Pac-Man game where you play as a ghost trying to catch an AI-controlled Pac-Man before he clears the maze. The twist preserves the original power pellet mechanic: when Pac-Man eats one, you become the prey and have to flee for a few seconds.
HN Discussion:
  • Reminiscing about similar inverted/multiplayer Pac-Man games from the past
  • Criticizing the game as poorly designed and vibe-coded with AI
  • Mobile swipe controls are broken or frustrating
  • ~Suggesting gameplay improvements like adding other ghosts for cornering
  • Pointing out exploits or trivial winning strategies due to weak AI