Difference between revisions of "Talk:2671: Rotation"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
(?)
Line 21: Line 21:
  
 
Where would the rotated photograph bar be on [[1909: Digital Resource Lifespan]]? [[Special:Contributions/172.70.211.50|172.70.211.50]] 22:14, 12 September 2022 (UTC)
 
Where would the rotated photograph bar be on [[1909: Digital Resource Lifespan]]? [[Special:Contributions/172.70.211.50|172.70.211.50]] 22:14, 12 September 2022 (UTC)
 +
 +
Doing this with an jpeg does the same. When rotating an image and saving it the lossy compression will lose more pixels. This makes it more blurry each step. [[Special:Contributions/162.158.203.38|162.158.203.38]] 22:41, 12 September 2022 (UTC)

Revision as of 22:41, 12 September 2022


For extra credit: Waht is the resolution of the phone screen? 172.71.94.135 18:59, 12 September 2022 (UTC)

IMHO 400px. Note SMALLER. -- Hkmaly (talk) 19:53, 12 September 2022 (UTC)
From the image you can assume an 9/20 aspect ratio. Assuming each rotation reduces the image dimensions by that fraction after 9 rotations the dimensions would be reduced 1322 times so the resolution would be something between 1322x595 pixels (anything less than that would made it require 8 rotations or less) to 2935x1321 pixels (anything beyond that would require 10 rotations or more). 1600x720 or 2400x1080 maybe? Applying the same formula for the phone width and assuming atoms are typically around 100 picometers across then the phone width is close to 4.67 cm, too small, but maybe that's because rounding. In the other hand that formula does not work with Planck length at all: using it the phone width would be 1.69 meters. If you assume a width of 7 cm and 97 rotations you get pretty close to Planck length, but the comic says 101, not 97. Something is wrong with my calculations, I don't know what. 162.158.63.160 21:03, 12 September 2022 (UTC)

This seems like it could actually be really cool. Can anyone do this and put the picture here as an example? Also, if possible, include an AI upscale of the one pixel. 172.69.90.83 19:07, 12 September 2022 (UTC)

There's a minor counting error: instead of pointing to the 9th rotation, the 'nine rotations' statement points to the 8th as the first phone has no rotations.172.70.90.77 19:10, 12 September 2022 (UTC)

Anyone getting a 404? Seems like the comic has disappeared. EDIT: ...aaaand it's back. 172.70.100.54 19:34, 12 September 2022 (UTC)

Just putting https://www.codeguru.com/multimedia/rotate-a-bitmap-image/ here. 172.69.134.131 20:12, 12 September 2022 (UTC)

Microsoft C#, and not the original HAKMEM or Smalltalk 80? Please! You might as well be using C++: https://docs.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-plgblt 162.158.166.173 20:21, 12 September 2022 (UTC)
I see your trivial software squabble, and raise one peer reviewed open access article citation: https://link.springer.com/article/10.1007/s10648-010-9144-5 172.69.22.5 22:03, 12 September 2022 (UTC)
I'll see your humorously ambiguous reference, and raise you a slightly more on-topic chapter encompassing both: https://journalspress.com/LJRHSS_Volume17/208_The-Geometric-Progression.pdf 162.158.166.125 22:10, 12 September 2022 (UTC)

Tiktok 108.162.246.68 20:40, 12 September 2022 (UTC)

Where would the rotated photograph bar be on 1909: Digital Resource Lifespan? 172.70.211.50 22:14, 12 September 2022 (UTC)

Doing this with an jpeg does the same. When rotating an image and saving it the lossy compression will lose more pixels. This makes it more blurry each step. 162.158.203.38 22:41, 12 September 2022 (UTC)