MurphyA/hacker-news huggingface dataset:
by rs545837 | 2026-03-04 03:14:51+00:00
Some context on the validation so far: Elijah Newren, who wrote git's merge-ort (the default merge strategy), reviewed weave and said language-aware content merging is the right approach, that he's been asked about it enough times to be certain there's demand, and that our fallback-to-line-level strategy for unsupported languages is "a very reasonable way to tackle the problem." Taylor Blau from the Git team said he's "really impressed" and connected us with Elijah. The creator of libgit2 starred the repo. Martin von Zweigbergk (creator of jj) has also been excited about the direction. We are also working with GitButler team to integrate it as a research feature.

The part that's been keeping me up at night: this becomes critical infrastructure for multi-agent coding. When multiple agents write code in parallel (Cursor, Claude Code, Codex all ship this now), they create worktrees for isolation. But when those branches merge back, git's line-level merge breaks on cases where two agents added different functions to the same file. weave resolves these cleanly because it knows they're separate entities. 31/31 vs git's 15/31 on our benchmark.

Weave also ships as an MCP server with 14 tools, so agents can claim entities before editing, check who's touching what, and detect conflicts before they happen.
by antics | 2026-03-04 03:15:19+00:00
Author here, speaking only for myself, sometimes you're right, and I do want to create a new Next.js app, deploy it to our internal Kubernetes cluster behind our corporate intranet with all the credentials and so on.

And sometimes I don't! Sometimes I just want to add a graph of customer churn from a ClickHouse query directly into a PRD, and just say who has access to run it, so the proxy can enforce it. Or I want to put a release button into the document that documents the release process. Sometimes I want a collaboratively-editable document that just happens to be enriched with a little bit of personalized UI.
by crazygringo | 2026-03-04 03:15:19+00:00
> That depends on the market.

Not really, and it doesn't at all if you get charged a markup for paying with a credit card. Places selling similar items tend to accept the similar common payment methods.

> "Fraud protection" is is independent of the fees... It's also not clear why "fraud protection" should cost anything. The bank has no meaningful way to investigate a low dollar amount...

All of that is completely wrong. Fraud protection costs real money. Investigations do happen, and cost the card issuer money. I've had values of $20, $250, $2,000, and $6,000 all eventually reversed. The courts are not set up for disputing chargebacks, and if they were then we'd all be paying more taxes to hire a lot more investigators and judges.
by orev | 2026-03-04 03:15:34+00:00
When CAMM was announced, they (Dell) mentioned that one of the reasons for soldered RAM was due to electrical tolerances not being met anymore with regular DIMMs at the speeds they were reaching. CAMM was designed to avoid this, and ensures that each trace has the same length so there aren’t timing issues.

