Tuesday, 30 June 2026

Monday, 29 June 2026

Sunday, 28 June 2026

England heading for series defeat against NZ after chaotic day
England's cricketers are heading for a series defeat after a chaotic fourth day at Trent Bridge in the third Test against New Zealand, where the home side closed on 103-4, needing 270 runs to win and avoid a series defeat in Ben Stokes' last in charge, following his shock announcement that he'll be retiring from international cricket after the match.

from BBC News https://ift.tt/Gapi6cM

Saturday, 27 June 2026

New top story on Hacker News: Running a software jam in a world of slop
Running a software jam in a world of slop
6 by foxmoss | 2 comments on Hacker News.
I'm Fox. I'm a 16 year old, and I've been working mostly working on making projects I thought were cool & would do well on the internet over the last year. You can check out my other blog posts if you want to get a sense of what that means: < https://foxmoss.com/blog >. Hack Club noticed these projects and thought I would be well suited to run an event. This was my reaction, I wanted to make something that could encourage the same competition as well the feedback I get from places like HN and appreciate well made projects. Hack Club does a good job at throwing money at people who make projects, but a iffy job at rewarding hard work. I wanted to change that. Radish Jam < https://radish.hackclub.com/ > was my reaction to that, and this blog post goes through my thought processes in logistics. How something similar could be run again either by another Hack Clubber or an adult looking to run something for similar for adults :)

Friday, 26 June 2026

Thursday, 25 June 2026

New top story on Hacker News: Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion
39 by engomez | 10 comments on Hacker News.
Hi HN, Nick here. We’re launching OpenKnowledge ( https://ift.tt/SRIFvGO ), a “what you see is what you get” markdown editor that has direct integrations with Claude, Codex, and Cursor. Available as MacOS app or CLI. Fully free/local and OSS ( https://ift.tt/EZOjFUR ). We built this because we wanted a “Google docs” like experience for writing and sharing markdown files across our team. Obsidian is the best alternative we tried, but found it doesn’t have a true “what you see is what you get” UI and it didn’t integrate well with Claude/Codex outside of community plugins. So we built OpenKnowledge. It takes shape as: 1. A MacOS app with a file navigator, the WYSIWYG editor, and link explorer. 2. Integrations with the Claude, Codex, and Cursor desktop apps. The agents can open an OpenKnowledge editor within their embedded web browsers for a side-by-side experience. 3. Built-in mcps, skills, and RAG for LLM-wiki and “AI Second Brain” scenarios + spec writing 4. An embedded terminal and CLI for TUI-first users OSS stack includes: Tiptap/prosemirror, CodeMirror, yjs (CRDT), Electron (MacOS app), Orama, remark/rehype/micromark/mdast, @pierre/trees On the architecture side, the interesting eng. challenges included: 1. A pipeline to convert ProseMirror to markdown in a bidirectional lossless way. ProseMirror uses ASTs, which are not designed to have byte-fidelity. 2. A dual-observer CRDT to keep the ProseMirror and markdown state in-sync. The CRDT + git also power a collaborative experience that shows what Agents are doing in the markdown, have undo/redo, and version history. The “Share” and cloud-sync functionality are geared for team collaboration. They feel “no-code” but leverage git/GitHub under the hood, which also means data stays fully private. In that spirit, we made OpenKnowledge open source for anybody who’s curious or who’d like to contribute. We’re actively thinking about plugins/extensibility and what’s next. If you have suggestions or feedback, would love to hear it.

Wednesday, 24 June 2026

Monday, 22 June 2026

Sunday, 21 June 2026

Friday, 19 June 2026

Thursday, 18 June 2026

Wednesday, 17 June 2026

Monday, 15 June 2026

Sunday, 14 June 2026

Saturday, 13 June 2026

Thursday, 11 June 2026

Wednesday, 10 June 2026

Tuesday, 9 June 2026

Saturday, 6 June 2026

Friday, 5 June 2026

New top story on Hacker News: Inside FAISS: Billion-Scale Similarity Search
Inside FAISS: Billion-Scale Similarity Search
10 by tohms | 0 comments on Hacker News.
Author here. I wrote this as a visual companion to the 2017 FAISS paper ( https://ift.tt/uAwLvYV ), focused on the parts I found hardest to grok from text alone. The article covers a subset of what FAISS does, with the paper as the source of truth. NSG, FastScan, IMI are not covered here, they'll get their own articles. I'd be especially interested in feedback on: - the IVFPQ / IVFADC explanation, particularly the LUT reuse argument - whether the GPU part captures enough of the actual complexity Happy to answer questions.

Thursday, 4 June 2026

New top story on Hacker News: Show HN: Cost.dev (YC W21) – making agents cost-aware and cheaper to call
Show HN: Cost.dev (YC W21) – making agents cost-aware and cheaper to call
4 by akh | 0 comments on Hacker News.
We launched Infracost on HN five years ago ( https://ift.tt/Jljm7WO ) where our CLI generated cost estimates for infra-as-code, e.g. "this Terraform PR adds $400/mo". The idea was to shift cloud costs (FinOps) left, so engineers get visibility of costs before deployment and make better decisions. Earlier this year we started seeing agent traffic in our logs and it looked like coding agents were calling our CLI. But that CLI wasn't designed with coding agents in mind. We went down a philosophical rabbit hole to see if a CLI is even needed anymore given that Claude, Copilot et al. already follow best practices. Ultimately we decided to create a new CLI from the ground up with coding agents in mind for two reasons: 1. We optimized the CLI for agent callers and cut Claude's output token usage by up to 79% and API cost by up to 67% versus a bare-Claude baseline. We wrote a blog documenting our lessons on optimizing user token usage when designing a CLI, e.g. using predicate flags so the agent doesn't compose jq | python | wc pipelines, output format that strips JSON's redundant field names. The blog is here: https://ift.tt/JhsT0ku... 2. With cloud costs, precision matters. Telling a coding agent "make this Terraform cost-optimized" can be expensive and lossy. You burn tokens loading code and policy context into every conversation. Your agent could make up a price and you wouldn't know because it's difficult to verify that across the ~10M price points that AWS, Azure and Google have. The CLI runs static analysis on the code, uses the latest prices from cloud vendors, and passes that context to the coding agent. So that's what we're launching today - Cost.dev: https://cost.dev/ . - It runs locally. Your code never leaves your machine, you get a fast feedback loop, and you're not burning API calls per character when you want to fetch prices. - The CLI does the deterministic work. Fetching price points, scanning the code, validating fixes. The coding agent does the natural-language part. You don't have to trust the LLM to remember the rules, and can verify it called the right CLI command. - It provides a consistent rule layer across every tool you use. Get cost estimates in your IDE and your coding agent with a single install. We support Claude Code, GitHub Copilot, Cursor, Windsurf, OpenAI Codex, Gemini CLI, as well as IDEs like VS Code and JetBrains Before we keep building more in that direction, I want to sanity-check with HN: is "agents writing IaC in prod" actually a thing yet, or am I betting on a future that's still a year out? I know software developers are using coding agents heavily, but are platform/infra folks doing that for prod too? Also, if you have any feedback on Cost.dev, I'd love to hear it!

Wednesday, 3 June 2026

Tuesday, 2 June 2026

Monday, 1 June 2026