MurphyA/hacker-news huggingface dataset:
by dathinab | 2026-03-11 17:23:01+00:00
this isn't wrong

but spelling and grammar still isn't a good indicator for expertise, intelligence or anything like that even in an academic context

Mainly:

1. Dyslexia doesn't make you dump, just likely to misspell and a less likely to notice your misspelling.

2. When speaking about neurodivergence people mainly think about Autism or ADHD but sometimes just mean that your brain thinks in very different patters, this can make grammar hard. Especially if it's not your native language.

3. Sometimes people had shitty situations earlier in their live, leading to incorrectly learning parts of languages. This is hard to fix. But isn't really representative in any way for their expertise in any topic which isn't the given languages grammar.

4. English grammar and pronunciation to spelling mapping aren't exactly well designed. People not wanting to bother with it is not really related to intelligence, or excellence in other topics.

5. Some kinds of expertise are unrelated to general intelligence, expertise, education. So even if spelling and grammar where related to intelligence, it wouldn't be meaningful to judge expertise.
by perfmode | 2026-03-11 17:23:04+00:00
The quality cliff question is the right one to be asking. There's a pattern in systems work where something that scales cleanly in theory hits emergent failure modes at production scale that weren't visible in smaller tests. The loss landscape concern is exactly that kind of thing, and nobody has actually run the experiment.

That said, I think the comparison to improving GGUF quantization isn't quite apples to apples. Post-training quantization is compressing a model that already learned its representations in high precision. Native ternary training is making an architectural bet that the model can learn equally expressive representations under a much tighter constraint from the start. Those are different propositions with different scaling characteristics. The BitNet papers suggest the native approach wins at small scale, but that could easily be because the quantization baselines they compared against (Llama 3 at 1.58 bits) were just bad. A full-precision model wasn't designed to survive that level of compression.

The real tell will be whether anyone with serious compute (not Microsoft, apparently) decides the potential inference cost savings justify a full training run. The framework existing lowers one barrier, but the more important barrier is that a failed 100B training run is extremely expensive, and right now there's not enough evidence to derisk it. Two years of framework polish without a flagship model is a notable absence.
by patchnull | 2026-03-11 17:23:14+00:00
This keeps happening across numerical computing. Abramowitz and Stegun is basically a cheat code that entire generations of developers forgot existed. I hit the same thing a few years back with a fast atan2 approximation buried in a 1971 naval research paper that turned out to be nearly identical to what a colleague spent two weeks deriving from scratch. The real problem is that modern CS education treats numerical methods as a solved problem delegated to libraries, so nobody learns to read the original tables and error bounds. Meanwhile game and graphics devs independently rediscover these approximations under deadline pressure and the knowledge stays siloed in engine-specific codebases instead of flowing back to the broader community.
by phickey | 2026-03-11 17:23:21+00:00
Real programs, whether native JavaScript or in any other language that targets Wasm, have concurrency. Would you rather the component model exclude all concurrent programs, and fail to interact with concurrent JavaScript? The component model is meeting the web and programmers where they're at. Unless you're one of the few people implementing the low level bindings between components and guest or host languages, you don't have to ever read the CM spec or care about the minutae of how it gets implemented.
by hyperfield | 2026-03-11 17:23:25+00:00
AI File Sorter: a cross-platform file organizer tool with GUI, which uses local LLMs to categorize and rename images, documents, media, etc (v1.7.0).

New in v1.7.0:

- redesigned the progress dialog for clearer progress tracking

- added metadata-based rename suggestions for audio/video files

- improved reliability and stability
by yomismoaqui | 2026-03-11 17:23:27+00:00
As a cheap user that only uses the 20$ month subscriptions I started with Claude Code as main & Codex as backup when the 5 hour quota was exhausted.

Then I saw that Codex worked better for me and cancelled my Claude Code subscription. And now for my moderate use (4-5 hours a day with no parallel agents) I have enough with Codex $20 and AMP free if I want to save some weekly quota.

