Welcome to the Lounge

OriginalGriff wrote:

65K rows? Not nice, not at all.

#realJSOP wrote:

What retard decided that storing vote counts as floating point numbers was a "good idea"?

1. Assuming only one voting machine per precinct, the number of voters would have to pass 2^24 (16,777,216) before problems would start. Most (all?) precincts in the US aren't that large.
2. Given (1), When calculating the results of local elections, or elections to the House of Representatives, the results will be accurate.
3. The population of California, the largest State, may be represented using 26 bits, i.e. the result will be inaccurate in the last 2 bits. Given that there are ~50 counties, the chance that a vote will be lost at the county level is small (a candidate would have to get more than 2^24 votes, probably more than the total voter register of any single county). When summing the county totals for a State-wide vote (i.e. Gubernatorial, Federal Senate, or Presidential elections), it is possible that a candidate would lose (or gain) a few votes due to round-off. Assuming no State-wide election is decided by less than ~200 votes, any errors are immaterial.

#realJSOP wrote:

Even more importantly, why would anyone use software that was demonstrably accuracy-challenged and so easily corrupted?

#realJSOP wrote:

What retard decided that storing vote counts as floating point numbers was a "good idea"?

#include <iostream>

int main() {
   __int64 test = 0;
   double d = 0;
   for (int i=0; i<16777216; ++i) {
      d = d + 1;
      }
   std::cout << d << std::endl;

   d = 0;
   for (__int64 i=0; i<1000000000; ++i) {
      d = d+1;
      }
   std::cout << d;
   return 0;
   }

#realJSOP wrote:

Why would any self-respecting developer agree to write code in such a way as to allow subversion of its targeted purpose?

#realJSOP wrote:

Even more importantly, why would anyone use software that was demonstrably accuracy-challenged and so easily corrupted?