My sister has only daughters, my mom has only sisters, half of my aunts only have daughters, my grandmother only has sisters... I've heard them say "miss you guys" to each other more times in my life than I can count... it's gender neutral enough.
In fact, I have yet to see an actual *woman* take offense to this phrase, it's always some SJW man that seems over-sensitive to it. I saw someone bring it up in #node.js over someone asking "mind if I ask you guys a question?" once. Everyone seemed to kowtow to the statement, I think I'm the only one in the channel that challenged it and stand by that assertion. If someone decides that the word "roses" is suddenly offensive, it shouldn't be society that necessarily adapts.
Personally, I find the term "git" pretty offensive, but I'm not championing changing the name. The biggest irony is when "github" forced the change of a repo that had a term deemed offensive... There's a matter of intent and context to consider... "Only guys will get it, chicks just can't understand." would be offensive, and I understand that... in this context it's used as a generic pronoun.
I self-identify as a 68yo Black Lesbian Woman whose personal pronoun is "my lord and master".
Pretty cool, but wonder how it handles synthetic events compared to react... It seems to me synthetic events and supported nodes should be as close to react as possible.
I'm also curious if this supports svg and associated elements as well.
I think it depends on the size and complexity of the original application, as well as the skill, experience and knowledge of the team(s) doing the work.
In this case, it looks like around 2.5 years for cars.com... My experience tells me at least 6 months for a moderately complex application. I've replaced a few microservices in days.
Just a mention, it's best to use connection pooling with your DB layer... many will have this functionality in the box... you create your pool and execute against the pool.
Creating and closing lots of connections leads to poor performance.
I would think that `require('please-upgrade-node')('./your-package-root')` would be more appropriate, than a nested require, this way the test can run, then the please-upgrade can simply require(...) on its' own.
Although not mentioned, if you are using babel anyways (for React), may as well get async/await support, which makes redux-thunks *MUCH* easier to use and understand for async operations, for most use cases... no it won't support really weird edge cases with multiple events against the same resource, but it's good enough for the vast majority of use cases in normal conditions.
I would think that `require('please-upgrade-node')('./your-package-root')` would be more appropriate, than a nested require, this way the test can run, then the please-upgrade can simply require(...) on its' own.