On 11 Sep 2014, at 17:41, Reza Razavipour wrote:
>
>
> function Param(stringifiedValue) {
> if (!this instanceof Param) {
> return new Param(stringifiedValue);
> }
>
> this.value = stringifiedValue;
> }
>
> Is this only doing away with the user having to do a new?
>
> Ca
On Thu, Sep 11, 2014 at 2:41 PM, Reza Razavipour
wrote:
>
> function Param(stringifiedValue) {
> if (!this instanceof Param) {
> return new Param(stringifiedValue);
> }
>
> this.value = stringifiedValue;
> }
>
> Is this only doing away with the user having to do a new?
>
That
On Thursday, September 11, 2014 7:24:07 PM UTC-4, Matt Sergeant wrote:
>
> Two issues: 1) Why would you expect it to be faster? It's pure JS using
> asm.js (which Node doesn't support), vs bcrypt is compiled C code. And 2)
> Being slow is a feature of bcrypt - it makes brute force cracking harder
On Sep 11, 2014, at 4:41 PM, Reza Razavipour wrote:
> function Param(stringifiedValue) {
> if (!this instanceof Param) {
> return new Param(stringifiedValue);
> }
>
> this.value = stringifiedValue;
> }
>
> Is this only doing away with the user having to do a new?
Yes. If a
On Thursday, September 11, 2014 5:41:15 PM UTC-4, Reza Razavipour wrote:
>
> Is this only doing away with the user having to do a new?
>
You're correct, although it's usually `if (!(this instanceof Param))`
instead of `if (!this instanceof Param)` for clarity.
--
Job board: http://jobs.nodejs.o
Two issues: 1) Why would you expect it to be faster? It's pure JS using
asm.js (which Node doesn't support), vs bcrypt is compiled C code. And 2)
Being slow is a feature of bcrypt - it makes brute force cracking harder.
On Wed, Sep 10, 2014 at 10:54 AM, Adrian Lynch <
adrian.ly...@concreteplatform
Sorry, missed your reply. Replies inline.
On Fri, Sep 5, 2014 at 5:37 PM, enormouspenguin wrote:
> Great explanation. Although, It took novice-me quite some time to dig in and
> digest. V8 is really "pretty large and complex" just as you said. The topic
> of V8 deserve full-time dedication in or
function Param(stringifiedValue) {
if (!this instanceof Param) {
return new Param(stringifiedValue);
}
this.value = stringifiedValue;
}
Is this only doing away with the user having to do a new?
Can someone explain?
--
Job board: http://jobs.nodejs.org/
New group rules:
h
Yea, I've never setup node on Windows but it looks to me like that warning
means it couldn't place a shortcut, presumably on your desktop. I'm not
sure what the shortcut would be for but I can assume maybe it launches CMD
straight into the the Node REPL shell.
On Sep 9, 2014 8:15 PM, "joegreen690 v
On Sep 10, 2014, at 11:54 PM, John Wang wrote:
> Hello fellow Node users,
>
>I just started learning node.js and some of the tutorials are not too
> complete. Do any of you have great tutorials for learning node and hopefully
> more advanced ones as well?
There's a huge pile of resources
Check out http://nodeschool.io
Gary Katsevman
gkatsev.com
On Wed, Sep 10, 2014 at 11:54 PM, John Wang
wrote:
> Hello fellow Node users,
>
>I just started learning node.js and some of the tutorials are not too
> complete. Do any of you have great tutorials for learning node and
> hopefully m
Nice
On Saturday, August 30, 2014 5:09:46 PM UTC-4, Dean Landolt wrote:
>
> I was trying to find a clean way to adapt co to be able to be able to
> yield promise or non-promise values (e.g. use yield like the `when` method
> of a lot of promise libs), so I started hacking out features. By the ti
Ok, I'm falling for it.
What syntax style? Show one specific example that will not work with
harmony?
Do you even know what changes it brings?
Do you know that some harmony features are already shipped, not just in
Chrome, but also Firefox? And no pages are being broken?
On Sep 11, 2014 8:09 AM, "
On Wed, Sep 10, 2014 at 9:43 PM, Ep Ga wrote:
> I'm more so speaking on syntax style... are we going to have to be force
> to use the enw syntax style or will there be a choice in the programming
> style we prefer?
>
> like callback function and so on.
>
> dark days ahead I see... dark days.
14 matches
Mail list logo