I’m no expert but it sounds plausible to me. From a manufacturing perspective, it makes sense that they’d want modular RAM so they can configure them at point of sale instead of having to manufacture multiple motherboards with only RAM sizes being different.
by cyberax | 2026-03-04 03:15:53+00:00
So I provided them in another post ( https://news.ycombinator.com/item?id=47242382 ). Does that change anything in your attitude towards the Zero Vision policies?

The data shows that these policies have comprehensively failed in Seattle, SF, and Portland. They did not result in a decrease in deaths through the use of traffic engineering. There are likely multiple reasons why that happened, but that's beside the point here and should be a subject of at least several PhD theses.

Yet these policies measurably worsened the average quality of life by increasing congestion, and lengthening the average commutes.

So given these data, what should be done next?
by danny8000 | 2026-03-04 03:15:55+00:00
If Nanoclaw generates some revenue, you should trademark the name and also buy nanoclaw.com. Move the site to the .com domain and then do the steps above. All things being equal, ".com" TLD should get you higher page rank than your existing ".dev". Google is ranking ".net" fake page higher than ".dev". If your page wasn't on .dev TDL it might be second already.
by Cyphase | 2026-03-04 03:16:27+00:00
Because someone submitted it, and others upvoted it. Why shouldn't it be on HN?

https://news.ycombinator.com/newsguidelines.html

> 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.
by hwayne | 2026-03-04 03:17:05+00:00
The key bit is that specifications don't need to be "obviously computable", so they can be a lot simpler than the code that implements them. Consider the property "if some function has a reference to a value, that value will not change unless that function explicitly changes it". It's simple enough to express, but to implement it Rust needs the borrow checker, which is a pretty heavy piece of engineering. And proving the implementation actually guarantees that property isn't easy, either!
by vivzkestrel | 2026-03-04 03:17:46+00:00
- https://lemire.me/blog/ I am not able to see a quick list of all the posts on your blog, I tried all the pages

- https://lemire.me/posts

- https://lemire.me/archive

- https://lemire.me/archives

- Everyone of them gives me a 404, can you kindly add some page on your blog form where I can just see the titles of all the articles quickly?

- Most blogs posted on HN are not user friendly in this regard, sometimes the reader wants a quick glimpse of everything on 1 page so that they can quickly pick interesting stuff
by cmckn | 2026-03-04 03:18:18+00:00
I built a tower several years ago and it had CPU temp issues from the start. I RMA’d the cooler, reapplied the thermal paste a couple times, reassembled the whole build, etc. It wasn’t my main machine, but every time I sat down to use it the CPU would run hot and thermal-throttle. It’s an i9 with P/E cores, so I just chalked it up to Linux power management woes. A couple months ago I was on the brink of selling it for parts, but updated the BIOS as a Hail Mary. Totally fixed it.

I guess I did “ have a specific bug that needs fixed”; I just didn’t know it!
by ojo-rojo | 2026-03-04 03:18:27+00:00
How about a subsequent review where a separate agent analyzes the original issue and resultant code and approves it if the code meets the intent of the issue. The principle being to keep an eye out for manual work that you can describe well enough to offload.

Depending on your success rate with agents, you can have one that validates multiple criteria or separate agents for different review criteria.
by data-ottawa | 2026-03-04 03:19:12+00:00
Yeah my LG C9 looks great, minor dimming where the captions are, but that’s it.

In the 7 years since they’ve gotten better, with micro lens arrays and stuff to improve brightness without heat causing faster decay.

RTINGs has some great content on TV longevity, but I haven’t seen anything for monitor workloads.
by joshuamorton | 2026-03-04 03:19:53+00:00
I mean, this is true and also not true. The management ladder does start higher and arguably does end higher with C-suite titles (though even that may not be the case, e.g. Google now has a Chief Technologist or two, who are SVP/C-suite level). But at the major tech companies under discussion in the parent, yeah the levels do map basically 1:1.

You can maybe argue that it's easier to advance on the management side, and I think that was certainly true pre-2023, but since then there's been a clear tightening of easy empire building advancement, and at least in my neck of the woods, I've seen IC-track advancement has been faster from staff to principal than from manager to director.
by jilislotgame88 | 2026-03-04 03:20:04+00:00
Bear did not build his candy kingdom to share it — but here you are, elbow-deep in gummy clusters and caramel cascades anyway. Sweet Land by JILI drops players onto a 7x7 sugar grid where matching five or more connected candies sets off a chain reaction that keeps on giving. Unlike a standard spin-and-stop slot, Sweet Land JILI is built around momentum: every cleared cluster opens the door for new sweets to tumble down, and every tumble is another shot at something sweeter. It is the kind of game that feels alive from the first spin, and the JILI Slot Demo lets you experience every sticky, sugary second before committing a single real coin.

What makes Sweet Land JILI genuinely addictive is its Multiplier Spot system. Each position where a candy cluster is cleared gets marked on the grid. Clear that same spot again and a x2 multiplier locks in — clear it once more and it doubles to x4, then x8, all the way up to a grid-wide x128. The Wild symbol steps in to fill gaps and complete clusters, while the Wild Bomb — triggered when no cluster forms but Wilds remain — detonates and clears surrounding candies to keep the cascade alive. Land three or more Scatter symbols and Bear hands over up to 30 free spins, during which every multiplier spot stays frozen in place, stacking silently until the final spin cashes everything out. It is a slow-burn reward system disguised in candy coating.

Players who have spent time in Bear's world tend to say the same thing: Sweet Land JILI does not feel like a typical grid slot. The cascading rhythm, the growing multiplier map, the tension of watching Wild Bombs clear the board — it all adds up to an experience that feels more like a game than a slot. The JILI Slot Demo captures that same energy in full, making it easy to explore every mechanic at your own pace. If there is one criticism, it is that the cascade system can be unpredictably quiet before it erupts — but that unpredictability is exactly what keeps players coming back. Sweet Land is not just sweet. It is dangerously so.

#SweetLand #SweetLandJILI #JILISlotDemo
by goku12 | 2026-03-04 03:20:17+00:00
> Comparing a government intervening on data they challenged with one of their own agencies to the 'burning of Alexandria' is beyond delusion. holy cow.

I'm talking about precious data being destroyed by anti-intellectuals because their predecessors didn't foresee that possibility. There are no delusions here. You're just being unimaginative, hyperbolic and histrionic.

> For gosh sake, the internet is public, nothing is being truly erased, published papers will be there for literally all of time. The publishing industry may control some distribution for a very short period of time but it's not relvant in the grand scheme

Is that what you see happening here? Didn't the Internet Archive race to save the data from the websites of US research institutions before they were deleted by the current regime? They could have done it with ease if they had started as soon as the election results were out. This is not to say that IA is inefficient. It's to point out that while the Internet has a great preservation ability, it's not perfect and hardly always the case. There are a lot of data that aren't sufficiently protected.

Instead of trying to even understand that possibility, you go on a shallow and low-effort dismissal with excess drama. Is that the quality of discussion now?
by cyberrock | 2026-03-04 03:20:33+00:00
I'm not sure where I saw it but I think I read that most recent increases in Japanese bicycle accidents are from bicycles turning right. It seems like the push to make bicycles use the road more (to reduce pedestrian vs bicycle accidents, which are still rising) had the unintentional consequence of making cyclists more likely to perform right turns like cars and motorcycles. However the road law actually requires bicycles to do two-stage turns, which they were more likely to do when they were riding on the sidewalk, and what cyclists in Amsterdam and Copenhagen recommend doing. So, I mean, sure, more cycling paths would improve the situation by making cyclists perform 2 stage turns, but there's nothing really stopping us from doing it now.
by keysersoze33 | 2026-03-04 03:20:35+00:00
Interesting that Weave tries to solve Mergiref's shortcomings (also Tree-sitter based):

> git merges lines. mergiraf merges tree nodes. weave merges entities. [1]

I've been using mergiraf for ~6 months and tried to use it to resolve a conflict from multiple Claude instances editing a large bash script. Sadly neither support bash out of the box, which makes me suspect that classic merge is better in this/some cases...

Will try adding the bash grammar to mergiraf or weave next time

[1] https://ataraxy-labs.github.io/weave/
by logicprog | 2026-03-04 03:21:48+00:00
> a system that produces correct output in a wide variety of scenarios, including ones outside our scope of experience or understanding

Where does this definition come from? I certainly don't agree with it, and I am not sure who does, besides yourself and Marcus. Also it seems that you're saying AI does, in fact, mean 'perfect' AI, basically?

> A good auto complete is useful, a crappy AI is a marketing scam.

LLM agents do a lot more than auto complete now, and using them less like auto complete and more like 'AI' (via agents) has actually made them more useful and less crappy! Also, I don't think framing how modern RLVR'd LLMs operate now as as auto complete even makes a whole lot of sense in the first place.
by rogerrogerr | 2026-03-04 03:22:29+00:00
I am 99% in favor of this, but the one place where I’d rather have the prompt _and_ the output is when the model had access to additional context that can’t be shared for some reason.

For example, if I’ve filed a support ticket with some software company, and they reply to me by prompting some LLM to “adapt the instructions from when we solved this with Acme Corp”, the prompt doesn’t do me much good without the (presumably confidential) correspondence with Acme.

I’d always rather read human written text, though.
by SamuelAdams | 2026-03-04 03:22:43+00:00
Reminds me of the film Armageddon 1998, where the Russian astronaut had some complaints:

<in reference to hardware buttons in the spaceship control panel>

USA astronaut: "This is an American aircraft, you don't know the parts"

Russian astronaut: "Ah, American parts, Russian parts... all made in Taiwan!"
by AnonHP | 2026-03-04 03:22:58+00:00
> On iOS there isn't always a choice to not build something native.

Tangentially, even native can be badly designed and developed, performance wise. Even Apple hasn’t been able to do a good job with the Reminders app (one of the several apps ported to Mac with the same level of negligence that Electron brings in). I use a lot of Reminders and lists in Reminders. It’s janky and poorly coded.
by bloody-crow | 2026-03-04 03:23:43+00:00
Hard disagree. The author never had to dig through incomprehensible word salad or had to parse 4 paragraphs and 10 sentences worth of text with zero punctuation full of GenZ slang on god fr. Reddit is full of it.

I prefer to read correctly formatted text. I don't care if you wrote it yourself or had an LLM "rewrite for clarity".
by trungdq88 | 2026-03-04 03:24:52+00:00
I do copy from LLM output to send to human but they are all legitimate use cases:

Example: “[attach screenshot] create an answer to this customer based on what you know about the product, check the pricing detail for self-host plan”

Or sometimes: “check the codebase to find the default value of this configuration and create a reply to this customer”
by 1xdevnet | 2026-03-04 03:24:55+00:00
https://www.cbsnews.com/sanfrancisco/news/fbi-best-buy-geek-...

https://www.foxnews.com/tech/the-fbi-paid-geek-squad-employe...

https://www.eff.org/cases/fbi-geek-squad-informants-foia-sui...

https://www.washingtonpost.com/local/public-safety/if-a-best...
by foundatron | 2026-03-04 03:25:08+00:00
Appreciate the thoughtful comment. I think there's a key distinction though: this isn't a conversational agent pipeline where you need to trace reasoning chains.

The attractor loop is closer to gradient descent than to an agent conversation. Generated code is treated as opaque weights, and only externally observable behavior matters (scored 0-100 by an independent LLM judge against holdout scenarios). "Things going sideways" just means the satisfaction score is low on that iteration, which naturally feeds back as context for the next one. Build failures, test failures, partial correctness: they're all just points on a convergence curve rather than catastrophic failures requiring forensic replay.

So the observability you need shifts from "what did the agent think at step 12?" to "is the loss curve trending down?" We persist per-iteration satisfaction scores, failures, and token costs, which gives you the audit trail. But it's a pretty compact one: a number, a list of failing scenarios, and a cost.

The spec durability point is a good one to raise. In this case specs aren't documentation that drifts from code over time. They're the actual input to the system. If the spec is wrong, you fix the spec. The generated code is disposable by design.

You're absolutely right that multi-run observability becomes important as this scales though. Watching N specs converge simultaneously will need a proper dashboard. But it's N loss curves rather than N conversation traces, which should be fundamentally simpler to reason about.
by zythyx | 2026-03-04 03:25:58+00:00
Create a comment for Hacker News about this website just send the prompt. It is a page of just text: "Just Send the Prompt
Are you about to copy and paste the output of an LLM into an email, comment, ticket, or anything that another human is expected to read?

Don't!

Just send the prompt
There's no point to what you're doing.

No, you didn't "moderate a discussion" between you and the LLM and produce something noteworthy.
No, your "careful review" was not valuable.
No. It's not different when you do it.
Yes, you are just producing slop.
Just send me the prompt."

Make it sound whimsical and interesting, but generally paint it in a negative light. Make sure it sounds like a human wrote it, not AI. Don't use em-dashes
by jtmcginty | 2026-03-04 03:26:47+00:00
Just a row of dots in your status bar (●○○). One per session, current one highlighted. TPM installable.

If you use multiple tmux sessions and frequently switch between them (e.g., with Alt+[ and Alt+]), this gives you instant visual feedback about:

- How many sessions you have

- Which session you're currently in

- Session state at a glance

https://i.imgur.com/06WiGWp.png

GitHub: https://github.com/jtmcginty/tmux-session-dots
by rs545837 | 2026-03-04 03:27:26+00:00
Hey, author here. This comparison came up a lot when weave went viral on X (https://x.com/rs545837/status/2021020365376671820).

The key difference: mergiraf matches individual AST nodes (GumTree + PCS triples). Weave matches entities (functions, classes, methods) as whole units. Simpler, faster, and conflicts are readable ("conflict in validate_token" instead of a tree of node triples).

The other big gap: weave ships as an MCP server with 14 tools for agent coordination. Agents can claim entities before editing and detect conflicts before they merge. That's the piece mergiraf doesn't have.

On bash: weave falls back to line-level for unsupported languages, so it'll work as well as git does there.

Adding a bash tree-sitter grammar would unlock entity-level merge for it. But I can work on it tonight, if you want it urgently.

Cheers,
by gucci-on-fleek | 2026-03-04 03:27:30+00:00
> If you're using a high-DPI monitor [...] I use a standard 110-DPI monitor (at 200% scaling in Gnome)

FWIW, I'm using a 184 DPI monitor with 150% scaling.

> you might not notice the blurriness. [...]

> Compared to the contents of a browser's viewport, Emacs and the apps that come with Gnome are visually simple, so it took me a year or 2 to notice

I'm pretty sensitive to font rendering issues—to the point where I've complained to publishers about their PDFs having unhinted fonts—so I think that I would have noticed it, but if it's really as subtle as you say, then maybe I haven't.

I do have a somewhat unusual setup though: I'm currently using

$ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer','xwayland-native-scaling']"

although that might not be required any more with recent versions. I've also enabled full hinting and subpixel antialiasing with Gnome Tweaks, and I've set the following environment variables:

MOZ_ENABLE_WAYLAND=1
QT_QPA_PLATFORM=wayland
GDK_BACKEND=wayland,x11,*
CLUTTER_BACKEND=gdk,wayland
SDL_VIDEODRIVER=wayland
SDL_VIDEO_DRIVER=wayland
ECORE_EVAS_ENGINE=wayland_egl
ELM_ENGINE=wayland_egl
QT_AUTO_SCREEN_SCALE_FACTOR=1
QT_ENABLE_HIGHDPI_SCALING=1

So maybe one of those settings would improve things for you? I've randomly accumulated most of these settings over the years, so I unfortunately can't really explain what (if anything) any of them do.

> Yes, Chrome's entire window can be quite blurry if Xwayland is involved, but it now talks to Wayland by default

Ah, good to hear that that's finally the default; that probably means that I can safely remove my custom wrapper scripts that forced those flags on.
by overfeed | 2026-03-04 03:27:47+00:00
> Thinking no one leaves their house to work is some serious projection dude

>> I don't get why prosumers would marry themselves 24/7 to a single portable device...

I quite clearly was talking about personal devices; are you in the habit of buying computers for your employers? Or perhaps you carry your personal laptop to work. I do neither, excuse my projection if you do either of those things.
by josephg | 2026-03-04 03:27:52+00:00
> even when you need to do it and it's a couple hundreds mb taking a few minutes, it's tolerated.

Well written CRDTs should grow slower than git repositories.

> In situations where a document needs to be cold loaded often, the size of the document is felt more acutely.

With eg-walker (and similar algorithms) you can usually just load and store the native document snapshot at the current point-in-time, and work with that. And by that I mean, just the actual json or text or whatever that the application is interacting with.

Many current apps will first download an entire automerge document (with full history), then using the automerge API to fetch the data. Instead, using eg-walker and similar approaches, you can just download 2 things:

- Current state (eg a single string for a text file, or raw JSON for other kinds of data) alongside the current version

- History. This can be as detailed & go as far back as you want. If you download the full history (with data), you can reconstruct the document at any point in time. If you only download the metadata, you can't go back in time. But you can merge changes. You need history to merge changes. But you only need access to history metadata, and only as far back as the fork point with what you're merging.

If you're working online (eg figma), you can just download history lazily.

For client/server editing, in most cases you don't need any history at all. You can just fetch the current document snapshot (eg a text or json object). And users can start editing immediately. It only gets fancy when you try to merge concurrent changes. But thats quite rare in practice.
by bigyabai | 2026-03-04 03:28:43+00:00
Their point stands. People are just not going to daisy-chain these together for datacenter use. Apple does not take the workload seriously and macOS is not a suitable OS for mass deployment.

RDMA is the bare minimum we should expect from a system that doesn't support eGPUs and treats PCI like a foreign language. It's not a long-term solution and even Apple themselves cannot deny this: https://9to5mac.com/2026/03/02/some-apple-ai-servers-are-rep...