smeranda

/*
Make the Facebook Like box responsive (fluid width)
https://developers.facebook.com/docs/reference/plugins/like-box/
*/

/* This element holds injected scripts inside iframes that in some cases may stretch layouts. So, we're just hiding it. */
#fb-root {
  display: none;
}

nicerobot

To run this, you can try:

curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh

jonkemp

History of Frontend Tooling

http://ln.hixie.ch/?start=1037910467&count=1

http://ln.hixie.ch/?start=1137740632&count=1

http://software.hixie.ch/utilities/js/live-dom-viewer/

http://joehewitt.com/2006/03/26/firebug-03-preview

sindresorhus

How to write your Markdown in Sublime Text 2 and preview in Mou

I use Sublime for everything text related, but it doesn't have any built-in way to preview my Markdown files.

This is how easy it is to preview in Mou:

• In Sublime, go to Tools -> Build System -> New Build System...
• In the newly opened file, replace the file contents with this and save: { "osx": {

rmurphey

What's wrong with Netmag's "Optimize your JavaScript" post

Update: The original post on Netmag has been updated since this was written.

I tweeted earlier that this should be retracted. Generally, these performance-related articles are essentially little more than linkbait -- there are perhaps an infinite number of things you should do to improve a page's performance before worrying about the purported perf hit of multiplication vs. division -- but this post went further than most in this genre: it offered patently inaccurate and misleading advice.

Here are a few examples, assembled by some people who actually know what they're talking about (largely Rick Waldron and Ben Alman, with some help from myself and several others from the place that shall be unnamed).

Things that are just plain wrong

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

rosylilly

先輩に学ぶ HTTP Status Code

超雑にまとめました。修正してください。

登場人物

• アプリケーション先輩: いつも忙しい。横に広がるのが得意(デブじゃない)。
• 後輩: 頼んでばっかしで役に立たない。
• サーバー先輩: アプリケーション先輩と仲がいい。Unix Socket でつながるくらい仲良し。
• プロクシ先輩: アプリケーション先輩とかサーバー先輩と後輩の間を取り持って代わりに伝えたりしてくれる。たまに勝手にレスポンスを書き換える。

addyosmani

CommandLineAPIImpl.prototype = {
    $: function (selector, start) {
        var result;
        if (start && start.querySelector && (start.nodeType === 1 || start.nodeType === 9 || start.nodeType === 11)) {
            result = start.querySelector(selector);
        } else {
            result = document.querySelector(selector);
            if (result == null && (selector || "")[0] !== "#") {
                result = document.getElementById(selector);
                if (result !== null) {

BlackKetchupTea512

追記

この記事は古いです...。はてなブログの方に完全版を置いてあります。→ http://blue-ham-cake1024.hatenablog.com/entry/2012/09/07/Sublime_Text_2_のDefault設定ファイルを眺める

---

はてなブログは調子が悪いようなので。

この記事ではDefault設定ファイルにどのような記述がされているか、その記述にどんな意味があるかを一つ一つ見ていきます。実際に設定をカスタマイズしてみたい方は、メニューのPreferencesタブの"Settings - User"からUser設定ファイルを開いてそこでいろいろ試してみましょう。

Gab-km

GitHub Flow

• Scott Chacon on the Interwebs(リンク切れ)
• Scott Chacon on the Interwebs
• GitHub Flow - The best way to use Git and GitHub

31 Aug 2011

git-flowの問題点 (Issues with git-flow)