X-Git-Url: http://git.bytex64.net/?a=blobdiff_plain;f=www%2Fwelcome.html;fp=www%2Fwelcome.html;h=e053273019a8db571c6bb5341408a872e6607405;hb=21db04ef3e4f66d7b5c4c9be2be36703b18cbcaa;hp=0000000000000000000000000000000000000000;hpb=08f2d9b356db309595da365b0b1dc7feda5cb469;p=blerg.git diff --git a/www/welcome.html b/www/welcome.html new file mode 100644 index 0000000..e053273 --- /dev/null +++ b/www/welcome.html @@ -0,0 +1,46 @@ + + +
I'M GLAD YOU ASKED. There are two aspects of Twitter that just bug +me as an engineer:
+ +Blërg solves these problems by applying absurd reactionary +engineering. Blërg's database backend is a custom C program that +handles requests over HTTP and stores data in a very small and +efficient indexed log-structured database. The frontend is done +entirely in client-side Javascript. A single post can be up to 65535 +bytes in length.
+ +Which is not to say that I believe writing your service in C is the +solution to all your problems. Clearly, this approach has just as +many hairy problems that will bite you in the ass sooner or later. +The best way, as with most things, lies somewhere in the middle of +high-level abstraction and ZOMGHARDCORE OPTIMIZATION.
+ +Yes. No. Maybe. Blërg is an exercise in constructive satire — a +fully functional service created in a fit of hubris to poke fun at Twitter's +engineering. It's just for fun, but no one is going to keep you from using +it seriously. :]
+ +Here, take a look at the design docs.
+ +I've created a bookmarklet just for you: Blërg it!