But honestly I usually have enough usage to last the full week without using AMP.
by baileywickham | 2026-03-11 17:24:37+00:00
You're right that security is a major risk. Our perspective here is that by defaulting to an EC2 instance, you're in control of what data is at risk. If you connect Google Workspace, you are exposing yourself to some security risk risk there, but tons of users do email through AgentMail which doesn't have access to your personal data. Also no risk of filesystem access/Apple ID access by default.
by giancarlostoro | 2026-03-11 17:24:56+00:00
Yeah, for a while my favorite laptop was the Surface Book 2. Decent specs, does what I want it to. Then Microsoft started going through "Marketing Driven Development" for Windows and its just been downhill for my experience with that laptop. It's not just the marketing trash, the OS has gotten noticeably slow despite me keeping it pretty vanilla. It's downright insulting. As for my desktops, I just smoosh over Windows and install Linux over now, I don't care about anything on Windows enough to keep it. I can play all my games on Linux just fine. I can do all my dev stuff on Linux too.
by pizlonator | 2026-03-11 17:25:03+00:00
> I mean, you are obviously entitely to your opinion

I'm trying to explain to you why attempts to make wasm mainstream have failed so far, and are likely to continue to fail.

I'm not expressing an "opinion"; I'm give you the inside baseball as a browser engineer.

> Getting rid of the glue layer

I'm trying to elucidate why that glue layer is inherent, and why JS is the language that has ended up dominating web development, despite the fact that lots of "obviously better" languages have gone head to head with it (Java, Dart sort of, and now wasm).

Just like Java is a fantastic language anywhere but the web, wasm seems to be a fantastic sandboxing platform in lots of places other than the web. I'm not trying to troll you folks; I'm just sharing the insight of why wasm hasn't worked out so far in browsers and why that's likely to continue
by perfmode | 2026-03-11 17:25:33+00:00
This is the most interesting point in the thread to me. Tolerance stack-up is the reason tight per-part tolerances matter at all. A single brick being precise is table stakes for injection molding. The hard problem is what happens when you compose hundreds of them.
The decoupling strategy you're describing is really similar to how you handle error accumulation in any large composed system. You can't make individual components perfect enough to avoid drift at scale, so you introduce boundaries where the accumulated error gets absorbed rather than propagated. In Lego's case that means designing joints between sections that are forgiving enough to accommodate the stack-up from each chunk independently.

It's also why knockoff bricks can feel fine for small builds and then fall apart (sometimes literally) on larger ones. If your per-part tolerance is 3x worse, it doesn't matter much for a 20-piece build, but for a 2000-piece build your cumulative error budget is blown long before you're done. The failure mode isn't that any individual brick is bad, it's that the composition doesn't hold.

I'd be curious whether Lego publishes or talks about those chunk size design rules anywhere. That seems like the actually interesting engineering story, more so than the per-part tolerance numbers that get repeated in every article about them.
by yanitcorel | 2026-03-11 17:25:36+00:00
I'm currently working on a technical session around productionizing agentic AI systems on AWS.

A lot of demos work well in prototypes, but once you try running agent-based workflows in production you start seeing issues around orchestration, tool reliability, latency, and cost control.

So I've been putting together some architecture patterns and real-world approaches teams are using to make these systems more reliable in production environments.
by VanCoding | 2026-03-11 17:25:46+00:00
It's not that much about type safety. Since TypeScript uses duck typing, a DateTime could not be used as a ZonedDateTime because it'd lack the "timezone" property. The other way around, though, it would work. But I wouldn't even mind that, honestly.

The real drawback of the functional approach is UX, because it's harder to code and you don't get nice auto-complete.

But I'd easily pay that price.
by anonym29 | 2026-03-11 17:26:04+00:00
As a Strix Halo owner, I've been eagerly awaiting Nemotron 3 Super since it was announced for H1'26 when Nemotron 3 Nano dropped. It's humbling to watch the industry move so fast that Qwen 3.5 122B A10B ends up being competitive with this on benchmarks, though, which isn't a dig at Nemotron 3 Super as much as it a testament to Qwen 3.5's phenomenonal achievements.

