MurphyA/hacker-news huggingface dataset:
by hrmtst93837 | 2026-03-09 19:17:08+00:00
I think people pick new tooling not because k8s lacks horsepower, but because running per-user filesystem-backed agents on k8s forces you to build and maintain a surprising amount of glue code. Newer platforms put versioned mounts, local-first dev cycles, secure ephemeral runtimes, and opinionated deployment so teams can focus on agent logic instead of writing Helm charts and CSI gymnastics.

If you repurpose k8s with ephemeral volumes or emptyDir, a sidecar, you'll likely get predictable ops and avoid vendor lock-in. Expect more operator work, fragile debugging across PVCs and sidecars, and the need to invest in local emulation or a Firecracker or gVisor sandbox if you want anything like laptop parity.
by qarau | 2026-03-09 19:17:11+00:00
Over the past year I started doing most development with AI coding agents. The productivity gains were real, but I also started seeing a different class of problems appear.

The issue wasn’t the code generation itself. It was workflow discipline around the code.

AI-assisted sessions move fast and often run long. Over time we noticed recurring problems like:

- commits landing in the wrong branch

- session context docs drifting out of date

- resuming sessions with stale assumptions

- environment inconsistencies between machines

- forgetting validation steps before pushing

None of these are new problems, but AI makes them happen more frequently because iteration speed is so high.

We didn’t want to introduce another heavy dev platform, so we built a small toolkit that adds lightweight guardrails around normal Git workflows.

That toolkit became Agent Session Kit (ASK).

ASK installs a set of helpers around a repo including:

- Git hook templates
- session validation scripts
- environment smoke tests
- session documentation helpers
- workflow checks before commit/push

The goal is simple:

Turn workflow discipline into default behavior rather than relying on developer memory.

If something is off (wrong branch, missing session updates, failing checks), the workflow catches it before the change lands in the repo.

We originally built ASK as internal tooling while experimenting with AI-assisted development workflows and decided to open-source it so other teams don’t have to rebuild the same guardrails.

The project is intentionally simple:

- no servers
- no dashboards
- just scripts and Git integration

If you’re experimenting with AI coding agents or long interactive dev sessions, this might be useful.

Feedback and suggestions welcome.
by varispeed | 2026-03-09 19:17:22+00:00
The distinction you're missing is between economic activity and wealth retention. Foreign investment in UK data centres generates GDP (construction jobs, some ops roles) but the productive capital and its returns accrue to foreign shareholders. This is the classic GDP vs GNI gap - Ireland is the textbook example, enormous GDP inflated by multinationals, but GNI per capita significantly lower because profits repatriate.

If a fund invests £100bn expecting 15-20% IRR, they're extracting multiples of that over the asset lifetime. That's the whole point - they're not philanthropists. The UK tax take is thin because these structures are explicitly designed for tax efficiency.

The deeper issue is where in the value chain the UK is positioning itself. Hosting someone else's compute is the low-margin end - it's being a warehouse. The high-margin positions are fabrication and supply chain. Taiwan, South Korea, and now the US via CHIPS Act understand this. They're not inviting hyperscalers to build data centres and calling it industrial strategy - they're building domestic fab capacity because that's where durable value and strategic leverage sit.

The UK is offering itself as a site rather than building itself as a participant. Those are very different things.
by kumar_abhirup | 2026-03-09 19:17:24+00:00
Ha, I get why it looks that way from the CRM angle, but outreach is maybe 5% of what I actually use DenchClaw for day to day.

Yesterday I asked it to pull up all my meeting notes from last week, cross-reference them with my task list, and draft follow-ups. Before that I had it reorganize a messy folder of research PDFs into a structured workspace. I use it to build slides, write code (DenchClaw literally built DenchClaw), manage my calendar, search through old Notion pages I forgot existed.

The CRM part gets attention because that's what people asked for when we talked to power users. But the actual product is just "OpenClaw with a good UI, a file system, and DuckDB, running locally on your Mac." It does whatever you'd normally do on your computer. The browser is yours, the files are yours, the data never leaves your machine.

