This article discusses Mozilla’s and Google’s reaction to the news that their browsers will not be allowed access to Windows RT (Windows on ARM). Mozilla has branded Microsoft’s restrictions a return to the digital dark ages “where users and developers didn’t have browser choices.”
This article is the continuation of February’s part one, to which a link is provided.
Node.js uses event-driven, asynchronous i/o instead of the traditional multi-threaded concurrency model. This article shows how to monitor objects in node.js.
This article explains why waterfall-chart measurements alone may not give a true picture of performance as seen by the end-user. Example: If everything is deferred until pageload is triggered, the page will become visible, but with very little usable content.
It’s a good article, but it fails to mention the free services available at Monitor.Us. Big oversight!