MurphyA/hacker-news huggingface dataset:
by ptx | 2026-03-09 10:26:30+00:00
But search engines are not a good interface when you already know what you want and need to specify it exactly.

See for example the new Windows start menu compared to the old-school run dialog – if I directly run "notepad", then I get always Notepad; but if I search for "notepad" then, after quite a bit of chugging and loading and layout shifting, I might get Notepad or I might get something from Bing or something entirely different at different times.
Show HN: VS Code Agent Kanban: Task Management for the AI-Assisted Developer
by gbro3n | 2026-03-09 10:28:08+00:00
Agent Kanban has 4 main features:

GitOps & team friendly kanban board integration inside VS Code
Structured plan / todo / implement via @kanban commands
Leverages your existing agent harness rather than trying to bundle a built in one
.md task format provides a permanent (editable) source of truth including considerations, decisions and actions, that is resistant to context rot
by asimovDev | 2026-03-09 10:29:04+00:00
looks fun

What kind of stuff is Visual Studio used for nowadays? I remember writing .NET Core using the 2018 I think version. The only person I know who writes C# and dotnet uses Rider since they are on Mac but I remember writing a take home in VS Code and the microsoft plugins were very sufficient as far as dev experience went

Am I naive in assuming that it's mainly people developing desktop applications for Windows that use Visual Studio? Do those of you who write C/C++ on windows also use it or do you go with a text editor + MinGW (or whatever is used for bash / gcc on windows) ?
by ppcvote | 2026-03-09 10:29:07+00:00
"Fair catch on both points.
The batch of replies: I had a list of expected questions and drafted answers beforehand. When I finally had time to respond, I posted them all at once. Not real-time typing — that's why the timing looks suspicious. Should've spaced them out.
On MRR: I dodged it. Honest answer — client project revenue is irregular (project-based, not subscription), so I don't track it as MRR. MindThread subscription revenue is early and small, I'm not comfortable putting a number on it publicly yet. What I can say: it covers my infra costs and Claude subscription with room left over. Not life-changing, but real
by lwansbrough | 2026-03-09 10:29:24+00:00
You realize how much work has gone into ensuring that didn't materialize in those 40 years, right? JCPOA... Stuxnet?

The Pentagon agrees that Iran is not officially pursuing nuclear weapons. However, there are CIA reports that indicated there may have been covert operations taking place that were exploring cruder nuclear weapons. I imagine that was the basis for the US bombing of Iran in 2025.
by yoz-y | 2026-03-09 10:29:41+00:00
I realized that there is no journaling program I like, so I wrote my own. Authoring is done purely by iOS shortcuts and is writer (the only thing I want is to create a new entry, or create a new entry with a photo and metadata from said photo)

Rendering is done by a go server. I wanted to learn go for quite a while and this is the perfect excuse.
by tpm | 2026-03-09 10:29:42+00:00
> China is using more coal, gas, and oil than ever.

Well, no. Coal peaked at 4.9 billion tonnes in 2024.

https://www.iea.org/reports/coal-2024/executive-summary
https://www.carbonbrief.org/analysis-coal-power-drops-in-chi...

> Oil use doubled from 2005 to 2025

yes, and gasoline production is trending down too:

https://www.mysteel.net/news/5109188-china-2025-gasoline-pro...
by backrun | 2026-03-09 10:30:33+00:00
F# hits a sweet spot that's hard to explain until you've used it: you get the conciseness of a scripting language but with a type system that catches errors before you run anything.

For automation specifically, the pipe operator (|>) makes data transformation chains read almost like pseudocode. Compare that to Bash where you're constantly context-switching between quoting rules and subshell behavior.

The thing that keeps me coming back is that F# scripts scale up. A quick .fsx file can grow into a proper project without rewriting anything — same language, same idioms. With Python you often hit a point where the "script" needs to become "real code" and there's a refactor involved.

The downside is real though: cold start on dotnet fsi is noticeable, and the ecosystem for quick one-liners isn't as mature as Python's. For anything touching data science or quick API calls, Python still wins on available libraries alone.

