frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

SectorC: A C Compiler in 512 bytes

https://xorvoid.com/sectorc.html
71•valyala•3h ago•15 comments

Brookhaven Lab's RHIC concludes 25-year run with final collisions

https://www.hpcwire.com/off-the-wire/brookhaven-labs-rhic-concludes-25-year-run-with-final-collis...
23•gnufx•2h ago•10 comments

The F Word

http://muratbuffalo.blogspot.com/2026/02/friction.html
28•zdw•3d ago•2 comments

I write games in C (yes, C)

https://jonathanwhiting.com/writing/blog/games_in_c/
119•valyala•3h ago•91 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
82•mellosouls•6h ago•154 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
39•surprisetalk•3h ago•49 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
142•AlexeyBrin•9h ago•26 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
91•vinhnx•6h ago•11 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
848•klaussilveira•23h ago•255 comments

First Proof

https://arxiv.org/abs/2602.05192
62•samasblack•6h ago•51 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1087•xnx•1d ago•618 comments

Al Lowe on model trains, funny deaths and working with Disney

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
60•thelok•5h ago•9 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
90•onurkanbkrc•8h ago•5 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
228•jesperordrup•13h ago•80 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
512•theblazehen•3d ago•189 comments

We mourn our craft

https://nolanlawson.com/2026/02/07/we-mourn-our-craft/
318•ColinWright•2h ago•379 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
249•alainrk•8h ago•402 comments

Show HN: I saw this cool navigation reveal, so I made a simple HTML+CSS version

https://github.com/Momciloo/fun-with-clip-path
25•momciloo•3h ago•4 comments

France's homegrown open source online office suite

https://github.com/suitenumerique
607•nar001•7h ago•267 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
34•marklit•5d ago•6 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
177•1vuio0pswjnm7•10h ago•247 comments

Selection Rather Than Prediction

https://voratiq.com/blog/selection-rather-than-prediction/
11•languid-photic•3d ago•4 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
45•rbanffy•4d ago•9 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
123•videotopia•4d ago•37 comments

History and Timeline of the Proco Rat Pedal (2021)

https://web.archive.org/web/20211030011207/https://thejhsshow.com/articles/history-and-timeline-o...
20•brudgers•5d ago•4 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
91•speckx•4d ago•103 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
28•sandGorgon•2d ago•14 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
208•limoce•4d ago•115 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
283•isitcontent•23h ago•38 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
564•todsacerdoti•1d ago•275 comments
Open in hackernews

SWE-Grep and SWE-Grep-Mini: RL for Fast Multi-Turn Context Retrieval

https://cognition.ai/blog/swe-grep
97•meetpateltech•3mo ago

Comments

marstall•3mo ago
SWE-1 has been being booped up by WindSurf to me lately and I've been impressed - often (enough?) getting me the same answers as GPT5 etc., but almost instantly. Gotta say speed is nice.
swyx•3mo ago
nice, what does booped up mean? is this gen z lingo?
marstall•3mo ago
ha more like how i talk to my two year old. WindSurf's Cascade sidebar tool (which i use in RubyMine) has a stable of LLMs and it somewhat randomly switches the active one out from time to time. So I get a taste of what different ones are like, it's kind of cool.
tifa2up•3mo ago
Searched for 'hi' and it took 166s to return a response using this model: https://pasteboard.co/oB4VqVC5FGkl.png

Claude Code took 0.1s, Cursor CLI 19s

mgambati•3mo ago
If you ask a real question, then you might get real results.
silasalberti•3mo ago
hey I'm from the SWE-grep team - feel free to ask me any questions :)
daralthus•3mo ago
this would be useful outside of coding. could you release a benchmark so we can have more models tuned for this?
kwillets•3mo ago
Are you actually using grep here? How much data are you searching?
swyx•3mo ago
no - grep is just the closest analogy/use case that we have for it. if we end up releasing the CLI it should be as handy and nobrainer as using ripgrep

idk what you expect from a question about "how much data". its tool based search. its a lot.

kwillets•3mo ago
I'm just learning about agentic search so I'm a bit adrift.

One of my side projects is a full text index for pattern search, and I'm trying to understand how it might fit with that. You mention tool call overhead, but is that a significant part of the latency in the multi-turn scenario, or is it the coding agent being forced into a serial processing pattern?

swyx•3mo ago
hey sorryjust saw this. i do think its majority serial processing, BUT, parallel calling the same tools also gets issues that i honestly havent spent the time to dig into (something something locks and threading). all i know is ive been stuck in very very super slow/tool calls myself in Windsurf/other AI IDEs and that was a drag.

for another take on latency attribution see https://x.com/silasalberti/status/1979310181424206143

