jed / 140bytes Goto Github PK

=> is a huge win when you can get rid of the hole word function & return

https://github.com/jed/140bytes/wiki/Byte-saving-techniques

In the main page it says:

for and while require the same number of bytes

But it is not the case if you want an infinite loop such as:

for(;;) {
}

over

while(!0) {
}

Or is there something better?

I saw that the Math.floor trick is documented but the not Math.ceil altough it's being used here:

a = 10.5;
~~a; //=> 10
-~a; //=> 11

I was looking at https://github.com/jed/140bytes/wiki/Byte-saving-techniques and the majority of examples on what is byte saving is what something like Uglify should be doing.

Other examples like

setInterval('console.log("z")',100) // after

is a definite no since that's an example of implicit eval call

function(a,b){b=1;...}   // after

is also not good since V8 doesn't like that and it de-optimized code
https://github.com/vhf/v8-bailout-reasons provides good desc of potential issues.

I am just making sure that people who are new to JS don't take these examples and uses them thinking they are doing a good thing.

After OAuth'ing, the "Log in with GitHub"-button redirects me back to the 140byt.es without doing anything.