Conversation

Notices

1. Embed this notice
   pwm (pwm@darkdork.dev)'s status on Tuesday, 18-Mar-2025 11:12:57 JST pwm
   concurrent programming hurts
   • Embed this notice
     :blank: (i@declin.eu)'s status on Tuesday, 18-Mar-2025 20:01:51 JST :blank:

     in reply to
     @pwm doing this in python is called self harm
     pwm likes this.
   • Embed this notice
     pwm (pwm@darkdork.dev)'s status on Tuesday, 18-Mar-2025 20:28:55 JST pwm

     in reply to

     • :blank:
     @i blah blah
   • Embed this notice
     :blank: (i@declin.eu)'s status on Tuesday, 18-Mar-2025 20:35:00 JST :blank:

     in reply to
     @pwm
     pwm likes this.
   • Embed this notice
     pwm (pwm@darkdork.dev)'s status on Tuesday, 18-Mar-2025 20:38:23 JST pwm

     in reply to

     • :blank:
     @i The GIL is being done away with in an upcoming release, but we'll see when that actually happens (you can currently compile it with it off).
     My implementation is a separate process with its own worker threads. The intended use here is long running i/o bound tasks, which threads in python are not bad at since they can switch contexts while something else is blocking.
   • Embed this notice
     pwm (pwm@darkdork.dev)'s status on Tuesday, 18-Mar-2025 20:43:19 JST pwm

     in reply to

     • :blank:
     @i (I may give up and use processes though instead)
   • Embed this notice
     :blank: (i@declin.eu)'s status on Tuesday, 18-Mar-2025 20:45:27 JST :blank:

     in reply to
     @pwm in the end it's all about them EYEPEECEE'S
     
     some days a network call is better than shared memory
     pwm likes this.