But for internal tooling, build scripts, and anything where correctness matters more than iteration speed — F# is underrated.
by sthlmb | 2026-03-09 10:30:40+00:00
Hmm, I'm not sure if I'm missing something but that 1st comment is what I'm doing. I have 3 different sized Deepseek R1 models (1.5, 8, 16) and they run on each board that can handle them and then the data is reported.

For the 2nd, the file I grabbed initially was https://github.com/geerlingguy/ai-benchmarks/blob/main/obenc... - which I now notice wasn't modified in his repository, so I can check that out, but either way, the same version has been tested across everything thus far.
by hrmtst93837 | 2026-03-09 10:31:56+00:00
In practice library authors must consider the editions used by downstream crates because public APIs cross crate boundaries. Even if a crate compiles under a single edition, exported APIs often avoid edition specific idioms that could cause friction for consumers compiled under older editions. This leads to a conservative design style where libraries effectively target the lowest common denominator of the ecosystem. The result is that authors informally maintain compatibility across editions even if the compiler technically allows them to ignore downstream edition choices.

Large Rust organizations often run mixed-edition workspaces because upgrading hundreds of crates simultaneously is impractical. Libraries in the workspace therefore interact across editions during migration periods. So while technically each crate chooses its edition, ecosystem reality introduces cross-edition friction.

Feature test macros in C and C++ primarily gate access to optional APIs or compiler capabilities. Rust editions can change language semantics rather than merely enabling features. Examples include changes to module path resolution, trait object syntax requirements such as dyn, or additions to the prelude. Semantic differences influence parsing, name resolution, and type checking in ways that exceed the scope of a conditional feature macro.

Tooling complexity is structurally different. Rust tools such as rustc, rust analyzer, rustfmt, and clippy must understand edition dependent grammar and semantics simultaneously. The tooling stack therefore contains logic branches for multiple language modes. In contrast, feature test macros generally affect conditional compilation paths inside user code but do not require parsers or analysis tools to support different core language semantics.

Rust promises permanent support for previous editions, which implies that compiler infrastructure must preserve older semantics indefinitely. Over time this creates a cumulative maintenance burden similar to maintaining compatibility with many historical language versions.
by alsetmusic | 2026-03-09 10:33:52+00:00
You’re right, yet at the same time you display that you are completely wrong. One party maintains the status quo (dems). The other advocates fascism (who? repups). We are not the same. You’re using a colloquium to pretend you know about politics.

I’m a Leftist and I want good things for all people. I don’t want to persecute my enemies. I don’t agree with you.
by vova_hn2 | 2026-03-09 10:33:55+00:00
Ask you IRL friends or colleagues from your job "hey, do you happen to have an HN account?"

If the discussion is related to a public project, like in the examples in this comment: https://news.ycombinator.com/item?id=47303604

...you can use existing communication channels (website, readme on github) to ask people for an invite to participate in it.
by mmustapic | 2026-03-09 10:34:21+00:00
The assertion was "if you really know how to prompt, give feedback, do small corrections and fix LLM errors, then everything works fine".

It is impossible to prove or disprove because if everything DOES NOT work fine you can always say that the prompts were bad, the agent was not configured correctly, the model was old, etc. And if it DOES work, then all of the previous was done correctly, but without any decent definition of what correct means.
by mikkupikku | 2026-03-09 10:34:22+00:00
On Saturday I had claude generate ~10k of lines of Lua code which uses the libASS subtitle format to build up nearly two dozen GUI widgets from subtitle drawing primitives, including nestable scrollable containers with clipping, drop down menus, animated tab bars, and everything else I could think of. I read probably about 100 lines of code myself that day, I "verified" the code only by testing out the demo claude was updating through the process.

Then on Sunday I woke up and had claude bang out a series of half a dozen projects each using this GUI library. First, a script that simply offers to loop a video when the end is reached. Updated several of my old scripts that just print text without any graphical formatting. Then more adventurous, a playlist visualizer with support for drag to reorder. Another that gives a nice little control overlay for TTS reading normal media subtitles. Another that let's people select clips from whatever they're watching, reorder them and write out an edit decision list, maybe I'll turn this one into a complete NLE today when I get home from work.

