Re:Go 2, here we come
by toyg on Thursday November 29, 2018 @03:55PM
(#18563915)
The subset of Go users who deploy on 32bit hardware in 2018 and care about performance at that level, is likely to be vanishingly small.
[ Parent
| on HN ]
32 bit ARM is still very common.
What about Go in 32 bit ARM?
Re:Go 2, here we come
by throwaway34241 on Thursday November 29, 2018 @04:16PM
(#18564093)
Even if it's OK to degrade the performance of a small minority of users, is there a big benefit to emulating 64 bit ints everywhere on 32 bit hardware? (I'm not saying there isn't a benefit, just that it's not clear to me what it is).
I don't know how many users are still on 32bit. Maybe low power network devices? Older mobile phones (Go isn't usually run on mobile, but it's possible...).
If at some point in the future 32 bit systems become totally irrelevant for Go users, maybe a release of Go could drop support for it altogether and make int an alias for int64, and save people some type casts. 32 bit systems probably aren't at that point yet though.
>I don't know how many users are still on 32bit. Maybe low power network devices? Older mobile phones (Go isn't usually run on mobile, but it's possible...).
Well, 16 bit would also be possible if someone took the effort. Perhaps it just shouldn't be encouraged.
Re:Go 2, here we come
by throwaway34241 on Friday November 30, 2018 @06:37PM
(#18573807)
By 'possible' I meant that it's currently supported by the Go toolchain.