You’ve probably heard this a million times. I know you have. So this is NumberOfDecimalRequests.
Consider the following: Go has an enormous amount of momentum right now. People recognize that the nature of goroutines and channels is far superior to any other form of asynchronous back-end code-flow. The philosophy of “Do not communicate by sharing memory; instead, share memory by communicating” is pure genius and blows everything else out of the water especially .NET/.NET Core ideas. I know. I’ve coded back-end APIs in Go and I have seen the results first-hand.
However, there is a market that you are going to completely fail to reach in terms of adoption of programming language unless you add native support for decimals. That market is: anything that has anything to do with money ever. If you have any common sense then you should realize that market is quite large. I work for a company developing a payroll application. It is practically a Greek tragedy that I have to rely on a third-party dependency and horrific functional notation to do any math.
I won’t waste your time with explanations of why float primitives fail because you know. I won’t waste your time with how inconvenient ‘big’ types are because you SHOULD know.
If you are not already working on native support for a Go decimal type, then start now. If you have been, then please reply and set my mind at ease.
Signed: every mathematician that writes Go code.