Reading every line of code? Why? The shit works, if I notice a bug I go back to claude and demand a "thoughtful and well reasoned" fix, without even caring what the fix will be so long as it works.

The concepts and building blocks used for all of this is shit I've learned myself the hard way, but to do it all myself would take weeks and I would certainly take many shortcuts, like certainly skipping animations and only implementing the bare minimum. The reason I could make that stuff work fast is because I already broadly knew the problem space, I've probably read the mpv manpage a thousand times before, so when the agent says its going to bind to shift+wheel for horizonal scrolling, I can tell it no, mpv has WHEEL_LEFT and RIGHT, use those. I can tell it to pump its brakes and stop planning to load a PNG overlay, because mpv will only load raw pixel data that way. I can tell it that dragging UI elements without simultaneously dragging the whole window certainly must be possible, because the first party OSC supports it so it should go read that mess of code and figure it out, which it dutifully does. If you know the problem space, you can get a whole lot done very fast, in a way that demonstrably works. Does it have bugs? I'd eat a hat if it doesn't. They'll get fixed if/when I find them. I'm not worried about it. Reading every line of code is for people writing airliner autopilots, not cheeky little desktop programs.
Gyro-Claw – Secure execution runtime for AI agents
by gyroscape | 2026-03-09 10:34:35+00:00
Hi HN,

I built Gyro-Claw, an open-source security runtime designed for AI agents and autonomous systems.

Modern AI tools can execute code, call APIs, and access sensitive data. One problem I noticed is that these systems often run with too much trust, which can lead to secret leakage or unsafe execution.

Gyro-Claw introduces a secure execution layer that sits between AI agents and the system.

It provides:

• sandboxed execution
• controlled secret access
• permission boundaries
• cryptographic fingerprinting
• zero-trust architecture

The goal is to make AI agent infrastructure safer without requiring developers to redesign their entire stack.

https://github.com/gyroscape/gyro-claw

The project is MIT licensed and written in Rust.

I'd really appreciate feedback from the community.
by szszrk | 2026-03-09 10:34:39+00:00
You don't need "that technology to become popular" to make it even more popular. It already was popular enough and it already worked.

Your whole comment makes no sense to me. Completely confusing.

Who are you arguing with? Why RSS has to compete with anything? Why do you even refer to it as "technology" - it's a text file people used to edit by hand in notepad. And maybe automate that with a script in their html editor.

It was popular, it's a fact. It was and is included in multiple blogging platforms. It was used by techies. It was used by non-techies. Learning curve was non existent and it was trivial to use on both ends.

What created friction was: killing the biggest RSS reader service that was free for all and killing very good support in browsers.

It used to be trivial - every browser was showing an orange button if site had rss. You could click it. You could add the feed to browser bookmark bar. It would display feed as nice bookmarks, downloading it live. This is what we lost - and we lost it because big companies wanted us to be entrenched in their socials. The rest was literally trivial.
by rcgeorge23 | 2026-03-09 10:35:30+00:00
We're building Aucly: https://aucly.co.uk/

It's an auction website for schools, charities etc without the exploitative transaction fees.

My wife and I are pretty heavily involved in our son's school PTA (parent teacher association) and have helped run school fundraising events for a few years, so we feel sort of like domain experts in this area :)
by Grimblewald | 2026-03-09 10:35:50+00:00
It works fine for me, because I don't trust to to do anything more than line changes, self-contained prototypes or minor updates. I've seen what happens when people give llms full control over authoring, and it has never worked out. Just look at the dumpster fire spotify has become. Its a buggy mess that barely works and is openly touted as being primarily llm developed at present.

point me towards something complex which llms have contributed towards significantly without massive oversight where they didnt fuck things up. I'll eat my words happily, with just a single example.
by devrimozcay | 2026-03-09 10:36:01+00:00
Interesting direction.

One thing we've been seeing with production AI agents is that the real risk
isn't just filesystem access, but the chain of actions agents can take once
they have tool access.

Even a simple log-reading capability can escalate if the agent starts
triggering automated workflows or calling internal APIs.

We've been experimenting with incident-aware agents that detect abnormal
behavior and automatically generate incident reports with suggested fixes.

