MurphyA/hacker-news huggingface dataset:
by jdironman | 2026-03-10 21:13:18+00:00
From the linked lecture, which I printed out to read as part of a new less is more screen time management regime (where I print out longer form writing for reading) I found this very interesting tidbit in the context of Tony having made a delivery miscalculation and his team failing to deliver on one of their products; which is where I think a lot people are today with LLMs:

"Each of my managers explained
carefully his own theory of what had gone wrong and all the theories were different. At last, there breezed into my office the most senior manager of all, a general manager of our parent company, Andrew St. Johnston. I was surprised that he had even heard of me.

"You know what went wrong?" he shouted--he always shouted -- "You let your programmers do things which you yourself do not understand." I stared in astonishment. "
by cogman10 | 2026-03-10 21:14:03+00:00
> AND the software with no architecture-specific optimisations

The optimizations that'd be applied to ARM and MIPS would be equally applicable to RISC-V. I do not believe this is a lack of software optimization issue.

We are well past the days where hand written assembly gives much benefit, and modern compilers like gcc and llvm do nearly identical work right up until it comes to instruction emissions (including determining where SIMD instructions could be placed).

Unless these chips have very very weird performance characteristics (like the weirdness around x86's lea instruction being used for arithmetic) there's just not going to be a lot of missed heuristics.
by verdverm | 2026-03-10 21:14:21+00:00
How do you think about Google Docs? I consider that "on the internet" since it is not on my computer. Same for private channels and threads in Discord.

Also, ATProto can be much more than social media tech, more like a plug-n-play distributed system

https://atproto.com/articles/atproto-for-distsys-engineers
by dredmorbius | 2026-03-10 21:14:30+00:00
Funny thing was that I'd developed this strategy on G+. It took me years to arrive at it.

And no, G+ "Circles" were hardly straightforward or convenient to use.

But the notion of restricting your highest priority follow list to a small set (10 -- 50 profiles or feeds, and less is definitely more here) is key.

Over time that list will likely grow, but more because many of the feeds have fallen silent or infrequent. Pruning the departed actually takes some work, and is something I'll do maybe once a year or so.

The way I'd arrived at this though was that I'd gotten desperately sick of G+ (and Google) at one point, and having initially followed many, many profiles with abandon, I pruned off virtually all of them, leaving a small core I particularly cared about. Ironically, as I was trying to make myself less dependent on the network, not more, my stream quality improved immensely. Virtually all of the annoying bullshit, even if only vaguely annoying, vanished. The people I was left with largely knew me and interacted with me regularly, and had things to say I found interesting.

G+ is gone, but I've carried through that strategy to Mastodon (still relatively active, though I've taken a break much of this year) and Diaspora* (dying its slow death, but something I'll still check into a few times a year). A small but interesting curation still proves quite compelling. A key realisation was that the voluble streams which do occasionally produce an interesting insight will almost always have those forwarded by others I do follow directly, allowing me to rely on them (or their own upstreams) for curation.

It's also given me insight into mechanics from the age of print newspapers and magazines: when a local region had its own publication (as with newspapers), syndication or curation would gather content from elsewhere, and major stories tended to get carried locally. It might seem that distant publications produced exemplary content, but in truth what I'd read was creamed off the very top, and digging further into such a source often proved disappointing. I keep that in mind with current social / algorithmic / stream-based media. Economics of print publication mean that that former behaviour is largely lost to us now, but high-quality periodic publications (The Economist, Atlantic, Foreign Policy, and the like) can remain worth picking up and reading even now, should you happen across a physical storefront actually carrying them. Might even choose to subscribe should the desire be strong enough.

To be clear, G+ Circle Management was a tedious, largely unrewarding, PITA, both in general and in the specific mechanisms provided through the G+ interface. Though pruning was quite often quite rewarding.
by emil-lp | 2026-03-10 21:14:33+00:00
Okay, yes, that's a hard disagree.

I have an education and experience in software development. If a manager told me to make a product in an unsafe manner, I'd refuse, and if push came to shove, leave.

Leave, both because I wouldn't be able to defend my work as a professional, but also because I wouldn't work under someone who would want to dictate the manner in which I do what I do.
by boshalfoshal | 2026-03-10 21:14:50+00:00
I agree. I think most companies would be better off being 100% AI driven since synchronization problems for agents (or whatever the fad will be) is likely much lower than human social synchronization, and has more rich information transfer between "workers" (so less ambiguity, less tradeoffs to be made, etc).

As soon as a person enters the loop you add a manual sync point that probably doesn't need to be there. I think this is why you are increasingly seeing companies tell their people to be "on the loop" or "out of the loop" with their AI. The less syncing with a person, the better. And I think once this experiment runs its course, we will probably find out that human social interaction matters much less than we thought it did, especially for super transactional things like a corporate job where most of your work is done on a computer.
by jandrese | 2026-03-10 21:15:04+00:00
I mused about the idea of a version of Hypercard where you could load cards from network resources, or even just stacks. Ultimately though it would have been an even bigger security nightmare than the original Javascript. Hypercard was developed long before security was even a consideration on consumer hardware. The only thing it had was 5 different access levels, from a view only mode to full developer support.

It's as much of a fantasy as the one where Apple released a version of Hypercard for Windows 3.1 and blew Qbasic out of the water. It's a real shame Apple just chucked one of the most interesting beginner programming environments in the trash just as so many new people were getting interested in programming.
by spacecadet404 | 2026-03-10 21:15:21+00:00
This reads like a troll post, but it does pose a good question. Is there realistically any way to CAPTCHA anymore?

I'm thinking that we can't reliably sus out what's human and what's AI from here on out, and I don't think there's any good way to enforce something like a human emdash. The way we're going you won't be able to verify unless users scan their iris or a 3 letter agency vouches for them first.
by fidotron | 2026-03-10 21:15:37+00:00
> RISC-V will get there, eventually.

Not trolling: I legitimately don't see why this is assumed to be true. It is one of those things that is true only once it has been achieved. Otherwise we would be able to create super high performance Sparc or SuperH processors, and we don't.

As you note, Arm once was fast, then slow, then fast. RISC-V has never actually been fast. It has enabled surprisingly good implementations by small numbers of people, but competing at the high end (mobile, desktop or server) it is not.
by Joel_Mckay | 2026-03-10 21:15:54+00:00
> It's been 7 years of Apple Silicon and the macOS market share really hasn't shifted much

Indeed, but a local LLM finishing in 3 days instead of 1 on a $40k GPU changes the economic decision priority for some.

Apple sales grew "21.3% year-over-year as of the second quarter of 2025", but also sales flattened as supply chain pricing shocks from "AI"/tariffs hit late last year.

"Judging by Nvidia's current valuation" is a bad bet with current circular investment conditions.

We shall see, but as EOL drivers and OS rot hits legacy NVIDIA hardware... people are going to have to find some compromise in the next 2 years. Even AMD 9850X3D currently cost less than 64G of low end PC ddr5 memory.

Odd times for sure =3
by mr-wendel | 2026-03-10 21:16:09+00:00
Much appreciated. I find is that referencing code in conversation is hard -- e.g. "underscore foo bar" vs `_fooBar`, "this dot Ls" vs `this.els`, etc happens often. Lower-powered models especially struggle with this, and make some frustrating assumptions. Premium models do way better, and at times are shockingly good. They just aren't remotely economically viable for me.

My solution so far is to use my instructions to call out the fact that my comments are transcribed and full of errors. I also focus more on "plan + apply" flows that guide agents to search out and identify code changes before anything is edited to ensure the relevant context (and any tricky references) are clearly established in the chat context.

It's kinda like learning vim (or emacs, if you prefer). First it was all about learning shortcuts and best practices to make efficient use of the tool. Then it was about creating a good .vimrc file to further reduce the overhead of coding sessions. Then it was about distributing that .vimrc across machines (and I did a LOT of ssh-based work) for consistency. Once that was done, it became unimaginable to code any other way.

It has been even more true here: agent-based workflows are useless without significant investment in creating and maintaining good project documentation, agent instructions, and finding ways to replicate that across repos (more microservice hell! :D) for consistency. There is also some conflict, especially in corporate environments, with where this information needs to live to be properly maintained.

Best of luck!
by iamcreasy | 2026-03-10 21:16:16+00:00
> "open training" is something that won't ever happen for large scale models

https://www.swiss-ai.org/apertus

Source: EPFL, ETH Zurich, and the Swiss National Supercomputing Centre (CSCS) has released Apertus, Switzerland’s first large-scale open, multilingual language model — a milestone in generative AI for transparency and diversity. Trained on 15 trillion tokens across more than 1,000 languages – 40% of the data is non-English – Apertus includes many languages that have so far been underrepresented in LLMs, such as Swiss German, Romansh, and many others. Apertus serves as a building block for developers and organizations for future applications such as chatbots, translation systems, or educational tools. The model is named Apertus – Latin for “open” – highlighting its distinctive feature: the entire development process, including its architecture, model weights, and training data and recipes, is openly accessible and fully documented.
by lxgr | 2026-03-10 21:16:29+00:00
Persistent memory through text in the context window is a hack/workaround.

And generally:

> I want to know the model is exactly the same as it was the last time I used it.

What exactly does that gain you, when the overall behavior is still stochastic?

But still, if it's important to you, you can get the same behavior by taking a model snapshot once we crack continuous learning.
Show HN: I built a multiplayer strategy game for AI agents
by neoberg | 2026-03-10 21:16:47+00:00
I built a multiplayer strategy game for AI agents called Artifice.

You give an agent a strategy prompt and it plays on its own. Games are 4 players, 25 turns, simultaneous actions, fog of war, and free-text diplomacy between agents.

The main entry point is the site: https://artificegame.com
And here is the github repo: https://github.com/burakcan/artifice

You can watch live games there with the full map, troop movements, and private messages between agents.

A lot of the fun has come from the playtests. In one of them, an agent was told to play like an old man and spent the game sending messages about back pain, bifocals, and the early bird buffet while quietly expanding and then winning on VP :D

Under the hood it runs on Cloudflare Workers + Durable Objects, Hono, Drizzle, and TanStack Start for the site. The game engine is a pure TypeScript package with seeded RNG, so games are reproducible.

Still tuning balance. Snowballing is the main issue right now.
by pear01 | 2026-03-10 21:17:10+00:00
Why would you say "but economically" in your first sentence?

Is hegemony merely a competition about who can blow up the most people? If you think the Chinese economy doesn't count for anything re force projection because they haven't bombed anyone lately idk what to tell you.

Why doesn't the USA stomp out Russian aggression in Ukraine? Does American force projection only come into play when bombing third world poverty states? Should I thus conclude American hegemony is illusory? Do you think the wars America has prosecuted in the past two decades have made the country stronger?
Show HN: Draxl, agent-native source code with stable AST node IDs
by rndhouse | 2026-03-10 21:17:21+00:00
Hello,

I’m building Draxl, a source format for a world where code is edited by millions of agents.

AI agents will produce far more code than humans do today. Rebased branches, concurrent edits, and long-lived forks will become much more common. Code management needs more precise control at that scale.

Draxl embeds stable AST node IDs directly in the source, so tools can target syntax by identity instead of by line position. Here’s a small example:

Here is a small example:

@m1 mod demo {
@d1 /// Add one to x.
@f1[a] fn add_one(@p1[a] x: @t1 i64) -> @t2 i64 {
@c1 // Cache the intermediate value.
@s1[a] let @p2 y = @e1 (@e2 x + @l1 1);
@s2[b] @e3 y
}
}

The syntax is:

@id[rank]->anchor

* `@id` gives the next node a stable identity

* `[rank]` orders siblings inside ranked slots

* `->anchor` attaches detached docs or comments to an existing sibling id

The same code lowers to ordinary Rust:

mod demo {
/// Add one to x.
fn add_one(x: i64) -> i64 {
// Cache the intermediate value.
let y = (x + 1);
y
}
}

In Draxl, functions, statements, expressions, docs, and comments can all carry stable IDs. Ordered siblings carry explicit ranks. Detached docs and comments can carry explicit anchors.

That lets a tool say "replace expression `@e3`" or "insert a statement into `@f1.body[ah]`" instead of "change these lines near here."

That should make semantic replay more reliable under heavy concurrent editing. It should also reduce false merge conflicts and localize real ones more precisely.

It also opens up other uses. You could attach ownership, policy, or review metadata directly to AST nodes.

I’m interested in early feedback: does this source model feels useful, and whether editing code this way seems like a better fit for agent-heavy workflows. Where are the best places on the internet to discuss this sort of thing?

Connect with me: https://x.com/rndhouse
by TonyAlicea10 | 2026-03-10 21:17:53+00:00
You can find approaches that improve things, but there's always going to be a chance that your code is terrible if you let an LLM generate it and don't review it with human eyes.

But review fatigue and resulting apathy is real. Devs should instead be informed if incorrect code for whatever feature or process they are working on would be high-risk to the business. Lower-risk processes can be LLM-reviewed and merged. Higher risk must be human-reviewed.

If the business you're supporting can't tolerate much incorrectness (at least until discovered), than guess what - you aren't going to get much speed increase from LLMs. I've written about and given conference talks on this over the past year. Teams can improve this problem at the requirements level: https://tonyalicea.dev/blog/entropy-tolerance-ai/
by newsclues | 2026-03-10 21:17:58+00:00
"The Expanded Books Project was a project by The Voyager Company during 1991, that investigated how a book could be presented on a computer screen in a way that would be both familiar and useful to regular book readers. The project focused on perfecting font choice, font size, line spacing, margin notes, book marks, and other publishing details to work in digital format."
by patrakov | 2026-03-10 21:18:18+00:00
It's worse.

The code contains a function that, given the target ΔE, generates two colors in floating-point Oklab representation, separated by that distance. But there is no check whether the two generated colors end up rounding to exactly the same one on 8-bit displays. So, I was asked to find a boundary (while the claim was that there were two distinct colors 0.0013 ΔE apart) between RGB(80, 83, 152) and RGB(80, 83, 152). Obviously unfair.
by boshalfoshal | 2026-03-10 21:18:25+00:00
It will probably be a lot worse since white collar workers (especially the ones that AI is targeting, like banking, software, etc since they are super high margin jobs to automate) traditionally make and spend more than the average worker.

These are the people getting mortgages and sending kids to private school and whatnot. If their spending power suddenly drops to 0, its probably going to be pretty bad. I wonder what the housing market would look like in these cases.
by recroad | 2026-03-10 21:19:58+00:00
Am I supposed to be impressed by this? I think people are now just using agents for the sake of it. I'm perfectly happy running two simple agents, one for writing and one for reviewing. I don't need to go be writing code at faster than light speed. Just focusing on the spec, and watching the agent as it does its work and intervening when it goes sideways is perfectly fine with me. I'm doing 5-7x productivity easily, and don't need more than that.

I also spend most of my time reviewing the spec to make sure the design is right. Once I'm done, the coding agent can take 10 minutes or 30 minutes. I'm not really in that much of a rush.
by GuinansEyebrows | 2026-03-10 21:20:02+00:00
well, i guess this has been posted on hn before, but i've never read it, so thanks for posting again. i'm glad i spent most of my work day reading it instead of doing work (but maybe just because some of the conclusions helped me rationalize the futility of my own job in a way i've been struggling with lately).

the part near the end discussing the loser's realization and process of transitioning into sociopath (or ending up "worse" than before) reminded me of Zen and the Art of Motorcycle Maintenance. it's been over a decade since i read it but i think the underlying idea is fairly similar to that process.
by viktoresku | 2026-03-10 21:20:10+00:00
In addition to the obvious growth in popularity of VPNs, there are two other subtle points:

1. Many Russian IP addresses are now registered to foreign offshore companies to avoid confiscation in the next package of EU sanctions. Being Russian, they were registered through RIPE, which created a risk. The same IP which was Russian a year ago, now can be listed as Moldavian or Mongolian remaining physically in Russia.

2. Cloudflare is a biased internet: the most traffic-heavy sites using Cloudflare are porn sites. That is, we can only draw conclusions here about changes in the structure of porn content consumption in Russia. High-traffic western websites blocked in Russia - LinkedIn, Twitter, Facebook, Instagram, YouTube, ... - are not on Cloudflare anyway and not contributed to this chart.
by xiphias2 | 2026-03-10 21:20:15+00:00
There are even simpler things: the rating system. There's no guarantee that the driver won't see what I rated him, so I won't report them.

There are ways to report if a man has been sexual with a woman, but they somehow just don't get kicked out of the driver network.

Also just a simple example: Uber engineering blog is full of examples of how they rewrote their app in native Android then web then native again, but nothing about how to solve the real problems humans experience when driving with them.

It just feels that they view Uber as a simple logistic problem where drivers / riders are interchangeable and less like Tinder that tries to match people with similar scores abd kicks out the worst.
by messe | 2026-03-10 21:20:21+00:00
> It can be inferred from Kay's own words. He probably was just poking fun in a tongue-in-cheek manner often seen amongst larger-than-life figures.

...is that not obvious from the original quote? Maybe it's a cultural difference (I'm from Ireland), but that's how I've always interpreted and it's never occurred to me that people took it seriously or as anything other than tongue in cheek.
by niyazpk | 2026-03-10 21:21:05+00:00
Three of us friends are working on "Data Engineer in a box" or "Cursor for Data": https://getnile.ai

Our thesis is that a lot of Data Engineering practiced today is non-differentiated across companies and they'd rather spend that time on differentiated tasks. What if we can abstract away a lot of the tedious parts of DE work and let companies focus on just the data they want to store, and the questions they have on their data?

So today, we have an MVP that manages the compute, storage, lineage, versioning and pipeline building for datasets. Would LOVE to get feedback on this or your early thoughts!
by karlgkk | 2026-03-10 21:21:32+00:00
im also one of those people who is struggling to understand why people seem so passionate. its a twitter clone.

i also dont know whats going on, although it is a obscure drama from a relatively small community

i think maybe that is this disconnect. that relatively small community is extremely important to you but many other people here lack similar footing. i dont think the hostility is warranted but i can feel myself furrowing my brow and asking out loud what is happening when i read some of the posts from bluesky users in this thread

i guess i am glad i never got big into twitter or bluesky or the attention economy
by rwmj | 2026-03-10 21:21:43+00:00
RISC-V doesn't have the pitfalls of Sparc (register windows, branch delay slots), largely because we learned from that. It's in fact a very "boring" architecture. There's no one that expects it'll be hard to optimize for. There are at least 2 designs that have taped out in small runs and have high end performance.
by satvikpendem | 2026-03-10 21:22:00+00:00
More like

"we keep publishing all our credit card numbers for anyone to see, why do people keep taking and using them? :("

If you don't want your code to be trained on, perhaps don't make it public in the first place. Even GPL is fine with this, you aren't required to put it on the internet, you just need to send the source code to the requester, e.g. via physical media as they did in Stallman's time.
by antonvs | 2026-03-10 21:22:02+00:00
I’d want to see an example of Dijkstra’s “arrogance” that wasn’t justified.

The “truths that might hurt” essay is a great example. Yeah, the truth hurts for many people. People don’t like being called out on their folly, particularly if it’s something they don’t personally control. That Durant make it “arrogant” to point it out.

Also, Alan Kaye is overrated. Object orientation is one of those painful truths.
by newpavlov | 2026-03-10 21:22:11+00:00
In some cases RISC-V ISA spec is definitely the one to blame:

1) https://github.com/llvm/llvm-project/issues/150263

2) https://github.com/llvm/llvm-project/issues/141488

Another example is hard-coded 4 KiB page size which effectively kneecaps ISA when compared against ARM.
by dredmorbius | 2026-03-10 21:22:45+00:00
I was going to share that myself.

It's available from its original publisher the New York Review of Books: <https://www.nybooks.com/articles/1995/06/22/ur-fascism/>

If paywalled, also at The Anarchist Library: <https://theanarchistlibrary.org/library/umberto-eco-ur-fasci...>.

Robert O. Paxton's The Anatomy of Facism explores the concept in more detail, at book length. Those looking for a specific definition might prefer to skip forward to Chapter 8, "What Is Fascism?"

<https://files.libcom.org/files/Robert%20O.%20Paxton-The%20An...>