HN user

LtWorf

2,495 karma
Posts6
Comments3,374
View on HN

I marked all my project on github as closed and added a link to the codeberg one.

After years google will still link to github anyway.

I had thought of just keeping them open and sync them, but I thought in that case people would presume the project is actually active on github and try to interact creating issues and pull requests and getting frustrated.

I must say codeberg's reliability isn't the best, but with all the scrapers that hit them it's a miracle they do seem to manage. And at work things on our private network without scrapers aren't more reliable.

So you haven't understood the distinction or you're letting your feelings for software get the best of you.

The proof that there are no (for rust's definition of "no") memory bugs becomes worthless, not the entire software itself.

An "unsafe" in rust is like an axiom in mathematics. You can use to prove higher level theorems but it has to make sense.

The second that you start to introduce nonsensical axioms (or bugs in unsafe sections) all your proven correct theorems will be worthless.

For a company that solved coding and doesn't need any software engineers… why spend money to acquire a runtime rather than ask claude to rewrite it in assembly directly and be done with it?

Could it be that they aren't being entirely honest?

I don't think you can claim your code is secure, or can claim anything at all about your code, if you haven't written the code and have no idea what's in there.

Rust protects against a rather small group of memory error, if and only if the unsafe sections are actually correct. And nobody knows if they are correct or not, plus there can be millions of logical errors that can be exploited.

See how many CVEs uutils has… quite a lot for a supposedly secure rewrite of GNU coreutils.