Jun 17Thursday, June 18, 2026 · all days
1.Midjourney Medical(midjourney.com)
950 points by ricochet11 11 hours ago | 660 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~Branding feels off; should be a separate company under an umbrella
  • Technology appears legitimate without obvious red flags, but resolution claims could mislead
  • ~Noble goal of cheap scans, but nothing substantiates the promises beyond renders
  • Cheap mass scanning could enable powerful AI-driven diagnostics across populations
  • Claims are absurdly overoptimistic; underlying tech has known limitations and won't replace MRI/CT
2.Local Qwen isn't a worse Opus, it's a different tool(blog.alexellis.io)
295 points by alphabettsy 10 hours ago | 154 comments | permalink
tl;dr: A founder running OpenFaaS spent ~$12K on an RTX 6000 Pro to run local Qwen 27B, and reports it's not "near-Opus" but is valuable for specific tasks: airgapped customer support diagnostics, telemetry analysis (which uncovered a 4-5x license under-reporting and paid for the card), and bounded maintenance work where data privacy matters. The main weakness is infinite loops and hallucinations on long-horizon unsupervised tasks, making it unsuitable as a Claude/Codex replacement for general coding. Key takeaways: match local models to scoped tasks, respect tuning parameters, use AGENTS.md, and don't trust them unattended.
HN Discussion:
  • Local models are different tools requiring different prompting techniques, like instruments
  • Article underestimates rapid improvement; too early to lock in conclusions about local model limitations
  • ~vLLM was wrongly dismissed; it actually fixes looping and outperforms llama.cpp in many cases
  • Article confirms local models are limited, expensive, and unsuitable for complex agentic work
  • Local models could serve as intermediaries (tool calling, anonymizing) feeding frontier models
3.Lore – Open source version control system designed for scalability(lore.org)
1178 points by regnerba 22 hours ago | 623 comments | permalink
tl;dr: Lore is an open-source version control system maintained by Epic Games, built to scale across massive datasets and large teams. It targets projects that mix code with large binary assets—such as games and entertainment—and is designed to serve both developers and artists.
HN Discussion:
  • Clarifies Lore competes with Perforce for gamedev, not Git for general software
  • Perforce is the entrenched but dated standard and badly needs a challenger like Lore
  • Lore isn't actually new, just newly open-sourced after use in UEFN
  • Skeptical that another data versioning system is needed when mature alternatives exist
  • Criticizes the 'open source' claim since the desktop client is binary-only
4.US holds off blacklisting DeepSeek, more than 100 firms deemed security risks(reuters.com)
481 points by giuliomagnifico 1 day ago | 524 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Users praise DeepSeek as affordable and effective, undermining the case for blacklisting
  • Blacklisting is hypocritical protectionism contradicting free market principles
  • US is becoming authoritarian like the China it claims to oppose
  • Entity List restrictions are largely ineffective given China's independence from US tech
  • Chinese open models are a strategic ploy to build dependence and sympathy in the West
5.A robot is sprinting towards you. Do you want it running on Claude or Grok?(openrouter.ai)
257 points by Usu 16 hours ago | 195 comments | permalink
tl;dr: An OpenRouter dev pitted 11 LLMs against each other in a 2D battle royale over 30 games; Grok 4.1 Fast won 43% of matches at $0.97/win, while Claude Sonnet 4.6 kept asking for truces and warning opponents of its location, winning only 5 games at 27x the cost. The experiment suggests "alignment tax" measurably hurts performance in adversarial zero-sum tasks, and that standard benchmarks poorly predict task-specific outcomes—cost-per-win rankings differ wildly from leaderboard rankings, and the model with the most kills (GPT 5.4) didn't win the most games.
HN Discussion:
  • Grok's lack of guardrails makes it more likely to complete tasks without refusal
  • Frontier-tier models are absurdly expensive and may not be financially viable at scale
  • Grok's pricing/model routing practices are deceptive and problematic
  • ~Cost-per-win/kill metrics for AI is a disturbing framing with real-world implications
  • Other models like DeepSeek prove benchmarks poorly predict real task performance
