Idris is a proof assistant, Iris is a datalog implementation that is often used in proofs around separation logic. I'm not sure there is huge overlap in users, but they are both fun tools!
Please do write up something on your approach to comments! I'm sad that I missed the stream. I just wanted to point out an idea that blew my mind recently. Kris Jenkins on Developer Voices interviewed Agnès Leroy who described doing calculations on encrypted data and outputing encrypted answers. Some stuff is just magic. Thank you for what you do.
The better solution to unsafe_op_in_unsafe_fn warning would be to have a different keyword for each context - an unsafe function is about marking the function unsafe to callers, whereas using unsafe on a code block is about agreeing to uphold the safety contract. They shouldn't be using the same keyword - that was the real mistake, and this new edition skirts it entirely. At least it doesn't make things worse. Thinking some more about it, and seeing the use of the "safe" keyword for "extern", I realise now that the correct keyword to mark a function or block that is unsafe as being safe is, of course, "safe". Only it's not, so I guess we're stuck with double-duty "unsafe" for code we think is safe to call, and code that is not safe to call.
Happy new year! Regarding NixOS, I have it running on my home server and my home coding desktop. For the server having one config file is great. Getting a Gitea registry going is as simple as services.gitea.enable = true. However, on my coding machine, getting editor plugins to work nicely with the strictly defined config file was pretty annoying. Sometimes I just want to update with Cargo, or flatpak and not deal with the configuration.nix file. On my coding laptop I just installed Debian and nixpkgs and like that experience more.
it sure does add friction to updating/installing stuff sometimes. Well, except when what you want is already packaged - there's no better feeling than just running `nix-shell -p` and being good to go. Regarding editor plugins, I just don't bother with Nix at all there, and do everything "dirtily" with a conventional plugin manager - though I do still try to burn mason with fire and add the LSPs/formatters etc. to flake.nix for the rare cases when I need to use something other than Rust
At 1:49:30 - I think there may be a typo in the chapter marker. Thoughts rather than though ...? HTH (I think I saw the part where env was going to be marked as unsafe around here and thought hmm - credentials for things like DB connections could be impacted and that's one that really shouldn't be in version control systems for obvious reasons)
“Somebody is going to build tech for war so it might as well be me”, or something along those lines, is a terrible argument. You have the privilege and opportunity to work wherever you want, in whatever field that interests you, and clearly you choose to work for a military company because you are interested in making weapons. You can’t hide behind “I’m doing this for the greater good”. You choose to work there, so you are part of the industry. Your country is not under attack. I think you should simply admit that you find weapons fascinating and enjoy working on them. I personally would respect you more if you just owned it. However I still think it reflects poorly on you to voluntarily work in this field without an existential threat upon you. I speak as someone who has been in this position myself and I actively rejected the opportunity. Someone else can have that on their conscience. However if my country was attacked, I would work to defend it, of course.
But that's simply false - I'm not "interested in making weapons", nor do I particularly "enjoy working on them". I think it's naive to say that *if* your country was attacked, then you'd be willing to work in this kind of technology. At that point it's likely too late. Deterrence and invasion stopping are both meaningful preventative steps to avoid getting to the place where what you hold dear has already been infringed upon. And while you may not think so, I very much think of the current situation in Europe as under threat, which further raises the impetus for getting involved now rather than reactively later.
glad to see you are back!
Great video! Thanks a lot
The thumbnail 😅
It does matter. According to my ex, at least
1:25:00
Hello Jon! good to see you again! :)
So happy to see you back Jon! We need more videos from you 😃
Im new here, and i really enjoyed Q&A. Looking forward for your content, where i starve to learn.
Idris is a proof assistant, Iris is a datalog implementation that is often used in proofs around separation logic. I'm not sure there is huge overlap in users, but they are both fun tools!
As always a really interesting Q&A session.
Please do write up something on your approach to comments! I'm sad that I missed the stream. I just wanted to point out an idea that blew my mind recently. Kris Jenkins on Developer Voices interviewed Agnès Leroy who described doing calculations on encrypted data and outputing encrypted answers. Some stuff is just magic. Thank you for what you do.
The better solution to unsafe_op_in_unsafe_fn warning would be to have a different keyword for each context - an unsafe function is about marking the function unsafe to callers, whereas using unsafe on a code block is about agreeing to uphold the safety contract. They shouldn't be using the same keyword - that was the real mistake, and this new edition skirts it entirely. At least it doesn't make things worse.
Thinking some more about it, and seeing the use of the "safe" keyword for "extern", I realise now that the correct keyword to mark a function or block that is unsafe as being safe is, of course, "safe". Only it's not, so I guess we're stuck with double-duty "unsafe" for code we think is safe to call, and code that is not safe to call.
Happy new year!
Regarding NixOS, I have it running on my home server and my home coding desktop. For the server having one config file is great. Getting a Gitea registry going is as simple as services.gitea.enable = true. However, on my coding machine, getting editor plugins to work nicely with the strictly defined config file was pretty annoying. Sometimes I just want to update with Cargo, or flatpak and not deal with the configuration.nix file. On my coding laptop I just installed Debian and nixpkgs and like that experience more.
it sure does add friction to updating/installing stuff sometimes. Well, except when what you want is already packaged - there's no better feeling than just running `nix-shell -p` and being good to go.
Regarding editor plugins, I just don't bother with Nix at all there, and do everything "dirtily" with a conventional plugin manager - though I do still try to burn mason with fire and add the LSPs/formatters etc. to flake.nix for the rare cases when I need to use something other than Rust
At 1:49:30 - I think there may be a typo in the chapter marker. Thoughts rather than though ...? HTH (I think I saw the part where env was going to be marked as unsafe around here and thought hmm - credentials for things like DB connections could be impacted and that's one that really shouldn't be in version control systems for obvious reasons)
At 1:30:00 you mentioned about teams without metrics. Which metrics are you are actually referring to? Could you provide any examples?
I think you missed timestamp for 2:41:20 - "What is missing in Rust?"
Thanks! Should now be fixed.
your link to wewerewondering is malformed ...
UA-cam is so bad at links... Should be fixed now!
@@jonhoo 👍
Nix certainly has some dark corners. But there definitely isn't anything better.
Guix but Guile is a weirder language than Nix.
Where are your glasses? You don't seem to wear glasses for a while.🤓
3:27:30
“Somebody is going to build tech for war so it might as well be me”, or something along those lines, is a terrible argument. You have the privilege and opportunity to work wherever you want, in whatever field that interests you, and clearly you choose to work for a military company because you are interested in making weapons. You can’t hide behind “I’m doing this for the greater good”. You choose to work there, so you are part of the industry. Your country is not under attack.
I think you should simply admit that you find weapons fascinating and enjoy working on them. I personally would respect you more if you just owned it. However I still think it reflects poorly on you to voluntarily work in this field without an existential threat upon you.
I speak as someone who has been in this position myself and I actively rejected the opportunity. Someone else can have that on their conscience. However if my country was attacked, I would work to defend it, of course.
But that's simply false - I'm not "interested in making weapons", nor do I particularly "enjoy working on them". I think it's naive to say that *if* your country was attacked, then you'd be willing to work in this kind of technology. At that point it's likely too late. Deterrence and invasion stopping are both meaningful preventative steps to avoid getting to the place where what you hold dear has already been infringed upon. And while you may not think so, I very much think of the current situation in Europe as under threat, which further raises the impetus for getting involved now rather than reactively later.