Hacker NewsConditions in the Intel 8087 floating-point chip's microcode
https://www.righto.com/2025/12/8087-microcode-conditions.html
#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture
JavaScriptBuzzHow to Stop Floating Point Money Bugs
0.1 + 0.2 is not 0.3 in JavaScript.
How to Stop Floating Point Money Bugs #howto
Zmij: Faster floating point double-to-string conversion
https://vitaut.net/posts/2025/faster-dtoa/
#HackerNews #Zmij #FloatingPoint #Conversion #FasterDtoa #Programming #TechNews
0.1 + 0.2 = 0.30000000000000004?!
JavaScript math is broken! Adding 0.1 + 0.2 creates a number that will shock you. This is why financial apps fail! Watch the chaos!
#javascript #javascripttricks #codingtips #programmingtutorial #floatingpoint #javascriptquiz #codingchallenge #javascriptshorts #javascriptbugs #mathprecision #javascriptwtf #numberprecision
claudefound+fixed a #bug : part of one track was using single precision float instead of double in one critical segment; it worked ok at 48kHz sample rate but at 96kHz it reached #FloatingPoint precision limits leading to a counter failing to increment past a certain point, meaning the track end condition was never reached...
The Eclectic Light CompanyExplainer: Numbers
https://fed.brid.gy/r/https://eclecticlight.co/2025/12/06/explainer-numbers/
R.L. Dane 
🍵 
This is still the best thing ever: https://i.kym-cdn.com/photos/images/newsfeed/002/128/164/13b.png #FloatingPoint #Meme #ProgrammerHumor — #microblogging #MicroToot: 137 characters
Nils Goroll 🕊️
i just found https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/ by @randomascii and i am amazed.
thank you for this great post!
Dyalog#APLQuest 2013-07: Write a function that selects the floating point (non-integer) numbers from a numeric vector (see https://apl.quest/2013/7/ to test your solution and view ours).
did some minor hacking on #Fraktaler3 today for the first time in months.
- fixed it so it works with toml11 v4 (run "make") as well as v3 (run "make TOML11=3")
- removed "quit when done" checkbox from android and web builds, where it doesn't make sense
- fix: correct status is now shown when pressing ESC after the rendering is complete
- added double precision version of floatexp (separate floating point mantissa and integer exponent, for wider dynamic range necessary for very deep zooms); the extra precision of doubleexpover single precision floatexp turns out to be necessary sometimes (more often with higher power formulas and higher iteration counts)
- fixed the mildly bitrotted quadruple precision float128 support, now works again enabled (run "make") and disabled (run "make FLOAT128="). hopefully it won't be necessary to use it for more than checking that double precision image are plausible, because it's very slow.
