3 ms·
The disinformation in your post is mind boggling. Go was not designed for 32 bit, segmented stacks are great because of reasons that have nothing to have with a
by 4ad 15y ago
The disinformation in your post is mind boggling. Go was not designed for 32 bit, segmented stacks are great because of reasons that have nothing to have with address space addressability, in fact there are C implementations that use segmented stacks, segmented stacks do not preclude using the system libc, the reasons for bypassing libc were completely different, and calling C code from Go works just fine.
- 0xABADC0DA 15y agoOr in other words "you're wrong because I said so. upvotes please!". Thread count vs stack space is a well-known tradeoff in 32-bit. It doesn't take a rocket scientist to know this is the reason for segmented stacks in Google Go even if there's no smoking gun (wayback didn't archive the golang site for a long time due to a misconfigured robots.txt).
- luriel 15y agoGiven that is well known Go was developed mainly in a 64bit environment and that the 64bit compilers produce much faster code and have been much more tested than the 32bit toolchain, to the point that some people have complained that Go favours 64bit systems too much (if for no other reasons because that is what the main developers use), your whole argument is clearly nonsense, that you are a well known troll with some kind of fixation with bashing Google is just coincidence.
- chc 15y agoSo, any hints about the real reason for passing up libc? Sounds like an interesting story.