In aws, Cloud Computing, Networking, Programming Paradigm on September 29, 2011 at 12:08 am
Amazon just launched its tablet, the Kindle Fire. Aside from the price (its only $199, less than half of an ipad 2) one of the most interesting feature is their browser called Amazon Silk. The browser basically off-loads the heavy lifting of rendering and image optimization to their huge proxy/rendering farm (courtesy of AWS). The result is snappier pages and happier users.
At least thats the idea. Theres no doubt that infrastructure-wise this will work as ISPs have done this at some point to save bandwidth and improve user experience (squid being the most popular open source cache/proxy).
Now for the privacy questions: how can amazon guarantee a) protection and b) anonymity of the session information and most importantly the data (eg username anf passwords) that will be “proxied” by the servers?
How will the browser deal with https traffic? Will that also be optimized too? (ie go through their servers)? I hope not!
That being said im looking forward to the getting my hands on them fondleslabs =)
In Microsoft, Programming Paradigm on September 20, 2011 at 9:40 am
Now, with the plethora of Tablets and smart phones numbering in the gazillions (and with Forrester research saying that by 2015 Tablets will overtake Laptops in sales) and with the vast majority with not a drop of MS technology exactly how relevant will MS be by that time? How will the corporate world develop their apps if their own internal users begin clamoring for Tablets that runs iOS or Android? Microsoft knows that the chances of it catching up with Apple and Android is slim and they have to live with the new reality: it has and will continue to lose relevance first and foremost in the user space (began by smartphones and tables) then increasingly and more critically in the corporate environment.
At the end of the day, Microsoft really has no choice but to go this route. It’s not Developers! Developers! anymore but Relevance! Relevance! Relevance!
In Database, Linux, MySQL on September 19, 2011 at 8:57 am
In early 2010, I noted that Oracle will only guarantee support to the open source version of MySQL until the end of January 2015 (or 5 years after the end of the transaction — that being the purchase of MySQL). A year and a half on and it looks like its well on schedule recently announcing that they’re now offering ‘commercial extensions‘ to the product.
The implication for this is obvious: we’re going to see more of these feature sets and ‘improvements’ on the commercial version of MySQL as opposed to the community version as to create enough doubt for corporate users who are a class of their own and who would invariably go for a more expensive solution ‘just to make sure’. The end result? why use open source mysql when you can buy? the purchase was, afterall, sweet revenge, as Oracle is able to effectively throttle competition from left field.
Purchasing MySQL is a medium term insurance policy, one which will have a maturity date of January 28, 2015.