4 ms·
"Not because of the missing functionality, but because you can't talk about go without somebody bringing up [the GIL]." It's better these days, but for a while
by 3JPLW 13y ago
"Not because of the missing functionality, but because you can't talk about go without somebody bringing up [the GIL]."
It's better these days, but for a while it was a common point of contention.
- LBarret 13y agoit was slightly different: Anybody who wanted to try implementing a gil-less python could. The reasons of the status-quo were well explained. We only get hand-waving from the Go core devs.
- ithkuil 13y agoAdding generics to the language affects the language and reimplementing an interpreter/compiler for a language that fixes a performance issue without being incompatible are two completely different things.