Still, the NVFP4 benchmark numbers also look fantastic, which is enticing to me as I'm considering supplementig my Strix Halo rig with a GB10 rig as well, not to mention the YaRN-less 1M native context window and that gorgeous hybrid mamba architecture that scales exceptionally well into the deep context lengths that are unlocked with that 1M context window.

It's fascinating how far Nvidia has been able to push models trained entirely on synthetic data, though it makes me curious to see what the hallucination rate turns out to be - this is exactly what I thought we we're not supposed to be doing to avoid model collapse.
Show HN: Linggen – Open agent system in Rust, any model, file-based
by linggen | 2026-03-11 17:26:04+00:00
Linggen is an open-source agent system where agents, skills, and scheduled missions are all markdown
files. Drop a .md file, get a new agent.

- Multi-agent — agents delegate to each other, run concurrently. Message a running agent mid-task and it
adapts (cooperative interruption)
- Any model — Ollama, OpenAI, Claude, Bedrock, any OpenAI-compatible endpoint. Route per agent with
auto-fallback
- Skills as files — portable Markdown skills, compatible with Claude Code and Codex (Agent Skills
standard)
- Scheduled missions — cron-based autonomous tasks without human-in-the-loop
- Web UI + TUI + VS Code — all share real-time session state via SSE

Rust backend (axum, tokio, ratatui). React 19 frontend embedded via rust-embed. Native tool calling for
all major providers. Workspace-scoped file ops with per-agent permissions.

Early stage. The name 灵根 (Líng Gēn) means "spiritual root" in cultivation fiction — the innate
foundation that determines what you can become.

GitHub: https://github.com/linggen/linggen

curl -sSL https://linggen.dev/install.sh | bash && ling
by hnlmorg | 2026-03-11 17:26:18+00:00
That’s the same point the author was making. And it’s not just limited to descriptions. Record labels, track names, genre names, sometimes even DJ / artist names have taken their “acid” name from the distinctive sound of the TB-303.

Obviously it will depend on the era and scene too. Eg if people talk about acid in the 70s Prog Rock scene then it’s not going to be about a hardware synthesiser built a decade later. But if you’re talking about dance music, then “acid” refers to 303 more often than it does the drug.
by jerf | 2026-03-11 17:26:42+00:00
Even a retrodiction can be impressive and/or interesting if it is a sufficiently "nothing up my sleeve" [1] type of prediction. I don't know enough about this field and the article isn't informative enough for me to guess, but it's possible that they made a retrodiction where they didn't tune the parameters for it explicitly and got near the correct result directly. In that case, it would at least constitute some sort of clue, even if it isn't necessarily correct. Or they could have tuned the heck out of it and glossed over it in the article, I dunno.

[1]: https://en.wikipedia.org/wiki/Nothing-up-my-sleeve_number
by dekhn | 2026-03-11 17:26:43+00:00
Maybe nature and cell and a few other journals should be exceptions: they should be the place that the most advanced scientists publish interesting ideas early for the consumption by their competitors. At that level of science, all the competitors can reproduce each other's experiments if necessary; the real value is expanding the knowledge of what seems possible quickly.

