Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #81683
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Vibe Programming |
| Date | 2026-02-01 21:09 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10lofe3$3uko$1@dont-email.me> (permalink) |
| References | <_7-dnWHCjJXD7eD0nZ2dnZfqnPQAAAAA@giganews.com> <10ln8o4$2fleq$1@dont-email.me> |
On Sun, 1 Feb 2026 10:09:08 +0000, Pancho wrote: > My naive solution would be to avoid threading, use IO with > callbacks, or use a handful of long-lived threads, like the "worker > thread"/"gui thread" pattern. Coroutines (in the “stackless” form) are making a bit of a comeback at the moment. You see these “async/await” constructs appearing in languages like JavaScript and Python.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Hmm ... CHAT Program Writing c186282 <c186282@nnada.net> - 2026-01-30 22:00 -0500
Re: Hmm ... CHAT Program Writing Pancho <Pancho.Jones@protonmail.com> - 2026-02-01 10:09 +0000
Re: Vibe Programming Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-01 21:09 +0000
Re: Vibe Programming c186282 <c186282@nnada.net> - 2026-02-01 18:05 -0500
Re: Hmm ... CHAT Program Writing c186282 <c186282@nnada.net> - 2026-02-01 17:44 -0500
csiph-web