Think of it less as a sales tool and more as what happens when your entire Mac becomes programmable through natural language. The CRM is one app that runs on top of that. People are already using it for project management, research, personal knowledge bases, all kinds of stuff we didn't plan for.
by simonh | 2026-03-09 19:17:31+00:00
It wasn't necessary for it to happen eventually, but if eventually is several generations further down the line because it would have been painfully slow that's an important factor to consider.

Slower industrial and economic development would include huge human costs in terms of slower medical, social, economic and possibly also political development. It might have some beneficial effects as well though. I don't think it's an easy calculation to make.
by fractallyte | 2026-03-09 19:17:34+00:00
Regarding the issues of banking apps: if the EU is serious about tech sovereignty, it's up to members to mandate that banks allow their apps to run on Sailfish, or other alternative operating systems. It really is as simple as that.

(But whether any EU member is capable of rising to this (very shallow) challenge... well, I'm justifiably cynical.)
by nycticorax | 2026-03-09 19:17:43+00:00
The whole thing of calling controls "chrome" is basically a metaphor gone horribly awry. The term was coined in the 1990s because (at least on Windows) the "content" usually had a white background, and the controls usually had a gray background. But of course the use of the word "chrome" inevitably implies that this stuff (the controls) are like the chrome on a car: nonfunctional, inessential visual frippery. And so UI chrome must be bad, and something to eliminate. But of course this is nutty: The UI controls are what you use to manipulate the content! It's like calling the steering wheel and the pedals in a car "chrome" and deciding you need to deemphasize them so that the driver can 'focus on the road' or something. The controls are important! They are how you drive the car!
by arbuge | 2026-03-09 19:17:53+00:00
> Never used coal power: Albania, Cyprus, Estonia, Latvia, Lithuania, Luxembourg, Malta, Switzerland, Norway

Definitely wrong - Malta has used coal power for example. See for example:

https://www.ebsco.com/research-starters/power-and-energy/mal...

"In 1979, a second oil crisis, this time due to the Iranian Revolution, again brought into question Malta’s energy policy and made the government seek alternatives. Between 1982 and 1987, four stream turbines were installed at the Marsa Power Station. This strategy could have worked if the environmental and human health impacts of the coal used at the power station had not caused the local population to protest. In 1987, construction of a new power plant, at Delimara, started; the plant was commissioned in 1994. In the meantime, the Marsa Power Station continued to be improved, with new turbines added to eliminate the use of coal. On January 12, 1995, Malta became independent of coal but consequently became fully dependent on oil."
by jono_irwin | 2026-03-09 19:18:07+00:00
Good point, network dependency is a valid concern.

In practice these systems typically fetch data over a local, highly available network and aggressively cache anything that gets read. If that network path becomes unavailable, it usually indicates a much larger infrastructure issue since many other parts of the system rely on the same storage or registry endpoints.

So while it does introduce a different failure mode, in most production environments it ends up being a low practical risk compared to the startup latency improvements.

For us and our customers, the trade off is worth it.
by kumar_abhirup | 2026-03-09 19:18:13+00:00
I get why it looks that way from the CRM angle, but outreach is maybe 5% of what I actually use DenchClaw for day to day.

Yesterday I asked it to pull up all my meeting notes from last week, cross-reference them with my task list, and draft follow-ups. Before that I had it reorganize a messy folder of research PDFs into a structured workspace. I use it to build slides, write code (DenchClaw literally built DenchClaw), manage my calendar, search through old Notion pages I forgot existed.

The CRM part gets attention because that's what people asked for when we talked to power users. But the actual product is just "OpenClaw with a good UI, a file system, and DuckDB, running locally on your Mac." It does whatever you'd normally do on your computer. The browser is yours, the files are yours, the data never leaves your machine.

Think of it less as a sales tool and more as what happens when your entire Mac becomes programmable through natural language. The CRM is one app that runs on top of that. People are already using it for project management, research, personal knowledge bases, all kinds of stuff we didn't plan for.
by jacquesm | 2026-03-09 19:18:14+00:00
> What's with the excessively hostile attitude? That's more of a Reddit thing than a semi-professional discussion site that has this as a guideline:

>> Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

Which part was snarky, excessively hostile or unprofessional?
by jaapz | 2026-03-09 19:18:23+00:00
You're a bit naive if you think China is a peace loving country that wouldn't bomb the living shit out of any opposing nation if they could do so without recourse

Even now they are posturing in their "South-Chinese Sea", or as the Filipino's like to call it, the "West-Phillipine Sea". Also, Taiwan, Hong Kong...

And then we haven't even talked about how nice they are to their own citizens.

China is growing in strength and moving towards a new global world order, and the way Trump is fucking up US supremacy at the moment, China might well succeed.
by qarau | 2026-03-09 19:18:28+00:00
Hi HN,

We built Agent Session Kit (ASK) while experimenting with AI-assisted development workflows.

One thing we noticed is that AI coding sessions tend to be fast and bursty, which increases the chances of workflow drift.

Examples we ran into repeatedly:

• commits landing in the wrong branch
• session context docs drifting out of date
• resuming sessions with stale assumptions
• inconsistent environments between machines

ASK adds lightweight guardrails around normal Git workflows using hooks, validation scripts, and smoke tests.

The goal is to make good workflow habits automatic rather than relying on memory.

Curious to hear how others are managing workflow discipline when coding with AI agents.
by runarb | 2026-03-09 19:18:40+00:00
> Yeah you do. Compare the casualties and destruction in 19th century and 20th century wars.

Looking at Wikipedia's list of wars by death toll[0], it seems that people were capable of massive casualties and destruction without fossil fuels, too. Like the Taiping Rebellion in 1850–1864, with a death toll of 20–70 million. The Mongol invasions in 1206–1368, with a death range of 20–60 million, and the Three Kingdoms period in 184–280, with a death range of 34 million.

0: https://en.wikipedia.org/wiki/List_of_wars_by_death_toll
by buildsjets | 2026-03-09 19:18:43+00:00
You don't have a strong understanding of automotive engine design, do ya?

The engine is still 5.0L. The supercharger is 3.0L. And that is why it makes 810 horsepower.

(Looks sadly at the 1.3L Eaton supercharger on my workbench and feels inadequate)
by culi | 2026-03-09 19:18:47+00:00
> The Washington Post reported Wednesday that the US military in Iran has “leveraged the most advanced artificial intelligence it’s ever used in warfare, a tool that could be difficult for the Pentagon to give up even as it severs ties with the company that created it.”

> According to the Post, Palantir’s Maven Smart System—which contains Anthropic’s Claude AI language model—reportedly helped US commanders select 1,000 Iranian targets during the war’s first 24 hours alone.

They said it explicitly. AI being used to determine targets.
by MrBuddyCasino | 2026-03-09 19:18:49+00:00
„Math Inc is building the verification infrastructure for an AI-native economy. As AI systems generate millions of lines of code, mathematical proofs, and scientific designs, the bottleneck around scale becomes trust. The outputs are too large and too complex for humans to reliably audit, yet AI-generated code will increasingly power critical infrastructure, financial systems, cryptography, and autonomous machines.
Their thesis is simple: verification scales as a function of AI generation. Every dollar spent on AI-produced code creates a corresponding need to confirm that code is correct. So, Math Inc treats verification as core infrastructure: the layer that makes large-scale autonomy economically and socially viable.
Their first product is Gauss, an autoformalization agent.“
by lich_king | 2026-03-09 19:19:02+00:00
I don't think there's a simple answer. For example, someone recommended black ink on white paper, but it really depends on the composition of that ink. Inorganic pigments last forever, but the ink used in black sharpies actually fades pretty quickly.

Pencil definitely lasts if the paper is undisturbed. I have some paperwork that's 100+ years old and with legible pencil text. On the flip side, if the paper is handled a lot, the writing will gradually fade because graphite particles just sit on the surface and can flake off.

On some level, the medium is your main problem. Low-grade paper, especially if stored in suboptimal conditions (hot attic, moist crawlspace, etc), may start falling apart in 20 years or less. Thick, acid-free stock stored under controlled conditions can survive hundreds of years.
by pollorollo | 2026-03-09 19:19:05+00:00
While nuclear was cost competitive a decade ago, it turns out that is no longer the case [0].

As of 2025, the cheapest levelized cost of energy is solar ($58), onshore wind ($61), and gas combined ($78).

Although the data is US-based, European prices likely follow a similar pattern.

[0] https://www.lazard.com/media/5tlbhyla/lazards-lcoeplus-june-...
by rootusrootus | 2026-03-09 19:19:07+00:00
It can be confusing for non-enthusiasts, but the 3L measurement in this news is the blower, not the engine. This is the metric used for positive displacement blowers, in particular, like the Whipple. The engine is still 5.0L.

For a moment I was excited. I'd be a little bit interested to see someone come up with a smaller V8 -- more efficient, but still all the right noises! Still have higher pumping losses compared to fewer cylinders, but might be worth it even still.
by CrossVR | 2026-03-09 19:19:37+00:00
That money is better invested in providing affordable family housing. Even if IVF is available no one is going to actually have kids if you do nothing to make it economically sustainable to start a family.

Do we really want to rely on IVF to solve the fact that people can only afford a family home once they're well into their 40s? It's insanity if you ask me.
by wobfan | 2026-03-09 19:19:45+00:00
While I feel so too, I do actually think that objectively Catalina is a UX-side step up. Current displays have 16:9 or even 3:2. Putting less things in the top bar and more stuff in the sidebar, especially in something like Pages where your content does not even fill half of your display horizontally, I think it makes sense.
by yasserf | 2026-03-09 19:20:18+00:00
I have been working on pikku.dev, a typescript server library / framework that does most things and deploys in most places [1]

Been a project I was using for a few years now. Initially started off as express middleware with a few tools chained together to automate as much typing as possible which can run anywhere (similar to hono).

Around a year ago I decided to change the approach and write a layer to statically analyze the typescript code ontop of tsc and pull out as much meta as possible.

After that I went a little crazy and ultimately added wires to everything. HTTP, Websockets, Queues, Scheduled Jobs, etc. All totally agnostic (the core runtime is pretty tiny). So can run scheduled tasks on lambas / a cron job / pgadmin, deploy websockets serverless or local, run your queues again most queue provides, etc.

I then saw Vercels workflow runner and figured, well, I could try do better . Looked at other libraries out there and decided to include addons, which are pikku typescript packages that declare functions which can be automatically imported into your app and are responsible for their own service initialization. If your used to writing n8n plugins be awesome to hear what you think about this approach!

That sort of required me to create a console to view workflows (otherwise what's the point right?). And since everything is statically extracted during runtime we can pretty much just visualise the entire codebase. So all your functions, what permissions each have, etc etc. The idea behind the console is that it doesn't have an actual backend. You install an addon into your own codebase, permission it as you see fit and you point the console towards it. That means you have a unified permissions/auth system as everything else.

Figured the last part was creating an AI agent to wrap it all together. Which is almost there. Subagent flows, tools, approvals, ai middleware that can turn input and output into voices, its does a bit.

Ultimately the idea is you write a function once, and it can be consumed as an AI tool, a workflow step, by a http route, a cron job, a gateway (like whatsapp) (I liked openclaw approach so figured.. why not ).

A function is the source of truth, so is permissioned / authenticated. Been alot of heavy development since I'm building a 'BuildYourAgent' portal ontop that pretty much takes an openapi doc and turns it into an MCP server / hooks it up to an agent / gives you a CLI around it so it can integrate with all the crazy wild west approaches, while you know, still allowing us to maintain sanity and build servers that don't hallucinate and burn forests down.

Curious on thoughts! Bit of a rambling explanation. I hope the website does a better job! Lots of content helped with AI (I prefer speaking tech, but doesn't always transition well).

Also, looking for a potential cofounder to help balance that out! If your interested in potentially working together / adopting pikku feel free to leave a comment / ping me an email

[1] https://pikku.dev/
by PaulHoule | 2026-03-09 19:20:26+00:00
I was working with prototypical foundation models and having the exact same problem. My diagnosis wasn't quite the same, I think more radical gains could be had with a "stamp out unnecessary copies everywhere" policy but it looks like he did get through a bottleneck. The thing is he is happy with 3x speedup whereas I was looking for more of 300x except that, of course, if it takes you 20 min to sling containers and 5 min to do real work you'll probably be happy to 3x the container slinging.
by conductr | 2026-03-09 19:20:27+00:00
Yet, it's projected timeline seems to be extending

> Trump first said military action was expected to last "four to five weeks" but on 7 March White House spokeswoman Karoline Leavitt said the operations could last up to six weeks.

> A day later, Trump told Israeli newspaper The Times of Israel that a decision on when to end the war would be decided mutually with Israel.

> Israeli Prime Minister Benjamin Netanyahu said at the start of war that the campaign would "continue as long as it is needed".

https://www.bbc.com/news/articles/cx2dyz6p3weo
Code-review-graph: persistent code graph that cuts Claude Code token usage
by tirthkanani | 2026-03-09 19:20:28+00:00
Hi HN I'm Tirth. I built code-review-graph because I got tired of watching Claude Code re-read my entire codebase on every single task.

When you ask Claude Code to review a commit or add a feature, it reads files to understand the codebase. On a small project that's fine. On FastAPI (2,915 files) or Next.js (27,732 files) it scans thousands of files that have nothing to do with your change. You're paying for tokens that add zero value, and more noise makes the review worse.

code-review-graph builds a persistent structural map of your code using Tree-sitter. Every function, class, import, call, and inheritance relationship lives in a local SQLite database. When you edit a file or commit, it re-parses only the changed files and their dependants in under 2 seconds. Claude then queries the graph, finds what changed and what depends on it, and reads only the relevant files.

Benchmarks on production repos with real commits:

• httpx (125 files): 26.2x fewer tokens
• FastAPI (2,915 files): 8.1x fewer tokens
• Next.js (27,732 files): 6.0x fewer tokens on reviews, 49x on a live coding task
• Review quality: 8.8 vs 7.2 out of 10

Some technical details:

• SQLite WAL mode for concurrent reads, no external DB
• Qualified names (src/auth.py::AuthService.login) for collision-free node identity without scope resolution
• SHA-256 hash skip: files touched but not modified are skipped entirely
• Optional vector search stored as binary blobs in the same SQLite file, no separate vector DB
• NetworkX for BFS graph traversal with a cached directed graph that rebuilds on writes
• 12 languages via Tree-sitter: Python, TypeScript, JavaScript, Go, Rust, Java, C#, Ruby, Kotlin, Swift, PHP, C/C++

No cloud. No telemetry. No sign-ups. One SQLite file in .code-review-graph/ and that's it. PostEdit and PostGit hooks keep the graph current automatically. Your workflow doesn't change.

Setup takes about 30 seconds:

pip install code-review-graph
code-review-graph install

Or as a Claude Code plugin:
claude plugin add tirth8205/code-review-graph

MIT licence. Around 3,700 lines of typed Python with 770 lines of tests.

GitHub: https://github.com/tirth8205/code-review-graph
PyPI: https://pypi.org/project/code-review-graph/

Happy to answer questions about the incremental engine, the Tree-sitter integration, or the benchmark methodology.
AluminatiAI – per-job GPU cost tracking (Nvidia-smi shows watts, not dollars)
by AluminatiAi | 2026-03-09 19:21:07+00:00
With H100 clusters running $2–3/hr per GPU and training runs lasting hours or days, it's surprisingly hard to answer "what did that job actually cost?" nvidia-smi gives you instantaneous wattage. Your cloud bill gives you a monthly total. Neither tells you which experiment was the expensive one.

I built AluminatiAI to fill that gap. A lightweight Python agent (pynvml, ~0% CPU overhead, ~50MB RAM) samples power draw every 5 seconds and streams to a Next.js + Supabase dashboard. The dashboard converts watts → dollars per job, per GPU, per day. Works on A100, H100, RTX 3090/4090, and Google Colab.

Install is `pip install` + one env var. Under 2 minutes.

As H100 time gets more expensive and teams are running larger sweeps against frontier models, not knowing which run cost $800 is a real problem — not just a nice-to-have dashboard.

Open source: https://github.com/AgentMulder404/aluminatai-landing
Website: https://www.aluminatiai.com

Happy to answer questions about the sampling approach or the watt-to-dollar conversion logic.
by ramesh31 | 2026-03-09 19:21:21+00:00
>"Prices are only going up from here."

There may be some short term spikes, but $100/barrel is the hard limit now. We actually have effectively unlimited oil supplies now, but the economics of it don't converge until that price. At 100$, it becomes feasible for all of the more expensive fracking infrastructure to come back online, which puts a hard cap on the price.