Earlier quoted context omitted.
I still remember dragging my CRT around to LAN parties... oh the good old days... was such a pain in the ass though in reality...
Those Sony Trinitron's were literally were made of lead. My back still hurts, but the 20" was worth it!
Bouncing DVD Logo
171–180 of 293 posts
Re: Bouncing DVD Logo
#172Re: Bouncing DVD Logo
#173Earlier quoted context omitted.
I never noticed a benefit over 70 or so. The flicker of 60 made my eyes bleed though. Then with LCDs 60 was fine.
I still don't know what it is about 60 Hz that made me see the flicker plainly as a strobing light. TVs at 50 Hz—nothing (other than being generally bleh back then). Had to use 800x600 instead of 1024x768 just to have 85 Hz instead. On LCDs, I still can see faint flicker on some static backgrounds, and I think 60 Hz might play a role here too—though it seems to also depend on the brightness and Flux being on or off.…
Re: Bouncing DVD Logo
#174As a historical note, the bouncing logo wasn't just for fun, but was important to prevent screen burn-in on CRTs. If you had a static image on a CRT for a long time, it could damage the phosphor. Sometimes you could even see the image when the screen was off! This was the original purpose of screensavers, which saved your screen from damage. Displaying a dynamic image prevented one part of the screen from being overu…
I had heard of this before, but didn't know that screensavers were designed to prevent that damage from happening. In this case, the bouncing DVD logo seems like an odd choice, as the way it's designed, there are certain pixels on the screen that it will never cross (corners, for example), which would fail to serve the desired purpose. Can someone explain?
Re: Bouncing DVD Logo
#175Earlier quoted context omitted.
I never noticed a benefit over 70 or so. The flicker of 60 made my eyes bleed though. Then with LCDs 60 was fine.
I still don't know what it is about 60 Hz that made me see the flicker plainly as a strobing light. TVs at 50 Hz—nothing (other than being generally bleh back then). Had to use 800x600 instead of 1024x768 just to have 85 Hz instead. On LCDs, I still can see faint flicker on some static backgrounds, and I think 60 Hz might play a role here too—though it seems to also depend on the brightness and Flux being on or off.…
Re: Bouncing DVD Logo
#176Earlier quoted context omitted.
I still don't know what it is about 60 Hz that made me see the flicker plainly as a strobing light. TVs at 50 Hz—nothing (other than being generally bleh back then). Had to use 800x600 instead of 1024x768 just to have 85 Hz instead. On LCDs, I still can see faint flicker on some static backgrounds, and I think 60 Hz might play a role here too—though it seems to also depend on the brightness and Flux being on or off.…
AC power is 60hz so room lighting (especially florescent) also flickers at 60hz. It’s a sort of wagon wheel effect.
Re: Bouncing DVD Logo
#177Re: Bouncing DVD Logo
#178Earlier quoted context omitted.
Probably more work to rip it out of your build pipeline than just reusing the config you use for all your other projects.
People use a build pipeline for small JS projects? I just open an editor in a directory and start typing.
Re: Bouncing DVD Logo
#179As a historical note, the bouncing logo wasn't just for fun, but was important to prevent screen burn-in on CRTs. If you had a static image on a CRT for a long time, it could damage the phosphor. Sometimes you could even see the image when the screen was off! This was the original purpose of screensavers, which saved your screen from damage. Displaying a dynamic image prevented one part of the screen from being overu…
That you feel the need to inform us of this "historical fact" makes me feel especially old... having lived through the CRT -> LCD transition period when buying an LCD made going to LAN parties a lot easier
Re: Bouncing DVD Logo
#180Earlier quoted context omitted.
It lags pretty bad on my Pixel phone too..
Only tested on an iPhone, works fine at 60fps. You can open the standalone page at https://wwpzj.csb.app/ to avoid the whole codesandbox app running at the same time.
I beleieve you are quite competent in this, so for me it's just another illustration of how HTML/DOM ecosystem is broken in so many ways that it takes enormous effort to perform such a trivial task. Thank you and plase stop wasting your time on this)