HN user

Nezteb

552 karma

Too many LLM accounts on HN.

I'm leaving.

Posts15
Comments156
View on HN

I thought so too, although treating everything as data and functions is really nice [1].

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...

MacBook Pro Insomnia 12 months ago

From `man pmset`:

    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.

Depending on the definition of "nicely", FWIW I currently run Ollama sever [1] + Qwen Coder models [2] with decent success compared to the big hosted models. Granted, I don't utilize most "agentic" features and still mostly use chat-based interactions.

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...

Agreed!

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.

Yeah this was the part I found a little silly, mostly because I just couldn't visualize what that mesh looked like or how I would describe how to operate it.

Which features specifically? I can't find a conclusive list anywhere. Other than searching GH issues for bugs like: https://github.com/containers/podman-compose/issues/655#issu...

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.

Interesting; I have yet to run into any issues with it. Teams I work with mostly use it for local development/testing and do actual deploys using Kubernetes, so we don't use Docker Compose for deployments that utilize features unavailable in Podman Compose.

I'll try to do some more testing between the two and edit my original comment with my findings!

Protip: if you want to use Podman (or Podman Desktop) with Docker Compose compatibility, you'll have a better time installing podman-compose [1] and setting up your env like so:

  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