Be careful with this. If I'm reading your code correctly, you are relying
on the order of that object literal matching the order of the arguments
object. This is not guaranteed, as far as I know. This would cause your
arguments to be matched against the wrong schemas.
I'd suggest replacing the
Seems to work for me. Node v0.11.7, Windows 8
>node-11 --harmony test.js
309.6952980849892
231.88106599263847
257.15388590469956
345.1376415323466
492.82865272834897
159.6157061867416
286.41347005032003
760.6169891078025
25.959153659641743
and so on...
On Sunday, 8 September 2013 18:28:12 UTC+10,
Hi all,
I'm working on a website that does all the basic stuff: permissions,
authentication, CRUD on objects, etc. One thing that has been a bit hard is
passing around the context of a request - the session information, who the
user is, etc.
In everyone's favorite language (Java, obviously) yo
On Monday, 9 September 2013 08:38:31 UTC+10, Adam Ahmed wrote:
>
> Hi all,
>
> I'm working on a website that does all the basic stuff: permissions,
> authentication, CRUD on objects, etc. One thing that has been a bit hard is
> passing around the context of a request -
gt;for
it is *intense*! You wrap *everything*.
I'll definitely be giving it a go. Thanks a ton!!
Adam
On Monday, 9 September 2013 13:49:14 UTC+10, Forrest L Norvell wrote:
>
> On Sun, Sep 8, 2013 at 3:38 PM, Adam Ahmed
> > wrote:
>
>> Hi all,
>>
>> I
Kinda funny how hard it is to explain this.
I thought it was interesting so I gave it a crack as well:
http://www.noiregrets.com/blog/2013/10/19/e40baf63/NodeJS-module-exports-vs-exports
TL;DR: variables are not the values they point to.
Maybe that helps yougen or maybe I'm beating a dead horse.
Node was doing fine for me until maybe 2-3 weeks ago. I'm not sure what
changed, but now every time I run a grunt or gulp task, it becomes
_extremely_ slow. Even just getting an error like "Fatal error: unable to
find local grunt" goes from taking 629ms to taking 34 seconds.
https://monosnap.co
