frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
1•edent•3m ago•0 comments

A BSOD for All Seasons – Send Bad News via a Kernel Panic

https://bsod-fas.pages.dev/
1•keepamovin•6m ago•0 comments

Show HN: I got tired of copy-pasting between Claude windows, so I built Orcha

https://orcha.nl
1•buildingwdavid•6m ago•0 comments

Omarchy First Impressions

https://brianlovin.com/writing/omarchy-first-impressions-CEEstJk
1•tosh•12m ago•0 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
2•onurkanbkrc•12m ago•0 comments

Show HN: Versor – The "Unbending" Paradigm for Geometric Deep Learning

https://github.com/Concode0/Versor
1•concode0•13m ago•1 comments

Show HN: HypothesisHub – An open API where AI agents collaborate on medical res

https://medresearch-ai.org/hypotheses-hub/
1•panossk•16m ago•0 comments

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•19m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•19m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•19m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•19m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
3•juujian•21m ago•2 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•23m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•25m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
2•DEntisT_•27m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
2•tosh•28m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•28m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•31m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
5•sakanakana00•34m ago•1 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•36m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•37m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•38m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
4•Nive11•39m ago•6 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•42m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
3•chartscout•45m ago•1 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•48m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•49m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•54m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•56m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•58m ago•0 comments
Open in hackernews

Ubuntu 25.10 Replaces GNU Coreutils with Rust Uutils

https://www.altusintel.com/public-yych08/
30•donnachangstein•9mo ago

Comments

JonathonW•9mo ago
This reads like AI spew, and it's also not news (the post announcing this initiative [1] is from March).

[1] https://discourse.ubuntu.com/t/carefully-but-purposefully-ox...

tuananh•9mo ago
Does GNU coreutils have that many CVE?
carlmr•9mo ago
I wouldn't say many, but not none: https://app.opencve.io/cve/?vendor=gnu&product=coreutils

The question is rather how many are logic bugs and how many are memory safety bugs, Rust excludes the latter quite well, which according to the MS and Google Studies makes up about 70% of programming mistakes in their C++ codebases. However rewriting carries the risk of introducing new logic bugs. So There's a tradeoff here.

I am a big believer in Rust, I basically only use rg instead of grep and fd instead of find and never looked back, but they are slightly different in behavior, so not a drop-in replacement. I'm not sure if porting coreutils will be so useful in the end, since if you do all the workarounds for the rust version to behave like the C version, maybe you won't have the performance benefits or the clean codebase that you set out for in the end. I like the rg and fd approach much better. It's an almost drop-in with huge performance benefits.

But let's see if they succeed.

ozgrakkurt•9mo ago
Do you have a source for “70% of programming mistakes ..” part? I was looking for this but couldn’t find it
AndrewDucker•9mo ago
https://www.zdnet.com/article/microsoft-70-percent-of-all-se...
ozgrakkurt•9mo ago
This says security, so it doesn’t indicate anything about percentage in all programming errors
carlmr•9mo ago
That is actually slightly different. I guess I misremembered this. Probably a good question is also how quantifiable other bugs than security vulnerabilities are. Security vulnerabilities are probably the only measurable bugs in that sense, since they are analyzed for root cause and listed consistently. While other bugs can often be explained away and are harder to get numbers for.

In any case the question was about CVEs in coreutils so it's still somewhat relevant.

temp0826•9mo ago
Does this fix something specific with coreutils (is there no way to upstream patches?)? Or is it that rust is supposed to save us from some class of unknowns (related to memory safety?)?
diegocg•9mo ago
The world is slowly but steadily going to replace non memory safe code by memory safe code (no matter how people feel about it). This is just part of that.
flumpcakes•9mo ago
It seems like replacing code that has been written and used extensively for decades with a complete rewrite without a real need is more of a risk to me. Perhaps the uutils are 'simple' enough not to be an issue though.
carlmr•9mo ago
I think the simplicity is maybe why this is a good first experient. I think we can learn from it, more than it being useful on its own.

A lot of code will need to be replaced by memory safe code in the future, but a lot of code is not so easy to replace as something like this.

diegocg•9mo ago
Replacing non memory safe code is good. Rewrites are unstable at first, then time passes and bugs are fixed and is no longer that
lionkor•9mo ago
That's the worst idea I've seen in a while. People rely on the behaviors of the GNU coreutils, this is going to break a lot of stuff. The uutils are not there yet at all.
whatagreatboy•9mo ago
I think this is a good experiment. 25.10 is not an LTS, people who want stability are using LTS anyway.
TickleSteve•9mo ago
Correct me if I'm wrong but the next LTS will be 26.04 which would give them 6 months to get maturity and stability... For such an important set of utilities, that seems unlikely.
matheusmoreira•9mo ago
And one day people will rely on the behaviors of other things. There's no reason those things can't be these Rust utilities, they just need feature parity. Hopefully they will surpass their GNU equivalents. They'll probably be easier to contribute to as well.
turtleyacht•9mo ago
If this rewrite is indicative of other rewrites, we'll see a license change from GPL [1] to MIT.

"Differences with GNU are treated as bugs." - https://github.com/uutils/coreutils#goals

That's promising. Wouldn't it be annoying though, to have to keep things bug-for-bug compatible on a green-field project? That priority may be the first compromise, and divergence is inevitable.

(If few report edge cases and there's no fuzzing.)

[1] https://github.com/coreutils/coreutils?tab=GPL-3.0-1-ov-file

polycaster•9mo ago
> The replacement will affect more than a hundred utilities that are part of Coreutils

…

> Last week, the issue of the package uutils coreutils 0.0.30 successfully passed 507 tests (in the last issue of 506, in a year old – 476) from the standard GNU Coreutils test set.

If I’m reading this right then there are on average only one to five tests per utility (like cat, dd, …) which is a shockingly low number. Particularly when you consider how many options a single command alone might accept. And of course, this alone would not even remotely cover a critical part of all the circumstances that might vary.

miohtama•9mo ago
Many of those were written in 80s, testing was not a thing.
polycaster•9mo ago
Yes, I remember. It still shows me how I overestimated the maintenance work distributors do / can do. My unreflected expectation was that in the past 40 years test were developed to secure the very foundation we keep on building on since then.
WhereIsTheTruth•9mo ago
I'm glad I no longer depend on Ubuntu

https://news.ycombinator.com/item?id=43313214