Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #81686

Re: Vibe Programming

Show all headers | View raw

On 2/1/26 16:09, Lawrence D’Oliveiro wrote:
> 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.

   Modern need is often for the highest speed/capacity
   possible, something that can deal with hundreds or
   thousands of internet clients.

   Never explicitly delved into co-routines, servers or
   otherwise. Sounds kind of complex to manage. It's
   kind of like starting several free-running pgms at
   the same time that can talk to each other, almost
   forking but not quite.

   Now, deep in the background of Python/C/etc, the
   library writers MAY be using them ...

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

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