> If a Get and Set can produce a collision and it is not dealt with, then it is unsafe for production. That was confusing to me as well in the article. However they also wrote: > If however, a key is already present in…
Disclaimer: I’m the CTO at Jut and have been with the company since it’s inception. Actually Jut didn't shut down last week. We figured out a much better way to package up our tech and ended up making some big changes…
(Disclosure: I’m the VP Eng at Jut) As Dave pointed out in the blog, we’ve definitely run into our fair share of challenges with the inherent limits of node.js. But on the whole, we’ve found it to strike a good balance…
> If a Get and Set can produce a collision and it is not dealt with, then it is unsafe for production. That was confusing to me as well in the article. However they also wrote: > If however, a key is already present in…
Disclaimer: I’m the CTO at Jut and have been with the company since it’s inception. Actually Jut didn't shut down last week. We figured out a much better way to package up our tech and ended up making some big changes…
(Disclosure: I’m the VP Eng at Jut) As Dave pointed out in the blog, we’ve definitely run into our fair share of challenges with the inherent limits of node.js. But on the whole, we’ve found it to strike a good balance…