nickfargo

6 ms·

1.
by nickfargo 9y ago
The term is not merely a recent appropriation. Parametric polymorphism is a concept from functional programming and formal type theory, with application far beyond just JavaScript.
2.
by nickfargo 9y ago
That's interesting, because I find #() rather less easy to parse compared to (comp) or (partial) for otherwise equivalent expressions. At a glance I know that (comp f g h) and its flat list of arguments expresses a simple function co
3.
by nickfargo 9y ago
This is a different notion of polymorphism, yes. Suggested reading: http://mrale.ph/blog/2015/01/11/whats-up-with-monomorphism.h...
4.
by nickfargo 10y ago
> just use a closure! Of course, but that means allocating a closure object per method per instance . When people say they want private variables, they mean they want them available in regular prototype-mounted methods. Proxies are one
5.
by nickfargo 12y ago
ls -l /usr/local/bin/node lrwxr-xr-x 1 502 staff 4 Jan 13 20:10 /usr/local/bin/node -> iojs Is this necessary?
6.
by nickfargo 12y ago
A generator is an iterator created and returned by a generator function .
7.
by nickfargo 12y ago
Faster read: http://en.wikipedia.org/wiki/Chimera_(genetics)#Humans
8.
by nickfargo 13y ago
People whose opinions of you really matter know that the green boxes don't.
9.
by nickfargo 13y ago
Referencing C10k implies yes . Threads cost.
10.
by nickfargo 13y ago
The "looks more pleasant?" test can be valid only between cljs/Om and the CoffeeScript from which the generated JS was compiled. By presenting Coffee's not-quite-idiomatic JS output as the counterpoint, the otherwise wel
11.
by nickfargo 13y ago
Pretty big rush to judgement. Slice off a copy of the arguments if you need them, but pall = -> console.log line for line in arguments; return would have done just fine there. One can be annoyed by `return` in tail position, or de
12.
by nickfargo 13y ago
And moreover, describe 'syntax after upgrading', -> it 'should be even meatier', -> expect parentheses.required .toBe false Very tidy.
13.
by nickfargo 13y ago
I have understood “performant” to suggest a soundness of design that causes something to be “fast”. In the context of algorithms, certainly the distinction is blurred, but in other, higher-level contexts, it can be meaningful.