bluelightning2k•3mo ago
No question just wanted to say good job and thanks as a user. Same with deepwiki and codemaps.
llllm•3mo ago
Did you intend to answer them, or you just wanted the questions?
foodbaby•3mo ago
What base model did you use?
swyx•3mo ago
(coauthor) main charts/evals here https://x.com/cognition/status/1978867021669413252

you can try the https://playground.cognition.ai/ here

i wrote a longer explainer here https://x.com/swyx/status/1978874342743343254 but saving you the click

this was a perspective cut from the blogpost, but let me explain why subagents kill long context

Like you can spend $500m building 100 million context models, and they would be 1) slow, 2) expensive to use, 3) have huge context rot. O(n) is the lower bound.

Cog's approach is something you learn in day 1 of CS50 - divide and parallelize. Embeddings are too dumb, Agentic Search is too slow. So train limited-agency (max 4 turns), natively parallel tool calling (avg parallelism of 7-8, custom toolset) fast (2800tok/s) subagents to give the performance of Agentic Search under an acceptable "Flow Window" that feels immaterially slower than Embeddings.

The benefit of this is threefold:

- 8 ^ 4 toolcalls cover a very large code search space. can compound subagent calls if more needed.

- predictable cost & end to end latency

- subagent outputs "clean" contexts, free of context failure modes like context poisoning and context rot

we originally called this Rapid Agentic Search, to contrast with RAG. but Fast Context rolls off the tongue better.

-- Second perspective --

The Fundamental Equation of Coding Agents is:

Coding Agent Performance = Ability to Read the Right Files * Ability to Generate the Right Diffs

Fast Context is Cognition's first solution for the Read. As codebases get larger and and tasks get more complex, Reads get more important. the average production codebase first query in Cascade is >60% just searching and reading files.

But if this were just about speed, it might not be that exciting. I think there are unappreciated effects in performance as well when you have very good context. In other words:

Context Engineering is Actually Very Important. Too important for humans and hardcoded rules.

The swe-greps are the first dedicated context engineer agent models.

vessenes•3mo ago
Thanks for the summary. I noticed from the announcement you trained on parallel tool calling to save on serial round tripping. This is awesome.

Most LLM coding is so slow that you're permanently out of flow state, and in 'manager' state right now - I'm interested in a future where you've got enough fast low TTFT support that an engineer could maintain flow state and have sort of super power type productivity at the same time, and this tool makes me think of that.

That is, it looks fast enough to be used as a sort of sidebar info tool, as in "what you're coding might need / refer to these other parts of the codebase" -- effectively increasing an engineer's working memory. Super cool. And obviously useful for an AI engineer as well. Thanks for the writeup!

SafeDusk•3mo ago
Any plans to offer this as a tool/MCP server for other coding agents or is it going to be Windsurf exclusive?
swyx•3mo ago
we have other things in store that can be used by other coding agents, this one was tuned to use custom fast search tools that kinda wouldnt be useful in other agents
ntntnt•3mo ago
lol dead thread, cognition begging to grab some traction in this space.
kburman•3mo ago
I thought https://playground.cognition.ai/ was just returning some cached query results, but no, they’re actually spinning up real VMs and running live queries without any authentication or restrictions. That must be costing them a fortune.
groby_b•3mo ago
Currently, all queries are returning "We're under load and processing too many requests. Please try again later."

So that's how that is going ;)

awsanswers•3mo ago
LLM product managers: Show me what's in the context convenient to where I am prompting. Likely the user knowing and editing the precise context between requests will be a user task for a long time
breadislove•3mo ago
guys please release the benchmark or the benchmark code. like this is just "trust me bro"
swyx•3mo ago
well thats what the playground is for! playground.cognition.ai
breadislove•3mo ago
yeah but if people would like to double check the results it would be nice to have the actual benchmark. especially given that your playground is broken...

"We ran into an error processing your request. Please try again"

seanobannon•3mo ago
This link redirects to https://cognition.ai/blog/swe-grep now?
swyx•3mo ago
got a lot of traffic and was taken down temporarily for a couple reasons - team got it online again last night
bluelightning2k•3mo ago
This is really cool. Thank you for this. I'm a Windsurf user since launch and was VERY pleasantly surprised to see this pop up.

I also enjoyed the tech write-up. It's good to see REAL substantial engineering like this which is both highly impressive and highly productized.

bluelightning2k•3mo ago
Actually I do have a question! How come things as substantial as this were just released and not part of a "wave" ? I quite liked the waves way of doing things! Great work either way.
SafeDusk•3mo ago
Kickstarting an exploratory open version here https://github.com/aperoc/op-grep since it doesn't look like they will do it.
unturned3•3mo ago
This has very little resemblance of SWE-grep haha. At least fine-tune a small pre-trained LLM or something on a retrieval dataset. But no, this literally tries to train a small RNN from scratch to retrieve results given a natural language query...