6.How we run Firecracker VMs inside EC2 and start browsers in less than 1s(browser-use.com)
292 points by gregpr07 1 day ago | 200 comments | permalink
tl;dr: Browser Use rebuilt its cloud browser infrastructure on Firecracker microVMs running nested inside regular EC2 (rather than bare-metal), cutting session start times to under 1s and costs from $0.06 to $0.02/browser-hour. Key optimizations included using 2MB memory pages and a custom userfaultfd handler to slash page faults 91x, dynamic vCPU pinning after Chromium launch, and a Chromium fork with real fingerprints enabling fully headless stealth (81% block-avoidance). Next up: snapshotting VMs after Chromium is already running to eliminate the remaining ~545ms startup cost.
HN Discussion:
  • ~Clarification from Unikraft that the migration wasn't due to technical limits but EC2 autoscaling support
  • Bot-scaling infrastructure makes captchas worse and harms legitimate users
  • Nested virtualization context missing - only recently possible on non-metal EC2
  • Sticking with Chromium is questionable; lighter alternatives like Lightpanda yield bigger wins
  • ~Simpler architectures (warm pools, AWS Lambda) could achieve similar results without the complexity
7.RFC 10008: The new HTTP Query Method(rfc-editor.org)
388 points by schappim 1 day ago | 160 comments | permalink
tl;dr: RFC 10008 defines QUERY, a new HTTP method that combines GET's safety and idempotency with POST's ability to send request bodies, solving the problem of queries too large to fit in a URL. Responses are cacheable (with the cache key derived from request content), and servers can optionally return Location or Content-Location headers pointing to equivalent GET-able resources for the query or its results. A companion Accept-Query response header advertises which media types a resource supports for queries.
HN Discussion:
  • Article lacks strong motivating example and body-as-cache-key feels problematic
  • Enthusiastic about practical applications like HTML forms, streaming APIs, and replacing POST /search
  • ~The QUERY name is confusing given 'query' already refers to HTTP requests generally
  • ~Concerns about ecosystem support like browser bookmarks needing to handle request parameters
  • Skepticism that QUERY was needed since GET with body already works in practice
8.Why thinking out loud with someone beats thinking alone(thesignalist.io)
292 points by kodesko 1 day ago | 130 comments | permalink
tl;dr: Thinking out loud with another person produces better reasoning than solo thought because verbalizing forces precision, and a listener's real-time reactions catch drift and surface hidden assumptions—a view supported by Mercier & Sperber's argumentative theory of reason, Vygotsky's ZPD, and Clark & Chalmers' extended mind. Remote work, async defaults, and LLMs erode this "dialogue dividend," and LLMs specifically tend toward sycophancy, agreeing with users rather than pushing back unless explicitly prompted (e.g., third-person reasoning), and even then only temporarily. Protect unscheduled conversation time and actively ask people and models to argue the other side.
HN Discussion:
  • ~The key benefit is verbalization/serialization forcing precision, not the listener themselves
  • Personal anecdotes confirm collaborative dialogue produces better ideas and solutions
  • Explaining to others forces covering foundational assumptions where errors hide
  • Article's framing about relationship-as-infrastructure undermines the piece's credibility
  • Thinking out loud isn't universally better; cultural differences matter
9.Volkswagen started blocking GrapheneOS users(discuss.grapheneos.org)
731 points by microtonal 22 hours ago | 430 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • VW is mismanaging its brand and losing customers through poor software decisions
  • VW's API lockdown kills useful community integrations and forces users into a bloated official app
  • Car data should be accessible locally rather than requiring manufacturer server access
  • Corporate liability concerns justify reliance on Google Play certification over open-source alternatives
  • This is part of a broader trend of companies blocking GrapheneOS and degrading user freedom
10.Show HN: An 8-bit live gamecast for baseball(ribbie.tv)
237 points by brownrout 20 hours ago | 121 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Enthusiastic praise with constructive feature suggestions for improvements
  • Loves the project and wants audio/sound to accompany the visuals
  • ~Critique of AI art usage, suggesting pixel fonts and deterministic methods instead
  • Cautionary tale about MLB's history of copyright lawsuits against similar projects
  • Curious about technical implementation or sharing similar scoreboard projects
11.Show HN: Inkwash, a watercolor sketching app and explanation(johnowhitaker.github.io)
234 points by Yenrabbit 4 days ago | 26 comments | permalink
tl;dr: Inkwash is a browser-based watercolor sketching app built as a single HTML file using WebGL2, simulating pigment, water, and paper via stacked float textures and Stam's Stable Fluids algorithm. It models effects like chromatographic bleed, edge darkening, granulation, and Beer-Lambert light absorption to mimic real watercolor behavior, with a "fix" command that bakes wet pigment into the paper for layering. Notably, the author built the entire app by prompting Claude (Anthropic's unreleased "Fable 5" model) without writing code themselves, and the accompanying explainer is largely AI-generated.
HN Discussion:
  • General praise for the app's visuals, writeup, and interactive explanation
  • Simulation physics are unrealistic with too much vorticity/flow compared to real watercolor
  • ~Suggestions for improvements like PWA support and mobile UI fixes
  • Appreciation for the single-file web app architecture as an exemplar of the pattern
  • Comparison to existing watercolor tools like Rebelle
