🤣 I wasn’t even sure if I should post it on lemmy. I mainly wrote it so I can post it under other peoples posts that actually are intended to artificially create drama to hopefully show enough people what the actual problems are with those puzzles.
But I probably am a fool and this is not going anywhere because most people won’t read a 30min article about those math problems :-)
Thank you very much 🫶. No it’s not annoying at all. I’m very grateful not only for the fact that you read the post but also that you took the time to point out issues.
Exactly. With the blog post I try to reach people who already heared that some people say it’s ambiguous but either down understand how, or don’t believe it. I’m not sure if that will work out because people who “already know the only correct answer” probably won’t read a 30min blog post.
The calculator section is actually pretty important, because it shows how there is no consensus. Sharp is especially interesting with respect to your comment because all scientific Sharp calculators say it’s 1. For all the other brands for hardware calculators there are roughly 50:50 with saying 1 and 9.
So I’m not sure if you are suggesting that thousands of experts and hundreds of engineers at Casio, Texas Instruments, HP and Sharp got it wrong and you got it right?
There really is no agreed upon standard even amongst experts.
That’s just wrong. “Kilo” is ancient Greek for “thousand”. It always meant 1000. Because bytes are grouped on powers of two and because of the pure coincidence that 10^3 (1000) is almost the same size as 2^10 (1024) people colloquially said kilobyte when they meant 1024 bytes, but that was always wrong.
Update: To make it even clearer. Try to think what historical would have happened if instead of binary, most computers would use ternary. Nobody would even think about reusing kilo for 3^6 (=729) or 3^7 (=2187) because they are not even close.
Resuing well established prefixes like kilo was always a stupid idea.
In a scientific context it’s actually very rare to run into that issue because divisions are mostly written as fractions which will completely mitigate the issue.
The strong implicit multiplication will only cause ambiguity after a division with inline notation. Once you use fractions the ambiguity vanishes.
In practice you also rarely see implicit multiplications between numbers but mostly between variables or variables and their coefficients.
👍 That was actually one of the reasons why I wrote this blog post. I wanted to compile a list of points that show as clear as humanity possible that there is no consensus here, even amongst experts.
That probably won’t convince everybody but if that won’t probably nothing will.
True, and it’s not only about learning math but that there is actually no consensus even amongst experts, about the priority of implicit multiplications (without explicit multiplication sign). In the blog post there are a lot of things that try to show why and how that’s the case.
In this case it’s actually the absence of sources. I couldn’t find a single credible source that states that ÷ has somehow a different operator priority than / or that :
The only things there are a lot of are social media comments claiming that without any source.
My guess is that this comes from a misunderstanding that the obelus sign is forbidden in a lot of standards. But that’s because it can be confused with other symbols and operations and not because the order of operations is somehow unclear.
I’m not sure if you read the post yet but I also have a short section about alternative notations which are less ambiguous or never ambiguous. RPN has the same issue as most notations that are never ambiguous namely that it’s hard to read - especially for big expressions.