JS1k, 1k Javascript demo contest
category: code [glöplog]
I see your 1K ZX81 chess and 1K Javascript chess and raise you 1.5K chess in Befunge :-)
New contest of js1k:
http://js1k.com/2011-dysentery/
I'm part of the jury. Please, send something!
The current money prize is 400$ (the website shows 300$, but it has to be corrected). Not so much right now, but expect it to be higher at some point.
http://js1k.com/2011-dysentery/
I'm part of the jury. Please, send something!
The current money prize is 400$ (the website shows 300$, but it has to be corrected). Not so much right now, but expect it to be higher at some point.
Anybody submitting something for the 2013 edition? Deadline is March 31st
Hulde voor je entry, inopia!
Still haven't decided what to do, but yes, I'm in!
I've got two ideas but only time for one:
I've got two ideas but only time for one:
- A "tool" similar to some other entries but with a different twist
[*] A "big gun" entry kinda like WOLF1K or the CHESS1K were.
I found that other people were using a compressor that does recursive global replacement. I wrote my own version of it and got another ~100 bytes to play with. New version: http://pastie.org/6470981
@p01: I'm looking forward to your entry. js1k needs more demoscene :D
@p01: I'm looking forward to your entry. js1k needs more demoscene :D
i'm divided to participate or not, don't have anything in my mind worthy of the effort right now. but if i get a nice idea and am too tired of working on other stuff, i guess i might.
I'm sending something. Get ready :P
Let's see which way Texel twists my arm with his entry. Man, knowing you I would hardly be surprised by some BeautyPi kind of thing.
Inopia: It's getting really nice! If you really run out of space you can always switch to a normal eval(_) ( instead of the global eval (1,eval)(_)
Inopia: It's getting really nice! If you really run out of space you can always switch to a normal eval(_) ( instead of the global eval (1,eval)(_)
@p01: thanks! I think this version is the final though, I shaved off a few bytes but I don't really have any use for them atm. I used (1,eval)(_) because it's supposed to be slightly faster?
@texel: it'd better not be the umpteenth JS low-res raymarching toy :P
@texel: it'd better not be the umpteenth JS low-res raymarching toy :P
WE WANT MORE P01 BIG GUNS!!!!!
1019 bytes, fixed the gaps between the polygons. I had to squeeze quite a bit before I could add the additional a.stroke and a.strokeStyle calls.
http://pastie.org/6495590
uncompressed: http://pastie.org/6495708
http://pastie.org/6495590
uncompressed: http://pastie.org/6495708
Inopia: why don't you mix the color for and the line for in the same?
@texel: haha, oh wow, missed that one :D
And here it is: http://www.romancortes.com/blog/furbee-my-js1k-spring-13-entry/
great stuff as usual texel
quite slow though, hope some browser devs use this example to optimize their stuff.
now *that* is impressive texel. Brilliant work.
texel: Nice iteration of the technique and spot on with the topic of the contest! Well done sir!
Aaawwh. Sweet ;)
Texel: that's beyond cool!
@texel: we have a winner :)
Nice bee! :]
That's excellent!
Great bee.