Skip to content

Instantly share code, notes, and snippets.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Google ought to make a phone called the Google Jaw, or gJaw, which we could use to access the Reticulum.
When choosing a technology, "because it's what you know" is always a good reason, but it's not always a good _enough_ reason.
@qpliu
qpliu / gist:9280429
Created February 28, 2014 21:36
On the size of futuristic 3D image files

On the size of futuristic 3D image files

Futuristic 3D displays

The type of futuristic 3D display I'm considering would be pixel-based flat surface, like today's displays. The futuristic part is that each pixel controls what color gets emitted in a number of directions.

If such a display were used to display a 3D image, then it should be like looking through a window, where different viewing angles give the

-- A friend interviewed at Google and was given the task of
-- making a linked list from a binary tree where an element's
-- next element is its sibling, or null where there is none.
-- Example:
-- A
-- / \
-- / \
-- B C
-- / / \