[–] thomasfoster96 11y ago ↗ +1 for implementing a Lisp in JavaScript that compiles to C.Just a heads up, the main script in your package.json points to a file that doesn't exist.
[–] mikkom 11y ago ↗ Why the obfuscated names? I mean> There is reduce (REDC), array (ARRY), filter (FLTR) and each (EACH).It would be much cleaner to just use full names (array instead of ARRY) [–] Dewie 11y ago ↗ It wouldn't be properly UNIX-like without randomly omitting vowels. [–] hultner 11y ago ↗ Those precious bytes of disk space though [–] madaxe_again 11y ago ↗ I dare say "it is intended to be very terse" answers that.Cleaner, yes, but more keystrokes! [–] mikkom 11y ago ↗ They are all uppercase so if you calculate that shift on every keystroke it's actually more :-) Or at least the same with array for example.EACH has more keystrokes than each.
[–] Dewie 11y ago ↗ It wouldn't be properly UNIX-like without randomly omitting vowels. [–] hultner 11y ago ↗ Those precious bytes of disk space though
[–] madaxe_again 11y ago ↗ I dare say "it is intended to be very terse" answers that.Cleaner, yes, but more keystrokes! [–] mikkom 11y ago ↗ They are all uppercase so if you calculate that shift on every keystroke it's actually more :-) Or at least the same with array for example.EACH has more keystrokes than each.
[–] mikkom 11y ago ↗ They are all uppercase so if you calculate that shift on every keystroke it's actually more :-) Or at least the same with array for example.EACH has more keystrokes than each.
8 comments
[ 5.8 ms ] story [ 29.6 ms ] threadJust a heads up, the main script in your package.json points to a file that doesn't exist.
> There is reduce (REDC), array (ARRY), filter (FLTR) and each (EACH).
It would be much cleaner to just use full names (array instead of ARRY)
Cleaner, yes, but more keystrokes!
EACH has more keystrokes than each.