Re: Python (was Re: I did not inhale)

On Sun, 18 Aug 2024 12:19:10 +0200
"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> boringly babbled:

On 2024-08-18 10:30, Muttley@dastardlyhq.com wrote:
>

The windows process API is crippled which is why threading is the main
parallel processing method in Windows and has been since 3.0.

>
Threading is the main method because of its performance in a tight
coupled application. Crossing the process borders is very expensive.

Most (all?) versions of unix use copy-on-write when forking so while the
processes are only reading its no different to threading. I doubt windows
implements CoW since - in user space at least - it can't do fork and you
wouldn't need it for executing a brand new process from scratch.

Also shared memory is pretty cheap too.

otherwise please give some examples. However I distincly remember trying to
port  server to windows only to discover that sockets are some wierd
structure in windows instead of a simple file descriptor meaning it was
impossible to multiplex using poll() or select() on them, you had to have
a seperate thread to manage each connection. What a fucking mess designed
by idiots.

>
There is no problem using socket select with Windows. Here is an
implementation of a server doing that:
>
   http://www.dmitry-kazakov.de/ada/components.htm#17.1
>
You can check the Windows implementation of to learn how it is done with
Windows sockets.

No idea what the pages of all that crap is.

Windows sockets are not integers , they can't be multiplexed with file
descriptors, pipes etc in a single call.

fork() copies the entire process space. No idea what you mean by "system
objects". Must be some windows thing.

>
Objects managed by the OS.

Like what? Why does the OS need to manage "objects"?

Windows NT was a slow unreliable dog.

>
It is not slow. Actually you can get same or better performance under
Windows as under Linux. The problem is the default settings of the

I'm not talking about now, I was talking about when NT came out. Learn to
read.