Hacker News: dangistan202611

New comment by dangistan202611 in "Show HN: Waymark – A workflow engine that compiles jobs instead of replaying"

dangistan202611 — Sat, 07 Nov 2026 15:59:58 +0000

> having to deal with their synchronization

No such thing is typically necessary. If modeled correctly, the need for synchronization is minimal.

With sync code, tasks run on different threads/interpreters/processes. Message passing via queues is used to communicate which tasks need to run. Many asyncio users seem to wholly unaware of how well it works. Go-lang doesn't even have or need async.

I actually like asyncio; I am just not a religious zealot about it as many here seem to be, also without awareness of the struggles they face with loop-hogging coroutines and multicore parallelism.

New comment by dangistan202611 in "Show HN: Waymark – A workflow engine that compiles jobs instead of replaying"

dangistan202611 — Sat, 07 Nov 2026 00:55:52 +0000

Huh. I hate neither async nor systemd. There is nothing wrong with async, but if my code is sync, what am I to do?

Also, the claim made that something is "better modeled as async" is wholly unqualified.

New comment by dangistan202611 in "The Ubuntu 26.04 Rust sudo is not compatible with standard sudo"

dangistan202611 — Fri, 06 Nov 2026 23:49:33 +0000

Before you know it, you will be needing a workaround for every replacement tool you use in Ubuntu. This is what makes it unacceptable.

New comment by dangistan202611 in "Show HN: Waymark – A workflow engine that compiles jobs instead of replaying"

dangistan202611 — Fri, 06 Nov 2026 23:38:08 +0000

This looks like something that will break easily with a newer version of Python or even with the use of third-party packages. It seems to couple too tightly with the user's application code.

New comment by dangistan202611 in "Show HN: Waymark – A workflow engine that compiles jobs instead of replaying"

dangistan202611 — Fri, 06 Nov 2026 23:11:28 +0000

I dispute the "better" assertion. Anyhow, I don't know how familiar or not you are with sync code, but it fully supports background jobs using queues with threads/interpreters/processes. It has been around for decades, far longer than async.

Also, it is okay to run something in the foreground. Not everything needs to run in the background. Sometimes it's better to wait and have assurance of completion.

There is no natural parallelism of async code in Python. The coroutines run in a single thread.

New comment by dangistan202611 in "Show HN: Waymark – A workflow engine that compiles jobs instead of replaying"

dangistan202611 — Fri, 06 Nov 2026 22:58:23 +0000

It is too async heavy as per its readme -- this is very off-putting. Not everyone cares for async. There is no usage shown with sync code.