| if input volume of (get volume settings) = 0 then | |
| set level to 90 | |
| display notification "On" with title "Mic" | |
| tell application "System Events" | |
| tell appearance preferences | |
| set dark mode to false | |
| end tell | |
| end tell | |
| else | |
| set level to 0 |
| /// Add Gap between the boxes | |
| /// | |
| /// @author Sascha Fuchs | |
| /// | |
| /// @group core - cssgrid | |
| /// | |
| /// @param {list} $boxes - List with box sizes | |
| /// @param {string} $gap - Optional column gap | |
| @function box-gap($boxes, $gap) { | |
| $box: (); |
| <!-- | |
| Complete feature detection for ES modules. Covers: | |
| 1. Static import: import * from './foo.js'; | |
| 2. Dynamic import(): import('./foo.js').then(module => {...}); | |
| Demo: http://jsbin.com/tilisaledu/1/edit?html,output | |
| Thanks to @_gsathya, @kevincennis, @rauschma, @malyw for the help. | |
| --> |
| // The `loader` prop is a Dataloader instance | |
| // https://github.com/facebook/dataloader | |
| class Dataloader extends React.Component { | |
| state = {data: null, isLoaded: false}; | |
| componentWillMount() { | |
| this.prefetchData(this.props); | |
| } | |
| componentWillReceiveProps(nextProps) { | |
| if (this.props.id !== nextProps.id || this.props.loader !== nextProps.loader) { | |
| this.setState({isLoaded: false}); |
| // A loader to transform a partial manifest.json file into a complete | |
| // manifest.json file by adding entries from an NPM package.json. | |
| // https://stackoverflow.com/questions/44232366/how-do-i-build-a-json-file-with-webpack | |
| const fs = require('fs') | |
| module.exports = function (source) { | |
| this.addDependency('./package.json') | |
| this.cacheable() | |
| const pkg = JSON.parse(fs.readFileSync('./package.json')) |
This text is the section about OS X Yosemite (which also works for macOS Sierra) from https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/#mac-os-x
The last time i visited this link it was dead (403), so I cloned it here from the latest snapshot in Archive.org's Wayback Machine https://web.archive.org/web/20170523131633/https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/
| // debug config for running project under vscode debugger | |
| { | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "trace": true, | |
| "name": "Chrome Debug", | |
| "type": "chrome", | |
| "request": "launch", | |
| "url": "http://localhost:8000/", |
I get a lot of questions about what I think about Vue.
I won't comment too much on Vue in general because I'm not familar enough with it, but I'm very familiar with templating systems, and in articles praising Vue, the fact that it uses templating system instead of JSX is almost always cited as a reason to choose Vue. This drives me up the friggin' wall, because the negative side effects of templates are not communicated or discussed. JSX exists for good reasons. To me, JSX is a great simplification and clear improvement over templates.
Template languages are often sold on looking superficially good. I recently ran across yet another one of these articles citing the wonders of Vue, and especially templates. In this article, this JSX example is included:
When Babel 6 came out, it was hard for a lot of packages to upgrade because it was essentially an entirely different category of thing than Babel 5. So what happened was that some packages upgraded, and some didn't — at least not straight away.
Some projects took the prima facie enlightened view that packages should expose untranspiled code, so that the consumers of that code could determine for themselves what needed to get transpiled based on the environments they supported.
That was a costly decision. If I was the author of an app that was using Babel 6, I couldn't import a library that was still using Babel 5 and shipping untranspiled code (because the configs were completely incompatible), and vice versa. Frankly, it was a bloody nuisance. We are bad at anticipating these sorts of issues. It will happen again at some point.
Adding a few extra bytes to pkg.main or pkg.module is a small price to pay for things just working. As well as avoiding the aforementioned headaches, it means that your
| module.exports = { | |
| extends: [ | |
| "strict", | |
| "prettier", | |
| ], | |
| parserOptions: { | |
| ecmaVersion: 2016, | |
| }, | |
| plugins: ["prettier"], | |
| rules: { |