12.Tesco moving 40k server workloads off VMware amid Broadcom's abusive conduct(arstechnica.com)
336 points by Bender 16 hours ago | 200 comments | permalink
tl;dr: Tesco is migrating 40,000 server workloads off VMware and suing Broadcom, VMware, and reseller Computacenter for at least £300 million, alleging "manifestly unfair and excessive" price hikes—reportedly 175% above expected pricing for VMware and 350% for mainframe software. Tesco rejected four Broadcom offers and is now contending with compatibility issues, as its new virtualization platform doesn't work with its existing Veeam and Zerto tools. The case is expected to reach UK court between late 2027 and early 2028, joining similar Broadcom disputes with AT&T (settled) and Siemens.
HN Discussion:
  • Broadcom's predatory acquisition and price-gouging business model is well-known and exploitative
  • Other customers share similar negative experiences with Broadcom's pricing and dishonesty
  • Now is a good time to migrate off VMware given established migration paths
  • Questioning technical details like which VMware alternative lacks backup compatibility
  • ~Broadcom is intentionally abandoning legacy customers to pivot to lucrative AI business
13.MicroUI – A tiny, portable, immediate-mode UI library written in ANSI C(github.com)
244 points by peter_d_sherman 1 day ago | 83 comments | permalink
tl;dr: MicroUI is a ~1100 SLOC ANSI C immediate-mode UI library that operates within a fixed-size memory region with no additional allocations. It provides standard controls (windows, buttons, sliders, textboxes, etc.) and a simple layout system, but doesn't render anything itself—users supply input and handle the emitted draw commands, making it compatible with any renderer capable of drawing rectangles and text. The project is intentionally minimal, so feature-additions PRs likely won't be merged, though it's designed for easy extension with custom controls.
HN Discussion:
  • Users share their own successful integrations and demos showcasing the library's minimalism and portability
  • ~The library is great but effectively abandonware with unresolved bugs
  • Pointing to related or alternative GUI libraries for different use cases
  • Lack of accessibility support makes it a non-serious toy project
  • Questioning what advantages it offers over established alternatives like Dear ImGui
14.GLM-5.2 is the new leading open weights model on Artificial Analysis(artificialanalysis.ai)
858 points by himata4113 1 day ago | 418 comments | permalink
tl;dr: Z.ai's GLM-5.2 (744B total / 40B active params, MIT license) tops Artificial Analysis's open weights leaderboard with an Intelligence Index of 51, beating MiniMax-M3 (44) and DeepSeek V4 Pro (44), with notable gains in scientific reasoning and a 1M token context window. It also leads open weights on GDPval-AA v2 (1524), roughly matching GPT-5.5. The tradeoff: it burns 43k output tokens per task (up from 26k in GLM-5.1), making it less token-efficient than peers despite sitting on the intelligence-vs-cost Pareto frontier at ~$0.46/task.
HN Discussion:
  • Model is impressive but reasoning/token efficiency is a concern matching the article's tradeoff point
  • GLM-5.2 is a massive disruption to closed-source providers at unprecedented prices
  • Benchmarks suggest GLM is not as cost-effective or capable as the article implies versus GPT-5.5
  • ~Lack of vision input is a notable limitation undermining its frontier status
  • Independent testing shows more modest gains than the leaderboard suggests
15.U.S. science is in chaos(scientificamerican.com)
835 points by presspot 1 day ago | 988 comments | permalink
tl;dr: The Trump administration's cuts via DOGE have gutted U.S. science funding: ~95,000 federal scientists have left, NIH and NSF are issuing far fewer grants, and projects like the AXIS space telescope died from staff losses and budget chaos rather than outright cancellation. Politically-driven filters now block research touching on DEI, structural racism, or foreign collaborations, breaking the post-WWII compact between government and academia and pushing researchers to consider leaving the country. Critics argue the shift reflects a Silicon Valley-influenced view that science should primarily generate commercial returns, which historical analysis suggests would have prevented roughly half of today's drugs from existing.
HN Discussion:
  • Personal accounts of scientists leaving the US or the field confirm the article's claims
  • Instability and chaos, not just funding cuts, are what's truly destroying research
  • The DEI framing in the article is wrong; removing DEI is depoliticizing, not politicizing science
  • The core issue is unconstitutional impoundment of congressionally-allocated funds
  • ~Chaos creates opportunity; the disruption isn't entirely negative for some labs
