I run Guix System on my personal laptop and Project Bluefin on my work machine.
Guix is even easier to get started with now thanks to the Guix Packager , a web UI for writing Guix package definitions.
Project Bluefin auto-updates thanks to its use of container images deliver system updates. It's also just a great platform to get started writing containerized apps, since it ships with rootless Podman by default and you can easily add new developer tools using just commands.
I deeply love the story of Grendel. He's left an invisible imprint on me since I was a young boy fishing issues from my father's oversized trunk that squatted tempestuously in our living room. Thank you for this summary! I learned a few things I hadn't known.
For those who grew up with Grendel and now work in tech, like me, I did a talk on mindfulness and conflict in the workplace using the leitmotif of Grendel. Matt Wagner was kind enough to allow me to use his art for the talk.
The Intel discrete cards are fantastic value for money. There's plenty of folks on the internet who can attest to this. Intel's support story in general (so not just graphics cards) on Linux has been nothing less than sterling. If you're using any Linux kernel you can expect Intel stuff to just work. It's been this way for at least a decade.
WebOS powers TVs now and, from the article, Amazon intends this replacement to cover their Fire tablet line. WebOS ticks all their boxes, especially since apps in Amazon's new flavor are intended to be delivered as React Native web apps.
I'm devastated they didn't choose to pick up webOS for this.
For something simple that just needs a bind mount like
services:
app:
build:
context: .
target: base
volumes:
- ./debaser_studio:/opt/app-root/src/debaser_studio/debaser_studio
ports:
- "3000:3000"
- "8000:8000"
user: default
I haven't found any issues. Do you have more complex needs?
I use Logseq for everything. I've found the more you throw into it the more useful it becomes since your touch points are so frequent and that gets you thinking through and exploring your graph more. I've yet to use any of the data query features but I've heard they're incredibly powerful.
Whiteboards are just a fantastic way for modeling a topic or themes you know you want to turn into a deliverable when the how is uncertain.
Now that I've finished the first draft of an article on setting up rootless Podman on Guix System, I'm using and building out a set of tools to support a new article covering an all Red Hat stack from inner loop to CI.
So far, it's
I did a little research and found a Redditor who was able to answer better than me:
Logseq makes it easier to work with blocks, transclusions can be edited in place, and you can automatically be building another page consisting of blocks you’re writing in your daily journal or another page.
EDIT: I was really curious about the major differences and what is enabled by Logseq's block-based architecture so I asked my network on Mastodon and got some great answers!
Some folks may not know this but Logseq has a built-in whiteboard feature too that's also FOSS. I use it all the time to mind-map new blogposts and newsletters.
In Logseq the starting page is always the journal page for the day. This allows you to build up content without worrying about where it should go. Once you have something you feel you can run with, then you can move it to its own page.
EDIT: more features enabled by Logseq's block-based (bullets) architecture over on Mastodon.
The original EverQuest theme song was mine. Captured the epic wide-eyed wonder of going on an adventure perfectly.