Immoral boot-licking human engineers are indistinguishable from LLMs.
552 karma · joined September 6, 2016
I'm leaving.
Immoral boot-licking human engineers are indistinguishable from LLMs.
Do you have sources for this claim?
I hope this was sarcasm.
Regarding the BEAM and why Gleam has a separate library for actors: [2]
> "One notable difference between Elixir and Gleam is that Elixir gets to just re-use the OTP code as-is (with some Elixir wrappers on top for convenience). Gleam concluded that the OTP is built expecting dynamic types, and that for best results in Gleam they'd need to re-implement the key primitives. That's why the example shown is an "Actor" not a GenServer - it serves the same purpose, and might even fit in a Supervision tree, but isn't actually a GenServer."
There's a brief snippet mentioning this in the Gleam OTP readme as well: [3]
> "Actors do not yet support all OTP system messages, so some of the OTP debugging APIs may not be fully functional."
[1] https://mckayla.blog/posts/all-you-need-is-data-and-function...
[2] https://news.ycombinator.com/item?id=40645489
[3] https://github.com/gleam-lang/otp#limitations-and-known-issu...
[1] https://en.wikipedia.org/wiki/Esperanto_vocabulary#Cultural_...
[2] https://en.wikipedia.org/wiki/Esperanto_profanity#Neologisms
SAFE SLEEP ARGUMENTS
hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets
written is also dependent on the values of standby and autopoweroff
For example, on desktops that support standby a hibernation image will be written after the
specified standbydelay time. To disable hibernation images completely, ensure hibernatemode
standby and autopoweroff are all set to 0.
hibernatemode = 0 by default on desktops. The system will not back memory up to persistent
storage. The system must wake from the contents of memory; the system will lose context on
power loss. This is, historically, plain old sleep.
hibernatemode = 3 by default on portables. The system will store a copy of memory to
persistent storage (the disk), and will power memory during sleep. The system will wake from
memory, unless a power loss forces it to restore from hibernate image.
hibernatemode = 25 is only settable via pmset. The system will store a copy of memory to
persistent storage (the disk), and will remove power to memory. The system will restore from
disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery
life, you should use this setting.
Please note that hibernatefile may only point to a file located on the root volume.The server is basically just my Windows gaming PC, and the client is my editor on a macOS laptop.
Most of this effort is so that I can prepare for the arrival of that mythical second half of 2026!
[1] https://github.com/ollama/ollama/blob/main/docs/faq.md#how-d...
[2] https://huggingface.co/collections/Qwen/qwen25-coder-66eaa22...
If you usually aren't able/allowed to use a debugger in production and must rely on observability tools, it's helpful to know how to utilize those tools locally as effectively as possible when debugging.
The output is pretty non-sensical: https://pastebin.com/raw/hetAvjSG
I use a combo of xbar [1] and Menubarx [2]. I used to have several widgets just for system stats but eventually moved to mac-stats [3] for that.
As someone who has also use GSAP a decent amount, these days I usually have a better experience with SVG.js [1].
RE debugging spam, the only thing I can think you're referring to can be turned off by setting `export PODMAN_COMPOSE_WARNING_LOGS=false`.
I'm also curious how it doesn't adhere to the spec. I don't doubt you, but it'd be cool if there was a test suite or audit tool that could document that.
I'll try to do some more testing between the two and edit my original comment with my findings!
alias docker=podman
# If you want to still use Docker Compose
# export PODMAN_COMPOSE_PROVIDER=docker-compose
# On macOS: `brew install podman-compose`
export PODMAN_COMPOSE_PROVIDER=podman-compose
export PODMAN_COMPOSE_WARNING_LOGS=false
Most of my initial issues transitioning to Podman were actually just Docker (and Docker Desktop) issues.Quadlets are great and Podman has a tool called podlet [2] for converting Docker Compose files to Quadlets.
I prefer using a tool like kompose [3] to turn my Docker Compose files into Kubernetes manifests. Then I can use Podman's Kubernetes integration (with some tweaks for port forwarding [4]) to replace Docker Compose altogether!
[1] https://github.com/containers/podman-compose
[2] https://github.com/containers/podlet
[3] https://github.com/kubernetes/kompose
[4] https://kompose.io/user-guide/#komposecontrollerportexpose