who the hell made that demo video. i want to quickly see how it works not unskippable video of some person blabbering.

they had my attention. now they lost it.

criteria for hitting HN frontpage is generally whether it is interesting to people. That thought is likely the same thought a bunch of us are having at the moment.

It easily reaches the front-page for people with a following. I don't think many votes are necessary to get to the front page. And when there's some critical insight or leak.

Aside from that I've seen few posts on X that didn't follow the pattern, and were short lived at the top.

> On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.

You can just downvote anything you don't like and move along.

It works well enough for my use cases so I don't know what these folks are looking for. I have it configured to run everything in WSL sandbox so the blast radius is limited to the VM w/ the code.

Karpathy is a notable researcher and broader AI leader. Among many, many other things, he invented the term "vibecoding". He also recently posted his autoresearcher project, which is using a swarm of agents to optimize the LLM training and recently produced a training process that is the fastest to achieve GPT-2-level performance using a very small model.

That gives you a chatbox tacked onto an IDE, not exactly an agentic command center. Cursor gets close. But it’s hard to work on multiple things at once, or across multiple codebases.

That's great, he sounds like a great guy ... when he say something newsworthy (on X or anywhere else), it might deserve to be here.

But his random thoughts on X do not.

IMO, the answer is remote container environments like Codespaces, Coder, DevPod, etc. (dev containers)

We are moving into Codespaces now and it basically gives us an isolated full runtime env with Docker-in-Docker running Postgres. Developers had been trying various things to script worktrees, dealing with jank related to copying files into worktrees, managing git commands to orchestrate all of this, and managing port assignments.

Now with dev containers, we get a full end-to-end stack that we start up using Aspire (https://aspire.dev) which is fantastic because it's programmable.

All the ports get automatically routed and proxied and we get a fully functioning, isolated environment per PR; no fiddling with worktrees, easy to share with product team, etc.

A 64GB developer machine can realistically run ~2 of our full stacks (Pg, Elastic, Redis, Hatchet, Temporal, bunch of other supporting services). Frontend repo is 1.5m+ lines of TS (will grind small machines to a halt on this alone). In Codespaces? A developer could realistically work on 10 streams of changes at once and let product teams preview each; no hardware restrictions. No juggling worktrees, branches, git repo state.

I can code from any browser, from my phone, from a MacBook Neo, from a Chromebook. Switching between workstreams? Just switch tabs. Fiddling around with local worktrees for small, toy projects seems fine. But for anything sizable, future seems to be in dev containers.