Nice project. Quick technical question: how are cards shuffled and dealt?

Is the RNG fully server-side, and what source are you using (e.g. crypto-secure PRNG)? Also curious whether the shuffle is deterministic per hand or purely random each time.

In my experience, the value doesn’t really shift from “coding” to “architecture” — it shifts toward understanding constraints.

On platforms like macOS, a lot of architectural decisions aren’t about clean abstractions but about what the system actually allows you to do (WindowServer rules, accessibility APIs, focus behavior, sandboxing). LLMs can generate plausible code, but they don’t feel where the platform pushes back.

The hard part is still knowing which designs will collapse once they meet real OS behavior, not writing the glue code itself.

A legit use-case is long-lived but infrequently accessed sessions.

Think debugging, learning environments, or experiments where the hard part is recreating state, not paying for compute. A VPS can do it, but suspend/resume avoids either leaving it running or constantly rebuilding it.

I think this is mostly true functionally, but not experientially.

A VPS gives you persistent state, but it still assumes you’re willing to manage that state. The distinction here seems less about what’s possible and more about who carries the ongoing operational burden: the user or the service.

I've spent months building a proper window manager for macOS, and the fundamental problem isn't the UI — it's that macOS has no proper window management API.

Third-party apps have to use the Accessibility API, which was designed for screen readers, not window manipulation. Some windows simply refuse to be resized below certain thresholds, and there's no way to query the minimum size in advance. You request 500px width, get 800px back, no error.

The real question is: will Apple ever provide a proper public API, or will this remain a cat-and-mouse game with Accessibility permissions?