1K JavaScript Madness 131
An anonymous reader writes "JS1k has a simple goal: to get programmers producing demos written in JavaScript that are 1k in size or less. That's just 1024 bytes to play with. There's even additional bonus points on offer if a demo's code can fit inside a single tweet. Now that the contest is finished and there is a top-ten, I'm wondering what they can do if given some extra bytes." I like the Tetris clone. The pulsing wires demo is neat too but kinda stuttery on my machine.
Re:Genetic approach (Score:4, Insightful)
Checking each if it followed the predefined rules would be time consuming. For instance, in Pacman, you might have to have the computer play a full game to check if the rules are met.
Almost all the programs would be utter nonsense.
wtf (Score:1, Insightful)
>>Now that the contest is finished and there is a top-...
WTF tell me I can win shit then say it's over >:/
Re:nice (Score:3, Insightful)
jQuery is for prototyping... if you're depending on it for production systems, you're lazy.
Or saving your employer time and money. Sometimes being "lazy" isn't so bad.
Re:nice (Score:2, Insightful)
Fast, cheap, good. Pick two. [wikipedia.org] If you're able to duplicate all the functionality you need, better than jQuery, in less time than it would have taken to use jQuery then good for you! For those of us bound by reality, perfection comes at a cost. What if, in the time it takes you to ship the "Highest Quality" product, your competitor pushes their "Good Enough" product (or prototype) out the door, corners the market and steals your lunch?
Depending on your application, you could still have the last laugh but recall twitter and the downtime it suffered in the beginning, or the recent (and not so recent) security vulnerabilities. If you wrote a complete, bug-free, "Highest Quality" version of Twitter, without any security vulnerabilities or downtime, and you released it tomorrow, how many people would jump-ship and start using your version?