elrumordelaluz

#!/bin/bash

# source https://github.com/feathericons/feather/pull/608/commits/bc3040710dfdbff3d0a849ae0ac6990d7884b9d4

# This script uses:
#   - Inkscape to convert every icon from strokes to paths
#   - Fontcustom to convert all svg icons to TTF font
#   - GNU Parallel to speedup process
#   - Xvfb (X11 virtual frame buffer) to prevent show Inkscape window for
#     every icon. Its not necessary, but highly recommended

elrumordelaluz

elrumordelaluz

import React from 'react'
import { CodepenIcon } from '../icons'

const CodepenButton = ({ code, className }) => {
  const codepenObject = {
    title: 'Title',
    description: 'Some description',
    editors: '100',
    ...code,
  }

elrumordelaluz

A story of ice, fire, and vendor prefixes

In standards development, there is always a big catch-22: standards groups need input from developers to create specifications that address real development needs. However, developers are generally not interested in trying out things they can’t use in production. When experimental technologies get widely used in production, the WG is forced to stick with the early, experimental version of the technology, to avoid breaking several existing websites if they change it. Obviously, this completely negates the benefits of getting developers to try out early standards.

Over the years, many solutions have been proposed to address this conundrum, none of them perfect. The universally despised vendor prefixes were one of them. The idea was that every browser would be able to implement experimental (or even proprietary) features with their own prefix prepended to its name. The most common prefixes are -moz- for Firefox, -ms- for IE, -o- for Opera, and -webkit- for Sa

elrumordelaluz

@define --my-theme {
  color: var(--main-color, #bada55);
  font-size: 1em;
  /* ... */
};

.hero {
  apply: var(--my-theme);
  width: 100vw;
  /* ... */

elrumordelaluz

<h3 class="item my-shake shake-constant">Shake</h3>

elrumordelaluz

React ST3 snippets

1. Goto Tools > New Plugin...
2. Paste the snippets
3. Remember to save it with .sublime-snippet extension

elrumordelaluz

/***
 * 
 * Is it ok to declare and use both `mapStateToChildListProps` and `mapStateToParentListProps` 
 * or there is a way to unify. I 'am thinkin if need more `connect()`ed comps will add more `mapStateTo__Props`.
 *
 ***/
 
const Child = ({ ...props }) => (
  <li>
    <h3>{ props.foo }</h3>

elrumordelaluz

# Using JSON.sh as a JSON parser
# Download https://github.com/dominictarr/JSON.sh

function jsonGetValue {
  ./JSON.sh | grep -F -e $1 | cut -f2 | tr -d '"'
}

# Usage
read -r -d '' JSON_DATA <<'EOF'
{

elrumordelaluz

/* Set up Git Configuration */

git config --global user.email "you@yourdomain.com"

git config --global user.name "Your Name"

git config --global core.editor "vi"

git config --global color.ui true