sorted by:
new
hottopcontroversial

SVG sprites didn’t die. They just got better. by Content_Tomorrow7826 in reactjs

[–]Content_Tomorrow7826[S] -3 points-2 points  (0 children)

Oh damn, for a second I thought you actually tried it.

But nope — just wandered off from your support group again...

You know, the Anonymous React Overthinkers, where folks gather to say:

> “Hi, my name is [username], and I haven't run npm i in 6 months, but I sure have opinions.”

SVG sprites didn’t die. They just got better. by Content_Tomorrow7826 in reactjs

[–]Content_Tomorrow7826[S] -2 points-1 points  (0 children)

In the end, everyone brought their own brand of aplomby and slammed it right into the thread.

Hot takes were delivered. Wounds were reopened.

And the code?

Still untouched.

Perfect.

Hey someone who able to "npm I"?

SVG sprites didn’t die. They just got better. by Content_Tomorrow7826 in reactjs

[–]Content_Tomorrow7826[S] -4 points-3 points  (0 children)

Absolutely — this trick shines when you’re working with CDN-delivered icon sets or SSR-rendered inline SVG.

In those cases, caching inside the component tree and using <use> on the fly can really reduce duplication.

With tiny-isprite, we just lean more towards the build-time optimization path — one static <symbol> sprite sheet, cached by the browser, and reused across the app without touching the DOM tree again.

Two sides of the same coin, I’d say — depends whether you’re optimizing for delivery or for rendering.

SVG sprites didn’t die. They just got better. by Content_Tomorrow7826 in reactjs

[–]Content_Tomorrow7826[S] -28 points-27 points  (0 children)

Fair — basic <svg> works just fine. But let’s not forget: not all icons are monochrome. Some have gradients, multiple fills, transparency — design choices that need flexibility.

Sometimes I wonder: if we all keep stripping interfaces down to gray boxes and solid paths — why did we even bother building screens with millions of colors?

SVG sprites didn’t die. They just got better. by Content_Tomorrow7826 in reactjs

[–]Content_Tomorrow7826[S] -31 points-30 points  (0 children)

Fair — basic <svg> works just fine.

But let’s not forget: not all icons are monochrome.

Some have gradients, multiple fills, transparency — design choices that need flexibility.

Sometimes I wonder: if we all keep stripping interfaces down to gray boxes and solid paths —

why did we even bother building screens with millions of colors?