hackernews

1. Publish (On Your) Own Site, Syndicate Elsewhere Total comment counts : 23 Summary POSSE (Publish on Your Own Site, Syndicate Elsewhere) is posting on your own site first, then syndicating copies or links to third‑party silos (like Twitter or Facebook) with a link back to the original post via a permashortlink. It keeps readers on your site, emphasizes personal relationships over federation, and aims to boost adoption of federated ideas by prioritizing connections....

1. A website to destroy all websites Total comment counts : 8 Summary The article laments that the Internet has shifted from a vast, liberating space for learning, community, and self-expression into a profit-driven, attention-siphoning machine. Once rich with diverse blogs and genuine connection, it’s now dominated by doomscrolling, AI-ified short-form content, and “content creation” as commerce. Social networks have become clout-chasing platforms, and coding is driven by throughput rather than meaning....

1. I canceled my book deal Total comment counts : 43 Summary An Associate Teaching Professor at CMU recounts deciding to publish a technical book with a traditional publisher after blogging success. He chose a publisher over self-publishing, collaborating on a concept: a collection of self-contained tutorials on classic coding projects, including a revised “Let’s make a Teeny Tiny compiler” chapter and a finale of smaller projects. The contract required a detailed proposal, audience, and TOC; he projected 115,500–132,000 words (~350–400 pages) with 10–30 illustrations....

1. Everything as Code: How We Manage Our Company in One Monorepo Total comment counts : 17 Summary Kasava runs on a single monorepo where code, docs, marketing, blog posts, and even investor decks live as code. This enables AI-native development: AI tools access the actual code and verify claims across frontend, backend, and sites in one conversation and one commit. A single change, like updating pricing limits in billing-plans.json, propagates everywhere: backend enforces, frontend shows, marketing page updates, and docs reflect it, with AI validation....

1. Google is dead. Where do we go now? Total comment counts : 40 Summary An entertainment business owner reports a 50% revenue drop over three months. Despite years of Google Ads expertise, inflated budgets and weekly experimentation yielded zero returns, even after a Google holiday bonus. With funds depleted, they explore TikTok/Instagram ads, rely on a 50% returning-customer base, and started an email newsletter. Plans include physical marketing (free shows at a market, handing out cards) and new Magic Poi projects with ordered supplies....

1. Stepping down as Mockito maintainer after 10 years Total comment counts : 5 Summary After a decade as Mockito’s maintainer, I plan to step down around March 2026 to ensure a smooth transition. The catalyst was frustration with Mockito 5’s breaking shift to an agent, prompted by JVM 22’s security flag, which I supported in principle but felt discussed poorly and without solid build support. Volunteers under pressure led to burnout and a sense the community underestimated its societal impact....

1. How we lost communication to entertainment Total comment counts : 8 Summary Ploum argues that Pixelfed’s message-dropping harms Fediverse trust. Reactions split into two worldviews: older users who see ActivityPub as a human communication protocol prioritizing reliable message delivery, and Pixelfed supporters who view it as a content-delivery platform, often using multiple accounts. The piece critiques one-account-per-platform monopolies and marketing-driven interoperability. Manuel Moreale reframes: the Fediverse isn’t a pure communication network; ActivityPub builds social platforms to deliver content, i....

1. How uv got so fast Total comment counts : 19 Summary uv is a Python package installer that runs far faster than pip thanks to design choices, not just Rust. Key shifts: rely on packaging standards (PEP 518/658) to avoid executing setup.py; document what uv won’t do; no eggs, no pip.conf, no environment lookups, no bytecode compilation by default; virtual environments optional; stricter spec enforcement; ignore upper-bounds; first-index wins to prevent dependency confusion; focus on fast paths via HTTP metadata and range requests; parallel downloads; global cache with hardlinks; Python-free resolution using TOML and wheel metadata; PubGrub resolver instead of pip’s backtracking....

1. Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster Total comment counts : 22 Summary The author revisits tail-calling CPython performance across two platforms. On macOS AArch64 (XCode Clang), tail-calling interpreters are about 5% faster than computed-goto counterparts on pyperformance. On Windows x86-64 (experimental MSVC), tail-calling yields roughly 15–16% speedups, with a wide range (some benchmarks up to ~60–78% faster, a few slower). Results are experimental for MSVC, but largely positive overall; larger libraries like xDSL show ~14% gains....

1. Show HN: Minimalist editor that lives in browser, stores everything in the URL Total comment counts : 25 Summary Summary: The piece states that user feedback is read and taken seriously, and directs readers to documentation for available qualifiers. It repeatedly mentions loading errors with a prompt to reload the page. It also introduces a notes web app: a minimalist, browser-based text editor that stores everything in the URL hash, built with JavaScript and a heart emoji....