Comments on: Rojo – how not to publish updates to your site http://damieng.com/blog/2006/09/19/rojo-how-not-to-publish-updates-to-your-site?utm_source=rss&utm_medium=rss&utm_campaign=rojo-how-not-to-publish-updates-to-your-site A .NET developer in silicon valley Fri, 18 May 2012 15:31:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Disappointing start to BlogRush http://damieng.com/blog/2006/09/19/rojo-how-not-to-publish-updates-to-your-site#comment-4623 Disappointing start to BlogRush Tue, 16 Oct 2007 17:55:56 +0000 http://damieng.com/blog/archive/2006/09/19/rojo-how-not-to-publish-updates-to-your-site.aspx#comment-4623 [...] on both fronts. It goes to prove that a great idea needs a great implementation which reminds me of Rojo's failed rollouts which led me to switch to the then-inferior Google Reader which is now much more [...] [...] on both fronts. It goes to prove that a great idea needs a great implementation which reminds me of Rojo’s failed rollouts which led me to switch to the then-inferior Google Reader which is now much more [...]

]]> By: Big Monkey http://damieng.com/blog/2006/09/19/rojo-how-not-to-publish-updates-to-your-site#comment-1629 Big Monkey Wed, 20 Sep 2006 01:53:19 +0000 http://damieng.com/blog/archive/2006/09/19/rojo-how-not-to-publish-updates-to-your-site.aspx#comment-1629 Plus the new pages takes longer to load (except when they are simply blank), is funky and generally looks ugly.<br /><br />There was no apparent upgrade of functionality. Plus the new pages takes longer to load (except when they are simply blank), is funky and generally looks ugly.

There was no apparent upgrade of functionality.

]]>