I spent most of the day getting comfortable with Guile and the basics of Guix services.
Followed the "perfect hacking setup" manual section (I'm lucky, I'm using Emacs). Geiser is okay-ish, but fails a lot of times (can't jump to definition in g-expressions for instance). Overall, the builtin yasnippets, and paredit are good and useful, geiser fails to jump to definition too many times to be really useful.
I have a fully functional sway/pipewire/xdg-desktop-portal setup. Costed me quite some headaches.
Guix home is super nice and definitely more integrated than home-manager.
I migrated ~60% of my laptop NixOS configuration. The remaining 40% are going to be pretty painful to migrate, Guix is currently lacking some features to do so (writers, secret management). I'll probably have to write the missing features to continue the migration, but I'm not comfortable enough with Guile/Guix to do so yet.
I packaged my first package (power-profiles-daemon) and wrote a service for that.
I really like the Guix service system. A lot more than the NixOS module system.
Tomorrow, I'll have to face my nemesis: mailing-list-powered patches. I'm 6 commits ahead of my Guix channel, it's time to reduce the stack and start cleaning/upstreaming the changes.
I'm not in love with Guile yet. Part of it probably comes from my inexperience, using it is still painful and slows me down a lot.
I hit a massive roadblock at some point: the guile error message was lying to me. I had a module with an error in it, and instead of throwing an error message, Guile was lying to me and telling me I was not loading this module, and giving me a hint explaining me how to load the module. But, I was already loading the module!! Gazlighted by the interpreter :D
Took me a good 2h before realizing the interpreter was lying to me. I need to find a minimal reproducer to send to the email list.
Massive kudos to @ekaitz_zarraga who helped me in the process :)
