LECO - Unicode Bitpacked by tomxor

function u(t) {

c.width=1920 // clear the canvas
for(i=0;i<9;i++)
x.fillRect(400+i*100+S(t)*300,400,50,200) // draw 50x200 rects

} // 122/140

Please log in (or register) to post a dweet (copy-paste the code somewhere safe to save it meanwhile)


    u(t) is called 60 times per second.
    t: Elapsed time in seconds.
    S: Shorthand for Math.sin.
    C: Shorthand for Math.cos.
    T: Shorthand for Math.tan.
    R: Function that generates rgba-strings, usage ex.: R(255, 255, 255, 0.5)
    c: A 1920x1080 canvas.
    x: A 2D context for that canvas.

show FPS hide FPS share 2 remixes fullscreen

tomxor

remix of d/35004 by u/NiVZ

function u(t) {

for(c.width|=i=63;i--;)'筯璓珧秧䧭秏篏䤧篯积'.charCodeAt(t%10)&1<<i&&x.fillRect(14+i%3<<6,7+i/3<<6,64,64)

Mar 6 2026 9:38 PM UTC

}// 95/140

Please log in (or register) to post as a new dweet (copy-paste code somewhere safe to save it meanwhile).

LECO - Unicode Bitpacked

u/tomxor

This is actually 115 bytes so only an 11 byte reduction over hex encoding, because each of the 10 codepoints takes up 3 bytes each when utf8 encoded, (over the wire, in the DB or in a local file)
u/dee-gomma

Top!
u/NiVZ

Loving seeing all the remixes. I've had another observation. The top left and bottom right segments are always filled. That means the binary can be reduced from 15 bits to 13 bits. Or a max value of 32,767 to 8,191. Would that help to compress things further?
u/tomxor

@NiVZ redundancies are a good thing to look for, but the tricky thing is figuring out if it's worth the extra code to pull out the info from the other side, sometimes you just gotta try and see if it saves bytes.


      u(t) is called 60 times per second.
      t: elapsed time in seconds.
      c: A 1920x1080 canvas.
      x: A 2D context for that canvas.
      S: Math.sin
      C: Math.cos
      T: Math.tan
      R: Generates rgba-strings, ex.: R(255, 255, 255, 0.5)

dwitter.net