paulirish

<!-- formatting fun #1: tables! -->

<!-- use whitespace to mimic the layout you want. leave off optional end tags for readability -->

<table>
  <caption>Selector engines, parse direction</caption>
  <thead>
      <tr><th>Left to right            <th>Right to left 
  <tbody>                              
      <tr><td>Mootools                 <td>Sizzle

travismillerweb

/*
Gmail/Google Reader Sidebar Scroll Shadows
-------------------------------------------
Neat effect that mimics the scroll shadows that appear in the GOogle sitde bar and visually cues users to scroll up or down depending on their position.
Credit goes to Lea Verou for this awesome find.

Source:
Lea's Talk: http://www.youtube.com/watch?v=3ikye7Qc7Ak 	
Code Source: http://lea.verou.me/more-css-secrets/#slide9
		

subfuzion

Install with Homebrew

brew install mongodb

Set up launchctl to auto start mongod

$ ln -sfv /usr/local/opt/mongodb/*.plist ~/Library/LaunchAgents

/usr/local/opt/mongodb/ is a symlink to /usr/local/Cellar/mongodb/x.y.z (e.g., 2.4.9)

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;

akatrevorjay

#!/bin/zsh
# git-fshow - git commit browser
#
# https://gist.github.com/akatrevorjay/9fc061e8371529c4007689a696d33c62
# https://asciinema.org/a/101366
#

git-fshow() {
	local g=(
		git log

bvaughn

This API was removed in React 17

---

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

manzoorwanijk

import * as yup from 'yup';
import { setIn } from 'final-form';

const validationSchema = yup.object({
	email: yup.string().email(),
	shipping: yup.object({
		name: yup.string(),
		phone: yup.object({
			code: yup.string().matches(/^\+\d+$/i),
			number: yup.number().max(10),