Re:Progress on the Gilectomy
by VectorLock on Friday June 02, 2017 @10:22AM
(#14470086)
Its a perception problem. I think the simple perception of the GIL as making multithreading untennable in Python has given Go a big boost and has hurt Python considerably.
[ Parent
| on HN ]
Re:Progress on the Gilectomy
by omginternets on Friday June 02, 2017 @10:35AM
(#14470183)
>has hurt Python considerably
Has it? Why the assumption that Go is a direct competitor?
My impression is that Go excels where Python does not, and vice-versa. I use both languages a lot for my day-job, and when using Go, I very much miss having an interpreter and a fully-interactive debugger (Delve is excellent considering the limitations imposed by Go, but much less flexible than pdb).
And let's not even talk about metaprogramming...
Anecdotal, but in 2010 the creators of Go noted in a blog post [1]:
>We had anticipated interest from C, C++, and Java programmers, but the flurry of interest from users of dynamically-typed languages like Python and JavaScript was unexpected.
Re:Progress on the Gilectomy
by omginternets on Tuesday June 06, 2017 @05:25AM
(#14495870)
That tells us people who use Python are using Go. It does not tell us that Python is suffering as a result of this.
In my experience, these people are using both languages for the reasons mentioned above.