Back when I did IBM 370 BAL Assembly Language, we did the same thing to clear a register to zero.
XR 15,15 XOR REGISTER 15 WITH REGISTER 15
vs
L 15,=F'0' LOAD REGISTER 15 WITH 0
This was alleged to be faster on the 370 because because XR operated entirely within the CPU registers, and L (Load) fetched data from memory (i.e.., the constant came from program memory).
It's baffling tha[t] after 59 years , Unix is still stuck in a weird directory naming structure inherited from the the late 60s that no longer make[s] sense when nobody has floppy drives.
I don't know about you. A common namespace composed as a tree makes sense to me. Splitting of user data makes sense to me. Splitting data from code executable code make sense to me. Splitting configuration from other data does. So does splitting code into executables and libraries, splitting into per machine/shared, and splitting into core OS and other (now reversed). The actual names don't matter all that much, but they are short and standardized so we use them.
What do you find weird about the directory naming structure?
We need to have death penalty--or at least life in prison without parole--for people who buy stolen copper. It's appropriate: copper theft puts lives in danger.
How do I prove where I got my copper from?
I can tell you why all of these things are bad ideas. They are bad ideas because you are outlawing legal commerce.
Copper has value. If people have this copper in their garage they can then get some value. The copper then goes back into the economy. Win Win. However if there is no gain to recycling it it might not quickly end up back into the economy. This is of course bad.
A totally radical view is to simply outlaw stealing :)
Laws on cars vary. It is common that cars can be sold for cash without any contract transfer. Same with guns but less so.
However are you saying that someone selling some extra scrap copper is in any way similar to someone selling their gun? These things are somehow equivalent?
However I will show you the actual connection.
What you are doing is making the law abiding citizen be punish for the crimes of the criminal. This happens with fire-arms legislation as well.
The result tends to of course be that citizens lose rights while criminals do as they have before.
This is not a world I want to live in and I hope you would not want this either.
This has been discussed ad nauseam and this adds nothing new. There's value in the memory safety for the majority of the code even if there are some escape valves ("unsafe" keyword, assembly).
There are no programs written in 100% safe Rust—the std library is written with unsafe as needed. But typically the majority of lines in the program—sometimes even all outside std or some well-audited foundational creates—are safe. Those lines can not directly cause any unsoundness, which has tremendous value.
reply