Readit Newssbt567 commented on Uv is the best thing to happen to the Python ecosystem in a decade emily.space/posts/251023-... · Posted by u/todsacerdoti
Have you found it easy to write rust modules with python interfaces? What tools do you recommend?
Many people use PyO3 for that
sbt567 commented on We rewrote the Ghostty GTK application mitchellh.com/writing/gho... · Posted by u/tosh
Indeed, but I'm curious about the second class of memory correctness issue he mentions:
> 2. All other memory issues revolved around C API boundaries.
Is this something Rust, or any other language, has the ability to prevent any more than any other language? Or once you introduce a C API boundary is it back to tools like Valgrind?
I vaguely remember that there is a new language that promises "Safety across FFI boundary", but can't recall the name
sbt567 commented on Why I'm Leaving NixOS After a Year? rugu.dev/en/blog/leaving-... · Posted by u/kugurerdem
I'm just starting my second attempt at using NixOS last week because suddenly, my SSD failed and I have limited amount of time to configure my second laptop to get to work. This time I don't think that installing Arch will be the best choice to get to the last state of my laptop as fast as possible (I'm using dotfiles management, but not all things can be automated). And I'm ready to try NixOS again.
The only thing that makes me confident this time, is that I can use LLM to help me. There is absolutely no way I could try Nix again without using LLM. The first attempt at using it just makes me anxious because of docs alone.
And what makes me stick using it? Nix-ld. I think embracing impureness and doing things incrementally will help alleviate the vertical learning curve that is Nix.
After all of this learning curve? I finally can see the rainbow that I can only dreamed of in the past.