proomt

Search

Search posts, papers, and topics

All posts

Hacker News front page14 min readintermediate

The Effect of CRTs on Pixel Art

Summary

A nostalgic‑but‑technical look at how CRT displays interact with pixel art, covering scanlines, color bleed, signal quality, and how 8‑ and 16‑bit developers used dithering and anti‑aliasing to compensate for low resolution and limited palettes.

  • CRT fuzziness isn’t a magic fix; real CRTs still show visible pixels and scanlines.
  • Artists on C64/NES used limited palettes but could achieve smoother looks with dithering and anti‑aliasing, especially on later 16‑bit machines like the Amiga.
  • Signal path matters: RF → composite → S‑Video → RGB SCART each adds or reduces blur and color bleeding.
  • Modern CRT emulation filters often over‑blur; the author prefers real CRTs for authentic viewing.

Pixel‑art creators and retro‑game developers still rely on CRT‑style displays for authenticity. Knowing which visual artifacts come from the display versus the art itself helps avoid misguided “CRT‑only” design decisions and informs better emulation or up‑scaling pipelines.

5/10

Related reading

  1. ModaLens: Measuring Image Sensitivity in Report-Conditioned Medical VLMs

    ModaLens introduces a paired image-swap audit to measure how radiology report availability affects image sensitivity in medical VLMs. It found that MedGemma-27B's answers changed significantly more often when the image was swapped if the report was not available, indicating reports reduce image reliance.

    Hugging Face Daily Papersarxiv.org1 minpaper
  2. Article: Architecting Secure and Scalable Facial Verification Systems

    A real‑world post‑mortem of a high‑volume face verification service that moved from a naïve synchronous API to an async, layered pipeline (edge validation, preprocessing, decoupled detection/verification, decision engine) to achieve 8.5k rpm, p99 < 1.8 s, 30 % cost savings, and strict privacy controls.

    InfoQinfoq.com15 min
  3. Anatomy of a Texture

    A practical deep‑dive into modern texture memory layout: block‑compression (BC7), swizzle ordering (Morton/Z‑order), mip‑map hierarchies, and concrete debugging tricks for cross‑platform texture conversion.

    Hacker News front pagegithub.io12 minHN10816
  4. Can we make default Tailwind a more accessible choice?

    The post examines Tailwind’s default rem‑based breakpoints, showing how they scale with a user’s root‑font‑size and can shift layouts, which helps some users but can break designs. It argues that pixel breakpoints remain a defensible alternative for preserving layout stability while still supporting accessibility.

    Freek Van der Hertenfreek.dev1 min