well 0.9999... is actually 1 because
x = 0.9999...
10x = 9.9999...
10x (9.9999...) - x (0.9999...) = 9
9x = 9
x = 1
so 0.9999... is 1
Welcome to /c/SoftwareGore!
This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!
Remember to read the rules before you make a post or comment!
Community Rules - Click to expand
These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)
You should also check out these awesome communities!
well 0.9999... is actually 1 because
x = 0.9999...
10x = 9.9999...
10x (9.9999...) - x (0.9999...) = 9
9x = 9
x = 1
so 0.9999... is 1
This is muuuch better demonstrated by
1/3 = .33... 2/3 = .66... 3/3 = 0.99...
"Repeating" matters in approximations
Yes, but 0.99999999999999999999 isn't 0.999... and therefore not 1, so it's still wrong.
The issue here lies in how it calculates each correct answer value, which is set at 1/15. This approach introduces an approximation error. When you sum all these values together, the total doesn't quite reach 1.
edit: It's actually 1/19 for each question
(1/19)*19 = 0,9999999991
Penmanship counts
Looks like a floating point error
it's almost like computers are not that accurate when calculating floating point numbers
About a year ago I ended up with a floating point value that was something like 1.0000000000078 when it should have been 1. Tore my hair out for hours trying to get the piece of crap embedded vendor locked device to just make it 1.