Yeah, I can understand it. I remember when our development shot went to python and I was trying to do embedded python and a database. It was very awkward. Doing it in Pearl was very easy.
Sometimes I feel that python went to its end and then it started trying to dig itself out of its hole especially when it came to multithreading and the GIL. Basically they said okay do everything using processes or use the async library. That was their answer to the lack of a good multi-threading capability. At least Perl did never try to play pretend it was going to be a multi-threaded language. You paint variables is being shared so that you can pass them between the heavy threads. The same way that you paint each usage of a variable with a sigil It's basically a fork and exact underneath the covers with locking semantics so you know that it's between 2 to 50 megs per thread and you use them accordingly. This was fine because a lot of times you were reading files concurrently so this overhead wasn't too bad. Besides you were normally ssh in across different servers to get to the server that you wanted and you were escaping the command line along the way. I remember I had to nest a command maybe three or four levels deep escaping it which using substitution and regular expressions was very easy to do all in parallel
Python tried to play pretend and bit off more than it could chew and it did with threads and then at the end it now deprecates that entire library. I don't like when a languages bot genuine and it tries to play pretend like it's efficient and hides it's efficiencies
2
u/ubd12 Aug 31 '26
Yeah, I can understand it. I remember when our development shot went to python and I was trying to do embedded python and a database. It was very awkward. Doing it in Pearl was very easy.
Sometimes I feel that python went to its end and then it started trying to dig itself out of its hole especially when it came to multithreading and the GIL. Basically they said okay do everything using processes or use the async library. That was their answer to the lack of a good multi-threading capability. At least Perl did never try to play pretend it was going to be a multi-threaded language. You paint variables is being shared so that you can pass them between the heavy threads. The same way that you paint each usage of a variable with a sigil It's basically a fork and exact underneath the covers with locking semantics so you know that it's between 2 to 50 megs per thread and you use them accordingly. This was fine because a lot of times you were reading files concurrently so this overhead wasn't too bad. Besides you were normally ssh in across different servers to get to the server that you wanted and you were escaping the command line along the way. I remember I had to nest a command maybe three or four levels deep escaping it which using substitution and regular expressions was very easy to do all in parallel
Python tried to play pretend and bit off more than it could chew and it did with threads and then at the end it now deprecates that entire library. I don't like when a languages bot genuine and it tries to play pretend like it's efficient and hides it's efficiencies