News for hackers. Stuff that matters.
Re:Thinking Go is simple is considered harmful by myWindoonn on Tuesday June 19, 2018 @02:32PM (#17349167)
Go had, last I manually counted, a whopping seventeen numeric types. That's a lot of complexity just in interpreting numeric literals!
Re:Thinking Go is simple is considered harmful by pythonistic on Tuesday June 19, 2018 @02:43PM (#17349240)
The underlying types are exposed to you, like C.

Go isn't adding sugar to handling numeric types: it's not autoboxing to help you with conversions, and it's not hiding the implementation like a scripting language. I'll admit, it's a real pain when trying to convert from one type to another (e.g., in graphics programming, where I'm changing types from internal representations to what gets drawn to the screen). For most "job" programming, it was a non-issue and I felt secure in knowing what types, sizes, and representations I'm really using.

Re:Thinking Go is simple is considered harmful by tapirl on Tuesday June 19, 2018 @04:21PM (#17350004)
I ever had many confusions in studying Go, but I never had any confusions on numeric literals. Go nmeric literals are intuitive and consistent with many other popular languages.
Re:Thinking Go is simple is considered harmful by icholy on Tuesday June 19, 2018 @02:43PM (#17349244)
Give me a break
Re:Thinking Go is simple is considered harmful by abiox on Tuesday June 19, 2018 @02:42PM (#17349234)
afaik the bulk of those are just related to sizing (16 bits, 32 bits, etc). it's not really that complex, and generally quite handy for a language like go.