News for hackers. Stuff that matters.
Re:GitHub Copilot as open source code laundering? by brundolf on Wednesday June 30, 2021 @11:28AM (#27689722)
I was somewhat worried about that until I saw this: https://twitter.com/nickjshearer/status/1409902649625956361?...

I think programming is one of the many domains (including driving) that will never be totally solved by AI unless/until it's full AGI. The long tail of contextual understanding and messy edge-cases is intractable otherwise.

Will that happen one day? Maybe. Will some kinds of labor get fully automated before then? Probably. But I think the overall time-scale is longer than it seems.

Re:GitHub Copilot as open source code laundering? by sillysaurusx on Wednesday June 30, 2021 @12:26PM (#27690445)
64-bit floats should be fine; I think that tweet is only sort-of correct.

The problem with floats-storing-money is (a) you have to know how many digits of precision you want (e.g. cents, dollars, a tenth of a cent), and (b) you need to watch out if you're adding values together.

Even if certain values can't be represented exactly, that's ok, because you'd want to round to two decimal places before doing anything.

Is there a monetary value that you can't represent with a 64-bit float? E.g. some specific example where quantization ends up throwing off the value by at least 1/100th of whatever currency you're using?

Re:GitHub Copilot as open source code laundering? by fredros on Wednesday June 30, 2021 @01:01PM (#27690847)
Storing money as float is always a bad decision. Source: been working for several banks and faced many of such bugs.
Re:GitHub Copilot as open source code laundering? by astrange on Wednesday June 30, 2021 @07:42PM (#27694819)
Pretty common in financial modeling, which I'm told is all done in Excel.