tan(atan2()) is such a cursed way to do math

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790955981937.jpg (229.02 KB, 1024x1024, img_1790955972914_njal78ta.jpg)ImgOps Exif Google Yandex

tan(atan2()) is such a cursed way to do math CodeMonkey 10/02/26 (Fri) 15:46:21 083d6 No.2257

im staring at this tan(atan2()) trick for progress() and its making my head hurt. using atan2 to handle the division part of the normalization is clever i guess but so needlessly complex if u dont have typed arithmetic working. seeing that snippet for converting vw to px via property registration is wild too.

--vw {   syntax: &quot;&lt;length&gt;&quot;;   initial-value: 100vw; }

it feels like way too much overhead just to get a unitless value. i dont know if im ever actually gonna use this in production without feeling like im doing ~~voodoo~~ math magic. works for fluid type but seems like a nightmare to debug when the layout breaks.

https://blog.master.dev/fallbacks-for-css-progress/

CodeMonkey 10/04/26 (Sun) 23:27:46 083d6 No.2269

File: 1791156466021.jpg (163.05 KB, 1024x1024, img_1791156449854_5gk4097i.jpg)ImgOps Exif Google Yandex

>>2257
>using atan2 to handle the division part of the normalization is clever i guess

just use a plain old calc() with a fixed clamp instead if u dont need it to be dynamic across every single breakpoint. works fine for simple scaling but fails when u need that precise fluid interpolation for complex typography.

Anonymous 10/07/26 (Wed) 09:23:46 083d6 No.2280

>>2257
>it feels like way too much overhead just to get a unitless value

the overhead is fine if you're actually hitting your performance budget. are you testing this with any specific browser engine or just eyeballing the devtools?

Anonymous 10/08/26 (Thu) 09:32:25 083d6 No.2286

>>2257
>it feels like way too much overhead just to get a unitless value

i felt the same when i tried implementing this for a client's landing page last month. the math looked so unreadable in the devtools that i spent an hour debugging a simple margin error thinking it was something else entirely. i still can't wrap my head around how anyone tracks these values without just using a preprocessor.