FlatBuffers stores serialized data in buffers in a cross-platform way, supporting format evolution that is fully forwards and backwards compatible through a schema. These buffers can be stored in files or sent across the network as-is, and accessed in-place without parsing overhead.

In pipelined processors, instruction are fetched, decoded, and executed speculatively, and are not permitted to modify system state until instruction commit. For instructions that modify registers, this is often achieved using register renaming. For stores to memory, speculative stores write into a store queue at execution time and only write into cache after the store instructions have committed.

Python's SimpleHTTPServer is a great way of serve the contents of the current directory from the command line:

python -m SimpleHTTPServer

However, as far as web servers go, it's very slooooow...

-> npm install http-server -g

Recover from a rm -rf at root

Another story: http://lug.wsu.edu/node/414

• e9c00be...2652a00 garment-quiz -> garment-quiz (forced update)
  • d91922d...2fec250 release-2012-07-04 -> release-2012-07-04 (forced update)

fix:
git push origin d91922d:release-2012-07-04

Some beautiful template for static html5 site

The behavior of dispatch_once is in the name. It does something once and only once.

It takes two parameters. The first is a predicate that tracks the "once". The second is a block to execute on the first call.

chmod a+rwX -R

Over the last ten years, LLVM has substantially altered this landscape. LLVM is now used as a common infrastructure to implement a broad variety of statically and runtime compiled languages (e.g., the family of languages supported by GCC, Java, .NET, Python, Ruby, Scheme, Haskell, D, as well as countless lesser known languages). It has also replaced a broad variety of special purpose compilers, such as the runtime specialization engine in Apple's OpenGL stack and the image processing library in Adobe's After Effects product. Finally LLVM has also been used to create a broad variety of new products, perhaps the best known of which is the OpenCL GPU programming language and runtime.

Throughout our life, we all continue to generate content, whether that's writing documents, taking photos, writing comments online, liking our friends' posts on social networks, etc. Our content is typically spread between a mix of different companies' servers ("The Cloud") and your own hardware (laptops, phones, etc). All of these things are prone to failure: companies go out of business, change ownership, or kill products. Personal harddrives fail, laptops and phones are dropped.

It would be nice if we were a bit more in control. At least, it would be nice if we had a reliable backup of all our content. Once we have all our content, it's then nice to search it, view it, and directly serve it or share it out to others (public or with select ACLs), regardless of the original host's policies.

Camlistore is a system to do all that.

A set of small, responsive CSS modules that you can use in every web project.

This document looks at the numerous and interesting ways the Linux kernel 2.6 interacts with user space programs. We explain sockets, procfs (and similar virtual filesystems), creating new Linux system calls, as well as mundane file and memory handling.

More on userspace interfaces: http://www.ibm.com/developerworks/library/l-kernel-memory-access/