Curious if you're thinking about integrating behavioral monitoring
or anomaly detection on top of the sandbox layer.
by lowdude | 2026-03-09 10:36:31+00:00
I cannot say much about the quality, but I am also testing around with it at the moment. As for the identity control, you may be able to achieve this with a few extra steps, if you set up bucket policies for the credentials. For this, it would be a bit cleaner to move the storage box to a project of its own.

I still have to check if this actually works in practice, but I am hopeful. I based it off their documentation here: https://docs.hetzner.com/storage/object-storage/faq/s3-crede...
by devrimozcay | 2026-03-09 10:36:48+00:00
One thing I'm curious about here is the operational impact.

In production systems we often see Python services scaling horizontally
because of the GIL limitations. If true parallelism becomes common,
it might actually reduce the number of containers/services needed
for some workloads.

But that also changes failure patterns — concurrency bugs,
race conditions, and deadlocks might become more common in
systems that were previously "protected" by the GIL.

It will be interesting to see whether observability and
incident tooling evolves alongside this shift.
by tpm | 2026-03-09 10:36:54+00:00
One of things the US could have done to stop proliferation was to actually honor its commitments it gave to Ukraine in the 1994 agreement in return to Ukraine agreeing to abandon their nukes. It didn't. Now a country sees that US is happy to bomb other non-nuclear countries, but not nuclear countries, and they doen't help even when they agreed to. There is exactly one lesson a country will learn from that.
by carlos-menezes | 2026-03-09 10:37:09+00:00
I started working on Rio[0], a modern TypeScript HTTP client for Node.js 24+, Deno and Bun. It's built on the native `fetch` API and fully type-safe from request to response. It's still very much a work in progress but I'm working towards an alternative to fetch/Axios/ky I wish I had.

[0] https://github.com/carlos-menezes/rio
by redat00 | 2026-03-09 10:37:12+00:00
I'm working on an alternative solution to Ansible and Puppet, trying to mix the best of both world: The pull-based aspect of Puppet, by having an agent running on nodes, and the simplicity of Ansible, by writing playbooks and roles.

It's called Peekl, and is available on Github. Tho it's still in what I'd called "alpha". Lot of new features to come!

https://peekl.dev
by devrimozcay | 2026-03-09 10:37:13+00:00
This looks useful.

One pattern we've been seeing internally is that once teams
standardize API interactions through a single interface
(or agent layer), debugging becomes both easier and harder.

Easier because there's a central abstraction,
harder because failures become more opaque.

In production incidents we often end up tracing through
multiple abstraction layers before finding the real root cause.

Curious if you've built anything into the CLI to help with
observability or tracing when something fails.
by antonkochubey | 2026-03-09 10:37:30+00:00
>The CAS latency for ECC is about double what gaming RAM offers

Ironically, overclocking ECC memory is much easier than overclocking non-ECC DIMMs, because you know exactly at which point you start encountering instability and need to dial back, instead of relying on.. application crashes and BSOD's to know that you're running way too optimistic clocks/timings.

Meanwhile I overclocked 'low clock / loose timing' ECC DIMMs on Ryzen 7 platform with no issues at all – kept increasing clocks and lowering timings until ECC started reporting errors, then dialed it back a couple notches, and now it is not just stable, but I also have exact reporting of it being stable.
by stinkbeetle | 2026-03-09 10:37:33+00:00
> because ToS have been long used to demand unreasonable things and threaten people with expensive lawsuits. The advantage of companies losing bullying power significantly outweighs the disadvantage of less business freedom

Why those in particular though? The criminal law one sure that's a part of contract law already. Why the others? Why not different ones? It was just asserted that those were reasonable and no other terms are.
by wolvesechoes | 2026-03-09 10:38:10+00:00
> Swift is not really for systems level programming

Apple seems to think differently.

> and interestingly some projects like Ladybird have moved away from Swift towards Rust.

Not really interesting after you spent some time tracking lifecycle of FOSS projects.
I don't think it is a last "moving away" announcement we get from Ladybird.
by alsetmusic | 2026-03-09 10:38:14+00:00
> People of all walks are extremely uninterested in being told that they need to care about something that they do not care about.

