Reputation
489
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 13
Newest
 Custodian
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 21 votes cast
1d
awarded  Custodian
1d
reviewed Edit Why does Node.js startup time vary so wildly?
1d
revised Why does Node.js startup time vary so wildly?
Just trying to introduce more details.
1d
asked Why does Node.js startup time vary so wildly?
Jun
24
comment Is there any reason to use the “var” keyword in ES6?
@RayToal I agree with 97% of what Kyle Simpson says, but his reasons to keep using var seem thin to me, and not enough to warrant having a third kind of variable that jumps around. You can scope a let to a whole function simply by placing it at the top of the function, which is much clearer in intent than writing var in a block (in order to have it hoisted out of that block so you can then use it outside the block - weird). He warns that if you scope a let to a function then "it's just position that signals the difference, rather than syntax", but I think that's a good thing.
Jun
16
awarded  Popular Question
Jun
15
awarded  Nice Question
Jun
12
awarded  Good Question
Jun
4
asked Any point in using ES6 Map when keys are all strings?
May
6
awarded  Yearling
Apr
14
accepted Why are native ES6 promises slower and more memory-intensive than bluebird?
Apr
14
comment Why are native ES6 promises slower and more memory-intensive than bluebird?
Good answer, thank you. I didn't realise new Promise was so slow. Your anti-patterns page doesn't mention that btw.
Apr
13
accepted How to avoid server-pushing assets to clients that already have them cached?
Apr
10
revised Why are native ES6 promises slower and more memory-intensive than bluebird?
added 62 characters in body
Apr
10
asked Why are native ES6 promises slower and more memory-intensive than bluebird?
Apr
10
awarded  Popular Question
Apr
9
awarded  Nice Question
Apr
9
accepted How much should I be using 'let' vs 'const' in ES6?
Apr
9
comment How to avoid server-pushing assets to clients that already have them cached?
That's interesting. So if the client 'refuses' it, does the server just stop mid-transfer? And doesn't this still waste a lot of bandwidth (depending on how quickly the server receives the refusal frame)? Compared to what we have now (where assets are only transferred the first time a new client visits your site, albeit with a round trip penalty), it sounds like server-pushing assets would be very bandwidth intensive.
Apr
9
asked How much should I be using 'let' vs 'const' in ES6?