3 ms·

> I.e. it has everything to do with floating point. Floating point has those problems, but so do many other representations. It isn't just a floating point pro

by fargle 7y ago

> I.e. it has everything to do with floating point. Floating point has those problems, but so do many other representations. It isn't just a floating point problem. This is exactly the kind of muddy thinking that is avoided by sticking to a more academic and formal exposition avoids. According to your theory, there are schloads of "Programmers" out there that can't do computer science, or engineering that need a crutch. If that is true, then you're mis-training them to blame floating-point intricacies that they can't possibly understand when it might not even be that.

brazzy 7y ago
> Floating point has those problems, but so do many other representations. It isn't just a floating point problem. This is exactly the kind of muddy thinking That is not "muddy thinking", that is "sticking to the matter at hand", the matter being rhe concrete problems very commonly encountered writing real programs using the built-in datatypes of most programming languages. The only muddy thinking here is your insistence that "other representations" have any relevance here. > If that is true, then you're mis-training them to blame floating-point intricacies that they can't possibly understand How exactly am I "mis-training" people by explaining things so they can understand them? You still have completely failed to point out a single thing that is actually factually wrong on my website. Your critique on the other hand, has been factually wrong in all the places where it's not superficial gatekeeping.
- fargle 7y ago
  So a well meaning reader will decide not to use floating point. He will switch to fixed point. And encounter the same problem because you never explained it correctly. You need to understand the material before you create a explanation of it. You are fixated on floating point when you mean binary fractions, which is a superset.
  - brazzy 7y ago
    I very much do explain all of this correctly. I clearly distinguish between the properties of typically available data types (binary floating point vs. decimal fixed point) You are splitting hairs in a pathetic attempt to sling mud.

by fargle 7y ago

brazzy 7y ago

> Floating point has those problems, but so do many other representations. It isn't just a floating point problem. This is exactly the kind of muddy thinking That is not "muddy thinking", that is "sticking to the matter at hand", the matter being rhe concrete problems very commonly encountered writing real programs using the built-in datatypes of most programming languages. The only muddy thinking here is your insistence that "other representations" have any relevance here. > If that is true, then you're mis-training them to blame floating-point intricacies that they can't possibly understand How exactly am I "mis-training" people by explaining things so they can understand them? You still have completely failed to point out a single thing that is actually factually wrong on my website. Your critique on the other hand, has been factually wrong in all the places where it's not superficial gatekeeping.

fargle 7y ago
So a well meaning reader will decide not to use floating point. He will switch to fixed point. And encounter the same problem because you never explained it correctly. You need to understand the material before you create a explanation of it. You are fixated on floating point when you mean binary fractions, which is a superset.
- brazzy 7y ago
  I very much do explain all of this correctly. I clearly distinguish between the properties of typically available data types (binary floating point vs. decimal fixed point) You are splitting hairs in a pathetic attempt to sling mud.