Should we just declare a 184 byte limit… by yonatan

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 fullscreen

yonatan

remix of d/9345 by u/yonatan

function u(t) {

eval(unescape(escape`景爨硛昽❦楬汒散琧崨〬〬挮睩摴栽椽ㅥ㌬椩㭩ⴭ㭸学崨匨琩⨱㤹⭓⡩⤪洫㔰〫匨稽椪⨮㔩⩭⭭⩓⡴⤪ㄮ㔬䌨琩⨪㈪㤹⭃⡩⤪洫㈰〫䌨稩⩭ⱺⱺ⤩洽椯ㄴⱸ⹦楬汓瑹汥㵠桳氨㌰ⰳ㔥Ⱔ笨䌨㤫椭匨琩⤫ㄮ㔩⨪㕽╠`.replace(/u(..)/g,"$1%")))

Aug 25 2018 12:30 AM UTC

}// 140/140

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

Should we just declare a 184 byte limit and be done with all this compression business?

u/cantelope

For some time, there has been https://codegolf.tk, which has categories for 140, 512, and 1024 byte dweets. Full disclosure: I created the site.
u/f8f82804

I'm with @cantelope. If you resort to compression, that's a choice.
u/aleamb

amazing dweet!
u/yonatan

source: for(x[f='fillRect'](0,0,c.width=i=1e3,i);i--;x[f](S(t)*199+S(i)*m+500+S(z=i**.5)*m+m*S(t)*1.5,C(t)**2*99+C(i)*m+200+C(z)*m,z,z))m=i/14,x.fillStyle=hsl(30,35%,${(C(9+i-S(t))+1.5)**5}%`


      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