121–130 of 293 posts
Earlier quoted context omitted.
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
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...
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!
Earlier quoted context omitted.
Ooh you could even animate with a css transition from one bounce to the next with a linear curve; then you don't run any JS per frame, only at the bounces.
The problem I think is that transitions have fixed amount of time, both long and short travels finish with the same amount of time giving a different velocity of movement. Also executing Javascript every frame is not that heavy
The animations built into the platform can run and remain smooth under a broader range of conditions, which is why they should be preferred if you don't need the level of control that running script via requestAnimationFrame gives you.
Earlier quoted context omitted.
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
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...
My wife's version uses SVG for scaling and is also responsive on resize. https://github.com/boglarkasebestyen/dvdscreensaver
Nice, a bit too fast on my machine though. It should probably use a time-based interval, rather than updating every frame.
Most web displays run at 60 Hz (16.66ms), making it inefficient to update every 5ms. 144Hz displays do exist and are wonderful, but you should always use requestAnimationFrame anyway.
Earlier quoted context omitted.
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
It didn't even occur to me that this would need to be explained. Up next we should talk about why it was bad to leave VCRs paused for long periods of time.
As 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…
Why do people bother minifying code this small? It's 168 bytes gzipped. The unminified source is probably under 1kb gzipped. Just no point to minifying.
Probably more work to rip it out of your build pipeline than just reusing the config you use for all your other projects.
Earlier quoted context omitted.
Why was that bad?
I remember being told as a child that it "wears out the tape," but I'm going to guess it's specifically because the same section of tape stays wrapped around the capstan (the metal cylinder it loops around to be read) when it would normally be passing through. Keeping the same section of tape under tension for a prolonged period presumably weakens or risks distorting it.