Evernote's business model and cost structure. Evernote is notable
for their pioneering of the freemium model \<http://www.fastcompany.com/magazine/147/next-tech-remember-the-money.html\>__,
based on the idea from their CEO: *The easiest way to get 1 million
people paying is to get 1 billion people using. *Evernote is designed
to become profitable at a 1% conversion rate.*
The SPDY project defines and implements an application-layer protocol
for the web which greatly reduces latency. The high-level goals for SPDY
are:
| * To target a 50% reduction in page load time. Our preliminary
results have come close to this target (see below).
| * To minimize deployment complexity. SPDY uses TCP as the underlying
transport layer, so requires no changes to existing networking
infrastructure.
| * To avoid the need for any changes to content by website authors.
The only changes required to support SPDY are in the client user agent
and web server applications.
| * To bring together like-minded parties interested in exploring
protocols as a way of solving the latency problem. We hope to develop
this new protocol in partnership with the open-source community and
industry specialists.
| Tomato Firmware | polarcloud.com
| Tomato is a small, lean and simple replacement firmware for Linksys
WRT54G/GL/GS, Buffalo WHR-G54S/WHR-HP-G54 and other Broadcom-based
routers. It features a new easy to use GUI, a new bandwidth usage
monitor, more advanced QOS and access restrictions, enables new
wireless features such as WDS and wireless client modes, raises the
limits on maximum connections for P2P, allows you to run your custom
scripts or telnet/ssh in and do all sorts of things like re-program
the SES/AOSS button, adds wireless site survey to see your wifi
neighbors, and more.
| Chris Hanson - launchd: Better than sliced
bread
| Simply put, launchd is what makes it easy to get tasks launched
on-demand on Mac OS X 10.4 and later. It obviates lots of different
archaic Unix infrastructure — init.d, cron, inetd — in favor of a
single self-consistent and easy to use mechanism. Dave Zarzycki’s post
Where to begin? describes the
launchd design philosophy in some depth.
Processes launched at startup on Mac OS X are managed by launchd.
There’s no careful balancing of init.d or SystemStarter scripts on
modern releases of the operating system. Instead, launchd jobs have
property list entries in the LaunchAgents and LaunchDaemons directories
in the system and local domains. Some specify that launchd should keep
them alive indefinitely, others simply provide conditions under which
they should be launched.