• halvar@lemm.ee
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    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
    
    • RedditWanderer@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      This is muuuch better demonstrated by

      1/3 = .33… 2/3 = .66… 3/3 = 0.99…

      “Repeating” matters in approximations

    • exscape@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Yes, but 0.99999999999999999999 isn’t 0.999… and therefore not 1, so it’s still wrong.

  • GigaWerts@lemmy.eco.br
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 year ago

    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

  • nogrub@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    it’s almost like computers are not that accurate when calculating floating point numbers

    • afraid_of_zombies@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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.