• 2 Posts
  • 60 Comments
Joined 10 months ago
cake
Cake day: June 23rd, 2024

help-circle


  • Yeah, it’s basically budget XKCD. The comic, started in 2003, has been steeply declining in production volume since 2013 and the last one was 2.5 years ago. I have scraped all 599 pages on the main website, plus there’s some on root.cz and Trustport, a now-defunct site available via archive.org (where the comics are in English already, such as this very funny one), I have yet to download. I have made a JSON index including tags, categories and body text, and I’ll probably translate a few of the images every week. I’m planning to make a GitHub Pages site plus a special Lemmy community and schedule a bot to post one daily. The earliest I can do this though is July.

    Some will have to be in German (if you can make comic #3’s Kern des Pudels kompilieren make sense in English, let me know), some will need an extra explanatory paragraph, and some cannot be translated at all. Lemmy users will be happy to see that 2006 Linux jokes haven’t aged at all but I wonder how they’ll put up with semi-rude Czech humor, traditional gender roles and lack of diversity.


  • Of course there is a relevant Bugemos comic

    “…by the end I would use Tor for every single thing…”
    “…and change my email every day!”

    “You see, most people here have more troubles with alcohol, rather than anonymity…”

    There’s like 600 of these and most are funny in English too. I should really translate them when I have the time…




  • This is a great time for the engineer to exert leverage.

    "Yes, I can fix it in hours. Here are my demands:

    • $200,000
    • I’ll also push a firmware update to all your devices that allows setting any address for the server and exposes all functionality in a Home Assistant API, and you won’t ever disable this in current or future devices
    • You’ll offer a free locally-connected button/knob device to any customer owning an affected product, or a free service to upgrade the products with on-device controls
    • In any social media posts, press releases, customer communication or interviews regarding today’s outage, you have to say that plumbing that requires a server connection is a bad idea





  • Displays have to be driven in multiplex because you can’t just wire each of the 6 million subpixels (4 million for Samsung OLED cuz they alternate red/blue in a checkerboard) of a 1080p screen to a pin of a chip that has the screen RAM and powers subpixels continuously. Therefore, the chip will have row and column outputs, and use a technique called “multiplexing” that powers only one row at a time.

    It’s really about how the pixels respond to being driven. In TFT LCDs, driving a subpixel will charge its memory capacitor to a desired voltage, corresponding to the target brightness. Over the next few milliseconds, the subpixel will fade into that color as the nematic elements twist in response to voltage. Over about one second, the capacitor would lose its charge and the LCD would fade to its resting state (all-white for positive ones). You can see this if you suddenly kill power to the driving board while leaving the backlight on. So it needs to be recharged (redriven) in a few tens of milliseconds. Subpixels do get a little brighter between refreshes but that’s very subtle and not noticeable at 60 Hz unless it’s a passive matrix (STN without those capacitors, like a Game Boy screen) under flickery lighting.

    Meanwhile, OLED pixels are black while not currently being refreshed, so the difference in brightness just before and during refresh is not about +0.1 % but -100 %, just like with CRT phosphor. It relies on human eyes’ persistance of vision to create an illusion of a complete image. It varies from person to person, but anything below about 60 Hz gets uncomfortable after long periods, and below 40 Hz (especially around 10-20 Hz) can be seizure-inducing. But again, the magnitude of flicker matters as much as frequency.


  • TFT cells in LCD panels hold the image for pretty long between refreshes so there is little difference between 60 Hz and 120 Hz. Yes, 120 Hz will allow for 120 fps but that/s not really relevant for basic GUI.

    Meanwhile, a 60Hz OLED panel is as flickery as a CRT TV because the LEDs only glow when being refreshed.

    With a 30Hz LCD panel, you might notice the direction the refreshing goes across the screen, and there might be a little less contrast, some inconsistency between pixels, and a soft moving gradient if this interferes with the backlight frequency (since most backlight is DC now, this problem only really manifests with reflective LCDs under flickery mains lights).

    Meanwhile, a 30Hz OLED panel would be seizure-inducing and unwatchable. This is what it would look like (60fps mandatory)