16.The founder's playbook: Building an AI-native startup(claude.com)
233 points by e2e4 1 day ago | 162 comments | permalink
tl;dr: Anthropic published a playbook for founders building AI-native startups, mapping the four startup stages (Idea, MVP, Launch, Scale) to AI-powered workflows using Claude products. It covers problem validation, avoiding technical debt in AI-generated codebases, measuring real product-market fit, and using agentic workflows to replace founder attention, with guidance on when to use Chat, Claude Cowork, or Claude Code at each stage.
HN Discussion:
  • Playbook is just marketing to sell Anthropic's tools, not genuine startup advice
  • Article trivializes founding a startup as a casual, formulaic process
  • It's not really AI-native; just using AI to build traditional apps
  • Anthropic lacks credibility giving security advice given their own practices
  • Claim that non-technical founders can now easily build software ignores that business skills matter more
17.Want your images back? That'll be $5(lutr.dev)
637 points by lutr 1 day ago | 265 comments | permalink
tl;dr: The author logged into their old Photobucket account hoping to recover childhood images, only to find them paywalled behind a $5/month subscription (a detail Photobucket conveniently obscured). After reluctantly paying, they discovered the account was actually empty — and the refund window had already lapsed by the time they noticed the fine print. The post blew up on Hacker News, nearly taking down their Vercel-hosted blog due to edge request limits.
HN Discussion:
  • Photobucket offers free data download if you close the account, no subscription needed
  • Pursue a chargeback since Photobucket misrepresented having user's photos
  • Users should take responsibility for archiving their own memories rather than blaming the service
  • This situation reinforces the case for self-hosting and against SaaS dependence
  • ~Critique of the author's technical choices like using Vercel for a personal blog
18.Running local models is good now(vickiboykis.com)
1540 points by jfb 1 day ago | 591 comments | permalink
tl;dr: Local LLMs have crossed a usability threshold, with GPT-OSS and Gemma 3 (referred to as "Gemma 4" in the post) enabling agentic coding workflows on a 64GB M2 Mac at roughly 75% of frontier model performance. The author runs Pi as an agent harness against LM Studio in a Docker sandbox, using it for refactoring, unit tests, and bootstrapping repos—though slow inference and small context windows still rule out production use.
HN Discussion:
  • Local models are still painful to run with quantization and memory tradeoffs lobotomizing them
  • Local models are genuinely preferable to frontier models for actual daily use
  • Rise of local models threatens the pricing power of frontier model providers
  • Local models are far behind frontier models and the article oversells their capabilities
  • ~Local models work well when paired with frontier planning or used for narrow, well-defined tasks
19.GrapheneOS has been ported to Android 17(discuss.grapheneos.org)
995 points by Cider9986 1 day ago | 581 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Satisfied GrapheneOS users sharing positive experiences and willingness to switch from stock Android
  • ~Limited Pixel availability worldwide gatekeeps access to GrapheneOS security
  • ~GrapheneOS has rough edges and app compatibility issues like banking and Strava
  • Questions about AI features in Android 17 and how they affect GrapheneOS
  • Pixel phones are valuable specifically because they support custom ROMs extending device life
20.AI demands more engineering discipline. Not less(charitydotwtf.substack.com)
390 points by BerislavLopac 22 hours ago | 196 comments | permalink
tl;dr: AI-generated code became roughly as good as a median engineer in late 2025, flipping the economics of software: code is now cheap and disposable, more like a cache of understanding than a durable asset. This makes traditional engineering discipline—observability, behavioral tests, evals in production, immutable/regenerable artifacts—more important, not less, since humans are the weakest link at validation but still essential for creativity, architecture, and defining specs. The author predicts 2026 will be a return to discipline, with massive payoffs for the small minority of teams that already work in tight feedback loops.
HN Discussion:
  • AI makes it harder to distinguish competent engineers from underperformers producing plausible-looking output
  • ~Reading AI-generated code is exhausting and breaks the productive feedback loop of manual coding
  • The article's key insight about code economics being inverted is being overlooked by commenters
  • Understanding systems requires human context and docs, reinforcing the article's discipline argument
  • The article ignores that sufficiently complete specs/models become the thing itself, undermining its premise