defunctzombie

The spec has moved to a repo: https://github.com/defunctzombie/package-browser-field-spec to facilitate collaboration.

ivyleavedtoadflax

---
title: "Xtable examples"
subtitle: "From [this thread](http://stackoverflow.com/questions/32005471/simple-example-of-using-tables-knitr-for-latex)"
author: "Matthew Upson"
date: "15 August 2015"
output: pdf_document
---

```{r}
library("xtable")

anvaka

npm rank

This gist is updated daily via cron job and lists stats for npm packages:

1. Top 1,000 most depended-upon packages
2. Top 1,000 packages with largest number of dependencies
3. Top 1,000 packages with highest PageRank score

killercup

macro_rules! max {
    ($x:expr) => ( $x );
    ($x:expr, $($xs:expr),+) => {
        {
            use std::cmp::max;
            max($x, max!( $($xs),+ ))
        }
    };
}

mastef

/*

  Watch out, os.IsExist(err) != !os.IsNotExist(err)

  They are error checkers, so use them only when err != nil, and you want to handle
  specific errors in a different way!
  
  Their main purpose is to wrap around OS error messages for you, so you don't have to test
  for Windows/Unix/Mobile/other OS error messages for "file exists/directory exists" and
  "file does not exist/directory does not exist"

aparrish

jFransham

Achieving warp speed with Rust

Contents:

• Number one optimization tip: don't
• Never optimize blindly
• Don't bother optimizing one-time costs
• Improve your algorithms
• CPU architecture primer
• Keep as much as possible in cache
• Keep as much as possible in registers

talon

Install Docker On Windows 10 Home

"Windows Home Docker Desktop requires Windows 10 Pro or Enterprise version 15063 to run." So says the Docker Installer however, the Docker forums beg to differ

The workaround is to manually image the Hyper-V and Containers features, then trick the installer into thinking you're using Windows Pro.

TL;DR

1. clone this gist somewhere locally git clone https://gist.github.com/4191def376c9fecae78815454bfe661c.git windows_home_docker
2. Run windows_home_containers.ps1 in an Administrative Powershell

sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.