Home-assistant also has a great homebridge plugin (https://github.com/home-assistant/homebridge-homeassistant) to easily bridge devices to HomeKit. I got home-assistant talking to zwave and zigbee with a Linear HUSBZB-1 stick (new version does both) and finally threw my wink hub in the garbage. Even through Home app -> homebridge -> home-assistant, everything is super fast and 100% local, unlike most of the commercial hubs.
But we either elect them or elect the reps that appoint them, and we have (some) recourse to make them explain their reasoning, which they usually offer openly.
Your guide mentions setting window size and taking screenshots, which I thought were not currently working via chromedriver. Do you know if that was fixed or is there something else going on?
My outgoing message is a close proximity iPhone recording of my 93 dodge dakota's door buzzer. Seems to also solve the VM problem, although the diligent VMers express confusion often. But those aren't VMs I'm interested in receiving, so it kinda works out.
In the case of left-pad, 2538464 of its 2550569 downloads last month are attributed to dependents of the line-numbers package (https://www.npmjs.com/package/line-numbers). So it would appear that relatively few people directly rely on left-pad, which highlights the importance of vetting the dependencies of dependencies.
They're only exported to the sub shell (bash on last line of cli script). Quitting the sub shell would restore them. Perhaps you were confused by the absence of `service:$` in the prompt for the upload command, which I believe was an oversight.
My best argument so far for the (mostly symbolic) raising of the minimum wage had been that going from ~$7 to ~$10-15 is approximately doubling the purchasing power of individuals who need it most (and will use it), at a low cost to everyone involved. It's an amazingly good return on a relatively tiny social investment. The best argument against it that I've seen is that black-teen unemployment goes up dramatically every time the minimum wage increases. However, it turns out that those scary data points (promoted usually by libertarian thinktanks) exactly correlate with general economic recession periods.
Never once did I imagine that employee turn-over would have such a huge economic impact, but it makes total sense. I've definitely known that happy employees prefer to keep working, but I never connected the dots to dollars spent on boarding new employees. And now I have a talking point that the hardest "show me the money" opponent can wrap her head around without accusing me of appealing to emotion or morality.
I welcome more talking points (pro and con) since I'm not formally educated in economics.
There are in fact plenty of hardcore bands from past and present with non-white/female/lgbt members. Bad Brains, Limpwrist, The Comes... Of course there are some openly anti-female/non-white/lgbt bands, but they're by no means the norm. My experience in punk and hardcore was defined by the open and accepting nature of the people in the scene. Our local venue's official motto was "NO RACIST, SEXIST, OR HOMOPHOBIC SHIT TOLERATED" (Lucy's Record shop in Nashville)
But both require a healthy ecosystem of packages to be any good at all. Right now the existence of io is making package authors choose to support one or the other or do the extra work to support both. Node is getting worse for that. It's a little less of a worry now that node 0.12 is out, but the politicization of the split is just going to make developers choose sides and focus their efforts on one or the other. And considering the fact that both use NPM for package distribution, package management is going to get more difficult, not easier.
I think you nailed it with "when it's possible." What about when it isn't? They're clearly divergent projects, so now you have to keep track of whether every npm package you use supports Io or Node, and which version of each. Package authors are now responsible for supporting one or the other, or becoming an expert on the differences in order to support both. It's a crappy burden on all parties involved.
I believe it's implied the finance sector knows they're draining the high-skilled worker pool, meaning R&D-heavy businesses won't be able to find the employees they need to succeed. So businesses with collateral are a better bet.