veloc

RT @botchagalupe: This blows my mind... A man gives a pres about building a 2 yr $billion exit and all the ?'s are about sharding #veloc ...

— Brendan Quinn (@brendanquinn)2012-10-03 09:48:58

RT @botchagalupe: This blows my mind... A man gives a pres about building a 2 yr $billion exit and all the ?'s are about sharding #veloc ...

— Fred Beringer (@fredberinger)2012-10-03 09:45:37

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Ilya Grigorik (@igrigorik)2012-10-03 09:43:13

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Alice Bartlett (@alicebartlett)2012-10-03 09:27:04

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Andrew Betts (@triblondon)2012-10-03 09:24:24

RT @ginablaber: MT @mpaluchowski: Eye tracking: Chinese users scan all 10 Google's search result. Americans never go below no. 3. #veloc ...

— Henrik Ingo (@h_ingo)2012-10-03 09:22:59

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Fred Beringer (@fredberinger)2012-10-03 09:08:29

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Jarred Nicholls (@jarrednicholls)2012-10-03 09:08:10

RT @souders: Holy ASCII packing Batman! FT avoids UTF-16 inefficiencies by packing two UTF-8 chars per UTF-16 with JS @triblondon #Veloc ...

— Chris James (@quii)2012-10-03 09:03:11

RT @vdandre: Thanks for sharing the mistakes that were made by @b3cft Awesome that you're unfearful with sharing your experience! #veloc ...

— James Sheridan (@jamessheridan)2012-10-03 08:52:48