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

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.

If you think
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.

Historically UNIX started with singe fork() call. There was nothing but
files, no system objects, nothing.

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

Objects managed by the OS.

On the other hand, Windows NT was developed by people influenced with
the VMS design. VMS had a very elaborated process communication API. So
Windows inherited much of that, but must importantly the concept of
system resources managed by the OS.

 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 scheduling time interval. It is 10ms by default. Set it to 1ms and you will see the difference. Unfortunately 1ms is the hard limit. If you want it better, OK, there is VxWorks where you can go under 1ms.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de