After fighting an series of odd issues on cuirass.genenetwork.org, I'm happy to announce we are back online, building packages and serving substitutes!
One of the things with mailing list driven workflow (in Guix and RDE) bothering me is that I can't review and merge patches without downloading emails, applying patches locally, signing them and pushing them to repo.
However, for most version bumps and other trivial changes it must be much more convinient, just one button click away. If it was so, it would be much less stale and forgotten patches I guess.
@abcdw They do a better job, except when the committer is required to sign commits, as is the case in Guix; in that case the forge still leaves it up to the committer to perform the last actions.
and just like that you have a dsl for any lisp in your scheme file, because its all just s-exps at the end of the day. and optionally you have an escape hatch.
i could write elisp configs in a .scm file, and i wont have to use guile-emacs (which is mostly dead due to only having a single dev)
and get this nix users, its not string interpolation. changing whitespace wont cause a recompile. its magical.
Today I converted almost a hundred transactions from bank statement to plain text ledger format using LLM in a few dozens of minutes and it made only two minor mistakes.
If I do it manually it would take a couple hours at least and whole a lot more of my energy.
Despite the all criticism it's a quite powerful tool for some categories of tasks.
I'm looking forward for more energy-efficient, FOSSy and local/self-hosted implementations.
@abcdw txr is quite handy for this sort of task. Unfortunately, you do have to remember txr which is extremely powerful and that can take some time. However, Kaz did write lots of examples and has been very responsive to answering questions about it.
I've spent the whole week walking through the forests, mountains and seasides. I took shower and washed in mountain rivers, swam in cozy bays, was chilling in hammock and reading a book, cooked on the tiny 25g titanium gas stove.
No rush, no tasks, no responsibilities. Found a water, found a place to sleep, have enough food left - good. I went through the memories, thought about past a future, lived in the moment. It was really good.
Studies, dayjob, competitions, someones birthday, whatever. I have never had time solely for myself. This one was for me.
I didn't get enlightened or something, but it was wonderful. I wish more people could have an opportunity to do the similiar things and live there lives.
I've spent the whole week walking through the forests, mountains and seasides. I took shower and washed in mountain rivers, swam in cozy bays, was chilling in hammock and reading a book, cooked on the tiny 25g titanium gas stove.
In the conversation about #guix sustainability I've talked a few times about Clojure Together which I think is a great example of "making things happen" (originally by just one person Daniel Compton) in a small community. Clojure is a small community compared to Python/Rust or whatever - but this project has been great for the Clojure community - recognising, supporting and sustaining improvements. Could equally apply to #guile#scheme
In the conversation about #guix sustainability I've talked a few times about Clojure Together which I think is a great example of "making things happen" (originally by just one person Daniel Compton) in a small community. Clojure is a small community compared to Python/Rust or whatever - but this project has been great for the Clojure community - recognising, supporting and sustaining improvements. Could equally apply to #guile#scheme
The work that you have done with RDE and arei and ares, along with the Spritely Institute are the main reasons why I am excited about using Guile for my stuff.
It is easy to focus on the gaps and issues associated with Guile but, ultimately, when using programming languages, a very big factor is the company we keep and the community we build.
I find you, Christine, Dave, and many others inspiring,
I have started working on an interactive debugger for Guile. Still at a very early stage. But here is a small demo. Thanks to Andrew Tropin (@abcdw) for guile-ares-rs and arei, which serve as the foundation for this tool.
What if we use number of days we didn't reply for each email in our inbox instead of just number of emails?
The obvious problem I have right now that I prefer to reply to the recent emails to keep the inbox number low, but it makes old emails to stay here for months.
@abcdw The problem with going round robin is that replying to an old email often takes way longer, because it's less likely to be about the most recent thing you were working on or thinking about, so you have to switch gears.
Also, there's a good chance that the subject of the old email has either worked itself out, or blown up (in which case you have newer emails about it.)
I finally found what can be worse than 10k forest run in the morning: it's 12k run with ultra trail running girl 😃 In the second part of the run I wanted to vomit and lay down in embryonic pose at the same time.
After that we jumped into a freaking cold mountain river and swimmed for a couple minutes.
Nevertheless, it is a good start of the day, I worked quite hard and was keeping focus relatively easy today. Also, my legs hurt much less than they were before run. It's Yoga cool down I guess?
Is there an #API#documentation where all procedures and macros are listed or searcheable for #guilehoot? I was looking for `procedure->external` today and had to peek into the source code (not for the first time). A searcheable index would be handy.
Fully-declarative deployment of 2-nodes Kubernetes cluster :kubernetes: successfully done with Guix :guix:!
The only manual step was generating a worker token to connect a worker kubernetes node to the controller and copying it to the respective host. It can be automated, but not today.
@abcdw Sounds awesome - hard to see exactly whats going on fully just in that screenshot - would love to see a short video going thru what you've got working here.