decimal VS logrus

Try it in JS with console.log(4.225 * 100);, you'll see the same unexpected result. Depending on your needs, it's actually fine to just be off by some amount. If it does really matter, then use an arbitrary precision library like https://github.com/shopspring/decimal to get the results you need.

Most programming languages ( JavaScript, PHP, Go, Python, Java, C# ) have built-in support or 3rd-party libraries for handling this data type, even though the internal implementations can differ:

while working with money, dont use floats, use something like https://github.com/shopspring/decimal (go std lib doesnt have its own decimals yet)

Integers, or something like this: https://github.com/shopspring/decimal

I make heavy use of caching, and was caching both in-memory and in Redis using JSON to convert the data in to a string. The struct itself isn't super complicated, one level nested, and some fields use the shopspring/decimal library.

I actually use this to represent monetary values btw :)

Check out https://github.com/shopspring/decimal for doing money related calculations.

We personally use https://github.com/shopspring/decimal and it works well.

decimal, one of the first Go library that created to work with decimal and monetary value.

https://github.com/shopspring/decimal also.

It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.

Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.

For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON

For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.

I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.

If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...

Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553

Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.