This is a variation of BEM/SUIT/RSCSS methodologies.
You won't always need utility classes, but if you want to use them, do in this way.
Syntax: u-<utilityName>
.u-utilityName {}
{... | |
"scripts": { | |
"postinstall": "node patch.js", | |
... | |
} | |
} |
#!/bin/sh -e | |
# A simple script to keep a tidy ~/code directory organized by owner & then repo | |
# When the script is done, just hit command-v to switch into the directory | |
# (Github and Mac only. Sorry, openness!) | |
# | |
# Usage: | |
# gloan <org>/<repo> | |
# Or: | |
# gloan <org> <repo> |
/** | |
* @method: PubSub | |
* */ | |
;(function(global) { | |
'use strict'; | |
function PubSub () { | |
this.topics = {}; | |
}; |
(by @andrestaltz)
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.
Hoje algo cômico e surreal aconteceu na comunidade FrontEnd Brasil. Algo chocante a ponto de desanimar o mais engajado dos participantes.
Após postar um Gist sobre moment com um código bastante didático, Berger foi rechaçado pelo moderador da comunidade, Jean Carlo Nascimento. Ao notar que o gist era escrito em CoffeeScript, o moderador comentou uma piadinha:
Prefiro usar moment a coffee.
A comunidade não gostou e reagiu, criticando o comentário infeliz e prezando o autor por compartilhar um código útil. Não satisfeito, as agressões sobre o uso de CoffeeScript continuaram.
Attention: the list was moved to https://github.com/vitorbritto/dev-list
This page is not maintained anymore, please update your bookmarks.
Recently, I decided to organize my bookmarks. So, like a good fellow, I am sharing with you. I hope you enjoy!
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
#!/usr/bin/env ruby -w | |
# pnginator.rb: pack a .js file into a PNG image with an HTML payload; | |
# when saved with an .html extension and opened in a browser, the HTML extracts and executes | |
# the javascript. | |
# Usage: ruby pnginator.rb input.js output.png.html | |
# By Gasman <http://matt.west.co.tt/> | |
# from an original idea by Daeken: http://daeken.com/superpacking-js-demos |
Backstory: I decided to crowdsource static site generator recommendations, so the following are actual real world suggested-to-me results. I then took those and sorted them by language/server and, just for a decent relative metric, their Github Watcher count. If you want a heap of other projects (including other languages like Haskell and Python) Nanoc has the mother of all site generator lists. If you recommend another one, by all means add a comment.