nazgob

# you have ctags but it does not work...
$ ctags -R --exclude=.git --exclude=log *
ctags: illegal option -- R
usage: ctags [-BFadtuwvx] [-f tagsfile] file ...

#you need to get new ctags, i recommend homebrew but anything will work
$ brew install ctags

#alias ctags if you used homebrew
$ alias ctags="`brew --prefix`/bin/ctags"

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

Rich-Harris

( function ( global ) {

	'use strict';

	var Promise, PENDING = {}, FULFILLED = {}, REJECTED = {};

	if ( typeof global.Promise === 'function' ) {
		Promise = global.Promise;
	} else {
		Promise = function ( callback ) {

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

a-r-d

#first install all the things:
sudo apt-get install flac ffmpeg mp3splt libav-tools shntool

# Okay first lets do an MP3:
# input files:
#   --> cd.ape
#   --> cp.cue
# (there are other options, like bitrate, but this is just the bare bones)
avconv -i cd.ape cd.mp3

OleksiyRudenko

Merging a repo into another one

Initial situation:

1. Repository A we want to become a part of another repository.
2. Repository B we want repo A to be merged into.

Targets:

1. We want source code from repo A to be located under a sub-directory in repo B and repo A history stored in a dedicated repo B branch.
2. We do not want original repo A be changed or corrupted.

OleksiyRudenko

You may want to employ the Parcel backed boilerplate that implements the solution described below.

• Targets
• Pre-requisites
• Solution
• Enjoy

Targets

DavidWells

/* Helper buddy for removing async/await try/catch litter 🗑 */
function O_o(promise) {
  return promise.then(data => {
    if (data instanceof Error) return [data]
    return [null, data]
  }).catch(err => [err])
}

/* Look ma, no try/catch */
async function usageExample(params) {

sebmarkbage

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr