So, yesterday I wrote about the new (and much expected) vulnerabilities in Googleâ€™s Gears technology. The issue is clear â€“ Gears is picking up speed and traction as Googleâ€™s applications start to use it (i.e. Gmail, Docs, etcâ€¦) and its security model is being scrutinized. And then I stumbled across GeeMail. Itâ€™s basically offline Gmail without using Googleâ€™s technology. How do you do that? Simple â€“ use Adobeâ€™s Airâ„¢, as if one technology was not enough to deal with, try mixing and matching two for some added confusion and security standard overlap.
Just like Gears, Air has its benefits, (admittedly, I’m using them both), but seriously, this is just too much! So whatâ€™s the next step? Gmail offline using Adobe Air with Silverlight UI running through Yahoo! Pipes backend? Back in the days we used to follow a simple methodology â€“ keep it simple (Iâ€™m omitting the latter part). Doing things just for the sake of using a specific technology is so 90â€™s â€œwar of the programming languagesâ€â€¦ everyone moved on to the simple model of using the right tool for the right job. In our case, even the review shows that the technology mix-up didnâ€™t really cut it.