1. Sprites & legacy CSS still matter for performance
Many commenters note that sprite sheets were once a must‑have for reducing HTTP requests and that the technique is still useful today, especially when HTTP/2 multiplexing isn’t available.
- “If you have a bunch of similarly‑sized elements stick them all in a single file and use CSS to make multiple references to the same file display different images.” – EvanAnderson
- “The file size of the sprite sheet image is often smaller than the combined file sizes of the individual images.” – toast0
- “Back in the day we used ‘background‑position’ to slice up the sprite map… it was the underpinning of the site’s legendary ‘sliding windows’ technique.” – lelandfe
2. AI struggles with CSS, but design tools can help
Users point out that large language models are still weak at writing aesthetically pleasing CSS, yet newer AI‑assisted design tools (e.g., Figma MCP with Claude) can generate good layouts.
- “LLM are actually really bad at writing CSS. CSS is 20% logic and 80% art… I hand write all of my CSS.” – zarzavat
- “I was shocked at how good it works. Sure, Claude sucks at CSS, but Figma nails it even for the worst designed pages.” – sigseg1v
3. Animation UX: timing, intent, and user perception
Several comments critique how animations communicate intent and affect usability, emphasizing that animations should feel natural and not intrusive.
- “The most important signal that any animation provides is this: the computer is doing this for you.” – hyperhello
- “The man coming from the left eased in and then slowly stopped… it is profoundly wrong, like a person sneaking out of a dark place.” – hyperhello
- “All animations are hitting a consistent 60 fps.” – semolino
These three themes—legacy sprite performance, AI’s CSS limitations, and animation UX—dominate the discussion.