minsung-kim

[minsung-kim @minkim9]

https://t.co/Mjmr2YqpK9
It’s awesome! Thank you all contributors, I admire you guys all!

[minsung-kim @minkim9]

NullishCoalesing operator helps us to run our code accurate, Look,
const data = 0;
message = data ?? ‘undefined’;
console.log(message);
You will see the result “0” while “message = data || ‘undefined’ returns “undefined”. #javascript #NullishCoalasing

[minsung-kim @minkim9]

Spread operator (...) only copies a referencing address. So be careful if you update values in your original object, consequently, newer one has updated values. #JavaScript #SpreadOperator

[minsung-kim @minkim9]

Non flowing mode is useful for implementing protocols, because it is more flexible to control. See https://t.co/0H9tZixwoW([size]), you can pull the data with fixed size. Moreover, it supports async iterators as well. #Nodejs #nodejssteams #streams #readablestreams

[minsung-kim @minkim9]

Thanks pipe(), it allows us to connect different processing unit. Only prerequisite is the data type of which is produced by previous method has to supported by next stream. #javascript #Nodejs #nodejsstreams #streams

[minsung-kim @minkim9]

Early return principal that you have a reduction of nesting level.
“if (err) { return cb(err) } // do something” Anyway, due to return value of async is usually ignored, we can write shortcut like it. #js #javascript #earlyReturnPrinciple #callbackhell

[minsung-kim @minkim9]

To prevent possible memory leak due to too many listeners, Node provides you a warning when it’s counter is exceeding 10. And you configure it with setMaxListeners() method. #nodejs #js #eventemitter

[minsung-kim @minkim9]

While process.nextTick runs before any scheduled IO, it can make IO starvation. But it never happens with setImmediate(). This function queues current task in an event loop so that it will run after all IOS have been processed. #js #node #callback

[minsung-kim @minkim9]

process.nextTick() it is the way of running your sync code working with async. It probably prevents some issues that could be happened due to using sync and async together. Since it push your sync call to the top of the event loop. #js #node

[minsung-kim @minkim9]

https://t.co/S5C9i6RrZx

[minsung-kim @minkim9]

I had a same issue. With the tunning of winrm do not excute too many creation of VM at once. https://t.co/0cksuJQolu

[Merlin from Belgium @MerlinFromBE]

@steingeerinck blogged on a WinRM related #SCVMM issue: #HyperV cluster shows “Needs Attention” in SCVMM https://t.co/6JbJfgRZCo

[minsung-kim @minkim9]

Be the L3 switch for BGP and ECMP required for the WS16 SLB right? #WS16 #AzureStack #HyperV

[minsung-kim @minkim9]

@lyndon678 but I think system center might help to increase operational efficiency. For example deploying, monitoring, backup and so on.

[minsung-kim @minkim9]

@renelindeboom
Thank you to share it, but the URL you written is not working.

[minsung-kim @minkim9]

@s1950356 광우형 맞지?

[minsung-kim @minkim9]

@merongyi 전 시원한 연휴 동안 내내 누워��었어요... : )