(I am not seriously proposing this, but it's interesting to think about distinguishing between the very small amount of truly innovative discovery versus the very long tail of more routine methods development and filling out gaps in knowledge)
by eqrion | 2026-03-11 17:26:52+00:00
The concurrency part of the C-M is complicated (I think for inherent reasons), but won't be exposed to end users. It's basically defining an API that language toolchains can use to coordinate concurrency.

For end users, they should just see their language's native concurrency primitives (if any). So if you're running Go, it'll be go routines. JS, would use promises. Rust, would have Futures.
by salawat | 2026-03-11 17:27:03+00:00
It has been proven and blessed by SCOTUS that an email and continued use is sufficient cause to derive implied consent. Contracts are now essentially pointless in their one sidedness. Anyone pointing to contractual limitations as justification of their position to a third party should find that third party looking them dead in the eye and pointing out all it would take for the justifier to be "right" in this circumstance is changing your TOS long enough to prove your point to me, sending an email that will never be read, then as soon as I'm gone changing the terms back to whatever else and sending another email. By de-frictioning contract law to enable click-wrap and EULA, we've completely undermined the semantic intent of the mechanism; which was to be a durable statement of an agreement between two parties that both agree to be bound to. When there is no binding on the originating party from changing the terms, there is no assurance to anyone else the terms don't change from second to second to the benefit of the originator of the contract.

Sometimes, the friction is the feature.
by lab14 | 2026-03-11 17:27:18+00:00
> It's hard to take your argument of "removing capitalization has made my writing better" seriously when your comment history shows that you do capitalize your written text.

right, because i couldn't have adopted this writing style in the past few weeks.

to address your second point, i could probably make better use of punctuation, but the original message is still delivered without all the fluff IMO.
by MisterTea | 2026-03-11 17:27:23+00:00
> Huang contends that the AI boom will create a vast number of skilled, well-paid blue-collar jobs—such as electricians, plumbers, and steelworkers—rather than simply eliminating white-collar roles.

It appears that inside Huang's reality bubble lives a fantasy where we will build AI data centers in perpetuity. While in reality, the workers will be busy for the duration of the construction projects then furloughed. It's all temporary short term growth thinking where the only thing that matters is Nvidia's growth and by extension, Huang's ego.
by swiftcoder | 2026-03-11 17:27:29+00:00
> Until we all have government-issued public keys or something

That's actually pretty common in Europe. The Spanish DNI (national identity card) has a chip these days, which gives you an authenticated key pair for accessing digital services.

In the pilot project for digital voting, that identity is only used to authenticate the user, and then an anonymous key needs generated that can be used to cast the final vote.
by k310 | 2026-03-11 17:27:35+00:00
My brother, the least techie person on earth, got really sick and tired of windows updates breaking his drivers monthly, so he eventually got a Dell linux desktop, installed and supported (online only) and after a few questions about FOSS apps to do his common chores, I haven't fielded a question in ages.

There are always going to be niche things. Say, why not have it all, ( as in my above post)

That's why we have, as Napoleon Dynamite says: "Computer hacking skills".

You know, like nunchuck skills, bowhunting skills, computer hacking skills... Girls only want boyfriends who have great skills.
by mhendric | 2026-03-11 17:27:49+00:00
Author here. Neotoma has nothing to do with blockchain, at least for any foreseeable future. It's a structured memory layer for AI agents. Think: entity storage with relationships, provenance, and queryable state. No token, no chain, no crypto.

The whole point of the essay's ending is that I chose not to issue a token and instead shipped a developer release to collect real feedback from real testers.

The takeaway wasn't "blockchain bad," it was "feedback loops matter and token economics break them." Neotoma is built around the opposite approach: short cycles, real users, and no financial instrument that makes belief liquid.
by elliotlarson | 2026-03-11 17:28:01+00:00
I feel like this is a pretty big fumble for Anthropic. I don't mind waiting 30 minutes or so for a service that's having issues. But, around the 2 hour mark, I start researching alternatives. I think like almost every other developer I've been working on my own AI assisted project management system. It was built around Claude Code, but now I'm using my down time adding in support for Gemini and Codex.
by spopejoy | 2026-03-11 17:28:04+00:00
> I have described what bothers me about the writing

No you haven't, you've made an unprovable claim about how the writing was accomplished without pointing out a single feature of the writing itself.

Too long? OK, but homebrew gamedev articles often are. Skimming was a good skill before AI and still is.

Bad writing? Again -- hobbyist posts don't exactly win awards. I suspected possibly some AI myself but not to the extent you're baselessly asserting: I really doubt there was a single prompt in any case. The article is structured like any other.

If it were content-free clickbait or something, the complaint would hold water. As it is this is a reasonably interesting article that has generated a large and fun discussion on HN, so even if you _could_ prove AI use, so what?
by rivetfasten | 2026-03-11 17:28:27+00:00
Thanks for the post!

Question: While you would want any official arch built natively, maybe an interim stage of emulated vm builds for wip/development/unsupported architectures would still be preferable in this case?

Comparing the tradeoffs:
* Packages disabled and not built because of long build times.
* Packages built and automated tests run on inaccurately emulated vms (NOT cross compiled). Users can test. It might be broken.

It's an experimental arch, maybe the build cluster could be experimental too?
by mothballed | 2026-03-11 17:28:51+00:00
It's still bizarre though how this plays out in reality.

In some places like Illinois, an ID is required to exercise the rights of people but not the rights of citizens (FOID required to bear guns, but ID not required for vote).

In places like Arizona, it's the exact opposite. You can bear or conceal guns without an ID but you need an ID to vote.

Vermont is the only state I know of with any consistency on lack of ID requirements that convey non-ID citizens to also have the right of people. You can conceal guns and vote without ID.
by pmarreck | 2026-03-11 17:29:10+00:00
It IS their own work.

The simplest refutation of your point of view is, who or what is responsible if the work submission is wrong?

It will always be the person’s, never the computer’s. Conveniently, AI always acts as if it has no skin in the game… because it literally and figuratively doesn’t… so for people to treat it like it does, should be penalized
by Sesse__ | 2026-03-11 17:29:22+00:00
And similarly, entire generations of programmers were never taught Horner's scheme. You can see it in the article, where they write stuff like

A * x * x * x * x * x * x + B * x * x * x * x + C * x * x + D

(10 muls, 3 muladds)

instead of the faster

tmp = x * x;
((A * tmp + B) * tmp + C) * tmp + D

(1 mul, 3 muladds)
by recursive | 2026-03-11 17:29:33+00:00
Yes, you can mutate props. But no, it's probably not going to do what you want if you did it intentionally. If react added Object.freeze() (or deepFreeze) to the component render invoker, everything would be the same, except props would be formally immutable, instead of being only expected to be immutable. But this seems like a distinction without much of a difference, because if you just try to use a pattern like that without having a pretty deep understanding of react internals, it's not going to do what you wanted anyway.
by linggen | 2026-03-11 17:29:36+00:00
Author here. Built this because I wanted one system where I could drop a markdown file and get a new agent
— for coding, but also for scheduled code reviews, architecture checks, or anything else.

The file-based approach is the core idea. An agent is 15 lines of YAML + markdown. A skill is a SKILL.md
directory. A mission is a cron entry pointing at an agent. No SDKs, no plugins, no code changes — just
files.

Happy to go deep on the Rust runtime, multi-agent delegation, or anything else.
by mmooss | 2026-03-11 17:29:39+00:00
Phones (really, the pocket/handheld form factor) are a necessity and are limited; I agree. We could deliver better text input interfaces for them.

For heavy typers, physical keyboards in candybar phones (.e.g, old Blackberrys, etc.) and landscape-oriented clamshells fix many issues, but those are outre for some reason. Even on-screen UIs could be better. Just arrow keys to move to the cursor precisely would be a signficant improvement.
by maxglute | 2026-03-11 17:29:50+00:00
> completely uncharted water

Good thing with analogue toys like legos is you know your kid is playing with legos that is wiring X brain cells for Y skills, even if Y skills are deprecated in digital world. It's hard to say with current gen, there's screen time to try to shape behavior, there are occasional kids who are tech literate maestros which every generation has, but plenty of kids who rely on LLMs, can only finger type because they grew up with touch screens. We're in tech timeline where passive users, i.e. most kids are impressed by millennials who can write cursive and touch type, other kids build stuff that previously required teams of 100s of engineers.
by eloisant | 2026-03-11 17:30:06+00:00
They already cannibalized a lot of Linux users, developers mainly when they released MacOS X around year 2000.

Suddenly you could have a Unix, with pretty much the same CLI as Linux but without all the supported hardware/driver issues. Laptop sleep in particular was pretty finicky.

If MacOS didn't pick a Unix/BSD base, I'm pretty sure all the tech companies running Mac would be on Linux.
by david-gpu | 2026-03-11 17:30:10+00:00
Yeah, I once worked at a place where the compiler team was assigned the unpleasant task of implementing a long list of trigonometry functions. They struggled for many months to get the accuracy that was required of them, and when they did the performance was abysmal compared to the competition.

In hindsight, they probably didn't have anybody with the right background and should have contracted out the job. I certainly didn't have the necessary knowledge, either.