Good on ya.
emr
The Internet Archive would be the usual place.
On a superficial level it's a lot nicer than Ada for people who didn't learn to program on Pascal. Rust's real flaws don't show up until you need to do large refractors and change your application's memory model.
By litigate I mean, if a person is creating something and says they don't plan to distribute it, do we take their word for it?
If it ends up getting distributed anyway, should we take their word that it was an accident?
We consider people's private data important enough that if you leak it even by mistake you are on the hook for that. You have a responsibility.
I think that rather than framing this as something harmless unless distributed and therefore intent to distribute matters, we should treat it as something you have a responsibility not to create because it will be harmful when it is inevitably distributed.
How do you litigate 'intention' in this way?
Good read. I'd add one more reason: write a post to document something. Might help someone else in the future, might not, but if you ever need to refer back to it, it's going to help you!
Well it sets an upper bound on compute requirements at 'simulate 10^27 atoms for thirty years' remains to be seen if what we can optimize away ever converges with what's feasible to build.
It would become Twitter.
Can't wait for the bots to tell us what they learned about b2b marketing!
I'm so hype for typed dictionaries
The... what?