You don’t care. There it is. Just say it. It’s not a crime. I’m not judging you. I’m really not.

I care and it might not matter, but I do. It’s not for you. That’s ok. Don’t bag on it for reasons other than this. It’s not difficult and I don’t care if you don’t care. It’s fine.
by trueno | 2026-03-09 10:38:48+00:00
is it underpowered? i'm pretty sure that a-chip variant is binned way faster than the m1 air i had and that thing was a paradigm shift little workstation in a backpack when it came out in 2020 that somehow had no fan and got all day battery. i was compiling faster on that then i could on the actual workstation i was provisioned for work, so im gonna guess there aren't laptops at this price point that put this kind of horsepower down? there's quite a few trade offs getting this over an air but i doubt it's an underpowered device at its price point
by softwarehippie | 2026-03-09 10:38:51+00:00
As a personal learning project on how to write efficient GPU code I'm trying to implement different shortest-path algorithms on the GPU. This is notoriously one of the cases where a simple algorithm like Dijkstra on the CPU will beat many implementations on the GPU.

It has been a lot of fun to learn about Vulkan / GLSL and the GPU execution model to figure out why the CPU is so much faster than the GPU. I'll be open sourcing the code soon but so far I'm documenting my journey in a series of blog posts. First one of the series is https://www.execfoo.de/blog/deltastep.html
by jmstfv | 2026-03-09 10:39:04+00:00
I've finally finished the long-abandoned project that I've been meaning to build for a while.

If you use Stripe Billing for subscriptions, your customers can specify reasons why they cancelled (e.g. too expensive, not using it, switched to competitor, etc.). However, to access those, you either have to use Stripe Sigma or pull them from the API. I wanted to build a more convenient way to access those (and also act upon them).

I've submitted the app to Stripe's App Marketplace, but I have a limited number of test invites to send out if you're interested (I will happily waive your subscription for 3 months).

https://dunningbear.com
by anonzzzies | 2026-03-09 10:39:21+00:00
They cannot? We have a client from 25 years ago and all the devops for them are massive bash scripts; 1000s of them. Not written by us (well some parts as maintenance) and really the only 'thing' that almost always flawlessly fixes and updates them is claude code. Even with insane bash in bash in bash escaping and all kinds of not well known constructs. It works. So we habe no incentive to refactor or rewrite. We did 5 years ago and postponed as we first had to rewrite their enormous and equally badly written ERP for their factory. Maybe that would not have happened either now...
by throwawayffffas | 2026-03-09 10:39:46+00:00
> The Unitree demos are prerecorded movements with no real adaptability.

That is not true. The routine is preprogrammed, but there is adaptability. If there wasn't they would fall on the ground in the first 5 seconds. The movement involved in the routine we saw requires continuous adjustment. You can't just record the movement as you would with a video game animation, real physics get in the way and you end up on your back on the ground trying to do a jump and a backflip.

If you think I am wrong, sure I could be but have a look at atlas, https://www.youtube.com/watch?v=oe1dke3Cf7I

The robots motion is not preprogramed at all, see how much more smooth the motion is?

Thats because boston dynamics are using an approach where they try to calculate and take the dynamics of motion into account, just like Unitree.

The kawasaki approach is clearly to use overwhelming torques in an effort to cancel all the dymanics and produce fully controlled movement. Exactly what an old man does as well or a robotic arm in a factory. It's honestly embarrassing it looks like kawasaki has no progress in the last 30 years their robots still move like its 1996.

Have a look here https://underactuated.csail.mit.edu/intro.html for a more indepth explanation of the difference between the two approaches.
by vova_hn2 | 2026-03-09 10:40:05+00:00
I think that this is the issue then, not pulling dependencies from the internet directly.

> meaningful review
No that I think about it, maybe for the first time in history it's actually feasible to review all the code in the repos using LLMs. Before LLMs were a thing, for any big project that would be way too much work to realistically do it.

Also, someone can provide code review of publicly available dependencies as a service, to avoid wasting tokens of reviewing same code again and again by each dev locally on their machine.

U wonder if anyone is already working on such service...