hyperbolist

10 ms·

1.
by hyperbolist 17y ago
Bitrate is the primary determinant for bandwidth consumption, no?
2.
by hyperbolist 17y ago
Thanks for this, I'm enjoying it! You probably want to add something like set :url, "http://example.com" # site root URL to your config.ru documentation.
3.
by hyperbolist 17y ago
Conventions are just conventions anyway. We've established that there's no technical barrier to your two objections. 1) You can clone different branches into different paths, which is exactly like a traditional svn workflow, and a pretty
4.
by hyperbolist 17y ago
http://daringfireball.net/2010/02/winer_flash_open_standards quote: But what if the source code to Flash Player is — as many would wager — a huge steaming pile of convoluted C++ horseshit? It’s sort of like what if Microsoft open-sourced
5.
by hyperbolist 17y ago
I'm not making that claim, and freely admit that I am utterly ignorant about mercurial. I'm merely demonstrating that, contrary to the author's assertion, it's possible to use git without deleting branches and still have a meaningful way t
6.
by hyperbolist 17y ago
how do I see two different branches' versions of files? You could clone the branches to different paths, I guess. But nobody else will [know that a branch is "done".] If you've instructed the team to care about merged status, they will.
7.
by hyperbolist 17y ago
Many sites deliver video by H.264 in the absence of Flash. It is seamless to the user, and there are no blue legos. The fact that Flash is missing from iPhones and iPod Touches, and that people with those devices are using the web, produc
8.
by hyperbolist 17y ago
http://jilion.com/sublime/video -- a Video player for these approaching Dark Ages
9.
by hyperbolist 17y ago
How do I get both files side-by-side in Emacs so I can go through them thoroughly (some of us prefer that to reading diffs, you know)? git show branch:path/to/file > /tmp/file I want the history of my codebase to be easy to ge
10.
by hyperbolist 17y ago
Further: To say "I'm done with this branch", merge it to master. This is natural; you already do this. git branch --merged master # list branches that are "done" git branch --no-merged master # list branches that are "not done" No
11.
by hyperbolist 17y ago
I read the article, I enjoyed it. It reminded me of why I like git so much. git-diff doesn't require you to do gymnastics to compare files from different branches in the same working directory: "git diff branch1 [branch2] path" where omitt
12.
by hyperbolist 17y ago
Coming from svn, I too felt initial discomfort about git's promiscuous branching, but then I learned to stop worrying and love the index. Working in svn repositories evokes "I wish this was a git repository" every time. I wouldn't have ini
13.
Text Layout with Core Text(slideshare.net)
2 points by hyperbolist 17y ago|0 comments