outcoldman

# The MIT License
# SPDX short identifier: MIT

# Further resources on the MIT License
# Copyright 2017 Denis Gladkikh (https://www.outcoldman.com/en/archive/2017/07/19/dbhist/)

# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

robertknight

How to test NVDA screen reader behaviour on a Mac:

1. Download Microsoft Edge VM from https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
2. Download Virtualbox and import the Edge VM image.

Then in the VM:

1. Install guest addons in the VM
2. Download & install latest NVDA from nvaccess.org
3. Download & install SharpKeys and use it to map left an alternative key (eg. Left Ctrl) to the Insert key. This is needed because Macs do not typically have an “Insert” key which is the prefix for many NVDA commands.

csswizardry

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vs **/*<partial file name><Tab>

sburnicki

# Provide locationis.ini to mount in the server
# Either provide locations yourself or use the official ones with an API key.
# See https://sites.google.com/a/webpagetest.org/docs/private-instances/locations for details

docker run -v $HOME/tmp/locations.ini:/var/www/html/settings/locations.ini -p 8080:80 --name wptserver iteratec/wptserver
#            -> mounts the locations.ini file in the server               -> use localhost:8080 to access

kylemanna

Price breakdown vs DigitalOcean, Vultr and Linode:

RAM / CPU Cores / STORAGE / Transfer

$5/mo
LightSail: 512MB, 1, 20GB SSD, 1TB
DO:        512MB, 1, 20GB SSD, 1TB
VULTR:     768MB, 1, 15GB SSD, 1TB

$10/mo

nathansmith

/*
  This method works similarly
  to jQuery's `closest` method.

  ```
  $('.foo').closest('.bar')
  ```

  Except, instead of returning an
  element, it executes a function.

developit

/** Async version of Array.prototype.reduce()
 *  await reduce(['/foo', '/bar', '/baz'], async (acc, v) => {
 *    acc[v] = await (await fetch(v)).json();
 *    return acc;
 *  }, {});
 */
export async function reduce(arr, fn, val, pure) {
  for (let i=0; i<arr.length; i++) {
    let v = await fn(val, arr[i], i, arr);
    if (pure!==false) val = v;

alekseykulikov

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

acdlite

// getComponent is a function that returns a promise for a component
// It will not be called until the first mount
function asyncComponent(getComponent) {
  return class AsyncComponent extends React.Component {
    static Component = null;
    state = { Component: AsyncComponent.Component };

    componentWillMount() {
      if (!this.state.Component) {
        getComponent().then(Component => {

froots

// in /src directory

import {kphToMph} from './convert';

class Car {
  constructor(speed) {
    this.speed = speed;
  }

  getSpeedInMph() {