brettz9

{
    "gitlens.hovers.currentLine.over": "line",
    "gitlens.currentLine.enabled": false,
    "gitlens.codeLens.enabled": false,
    "gitlens.hovers.enabled": false,
    "editor.accessibilitySupport": "off",
    "editor.fontSize": 17,
    "editor.minimap.enabled": false,
    "editor.acceptSuggestionOnEnter": "off",
    "editor.quickSuggestions": { "other": false, "comments": false, "strings": false },

brettz9

{
	// Place your snippets for javascript here. Each snippet is defined under
	//  a snippet name and has a prefix, body and
	// description. The prefix is what is used to trigger the snippet and
	//  the body will be expanded and inserted. Possible variables are:
	// $1, $2 for tab stops, $0 for the final cursor position,
	// and ${1:label}, ${2:another} for placeholders.
	// Placeholders with the same ids are connected.
	// Example:
	// "Print to console": {

brettz9

Plain JavaScript + TypeScript-flavored JSDoc (i.e., no need for TypeScript syntax)

Here are some basic tips for beginners trying to use TypeScript tooling against plain JavaScript + JSDoc files.

TypeScript-style documentation syntax is JSDoc, it's just a different dialect of JSDoc as far as which JSDoc tags have formally defined behavior, what the types are (there are many more available in the TypeScript flavor), and what the allowable syntax is (the TypeScript team tried to hew closely to JSDoc, but they avoided @module in favor of allowing import() of third party types and they don't yet support certain tags in a type-aware way--though for doc tools unrelated to type-checking it might not matter).

brettz9

$ ffmpeg -i "Efficient-Searches-and-Shortcuts-1-SD-480p.mov" "Efficient-Searches-and-Shortcuts-1-SD-480p.webm"

ffmpeg version 3.3.4 Copyright (c) 2000-2017 the FFmpeg developers
  built with Apple LLVM version 9.0.0 (clang-900.0.37)
  configuration: 
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100

brettz9

I understand your argument about force, and although I very much sympathize with the general tendency to seek to do things without what one could in a sense call "force", I think there are a few factors which are obscuring matters here.

For one, I think we have to be careful that we are not engaging in a fallacy of equivocation. While it is especially disconcerting to see "force" being used ot justify even well-intended behaviors, when understood as compulsion under threat of violence or imprisonment by the state, obviously we are not talking about anything remotely similar in degree here (assuming all would even agree that this is indeed a form of compulsion at all).

So saying "it's always wrong to force things on people" might be seen as gaining credence by attacking the strawman of a supposed claim justifying physical compulsion. This brings me to my second point which is about the polemical-sounding nature of engagement with such a fallacy.

Polemicists use ambiguous language such as this to obscure mat

brettz9

'use strict';

// Todo: Move to own repo

/**
 * You can use this in your `.eslintrc.js` as follows...
 *
 * @example
 *
 * 'use strict';

brettz9

/*
import resolve from './resolve.js';
await resolve('tap', { basedir: __dirname });
*/

const _resolve = require('resolve');
const resolve = (path, opts = {}) => {
  // eslint-disable-next-line promise/avoid-new
  return new Promise((resolve, reject) => {
    // eslint-disable-next-line promise/prefer-await-to-callbacks

brettz9

# dist

# very unfortunately, it seems this can't be overridden apparently
#    per https://eslint.org/docs/user-guide/configuring
#   "ESLint always ignores files in /node_modules/* and /bower_components/*"
!node_modules

!.eslintrc.js
!.eslintrc-script.js

brettz9

/* globals hyperHTML, jml, Interpolator */
// Relies on getInterpolator of Jamilih: https://github.com/brettz9/jamilih

'use strict';

window.hyperJamilih = (() => {

const map = new Map();
const {bind: hyper} = hyperHTML;

brettz9

'use strict';

// Todo: Move to own repo

const {i18n} = require('intl-dom');
const walk = require('pug-walk');
const fileFetch = require('file-fetch');

global.fetch = fileFetch; // For `intl-dom`