Comments on: Performance matters http://dev.enekoalonso.com/2010/05/16/performance-matters/ having fun with code Thu, 15 Sep 2011 22:21:33 +0000 hourly 1 By: Eneko Alonso http://dev.enekoalonso.com/2010/05/16/performance-matters/comment-page-1/#comment-26522 Eneko Alonso Tue, 18 May 2010 13:47:38 +0000 http://dev.enekoalonso.com/?p=543#comment-26522 Yeah, that is the best solution. Currently in the project I am working on the JS is processed by our CMS, so it can generate different outputs, one of them being a flag to display/hide debug messages. The MooTools just released something very interesting for MooTools 1.3: <a href="http://github.com/cpojer/mootools-interface/blob/master/Demos/Example.js"Interface</a rel="nofollow">. While in use, it throws exceptions if someone in the dev team does not use a class as defined by the Interface. What is very interesting is that <a href="http://twitter.com/cpojer/status/14177043960" rel="nofollow">it can be removed prior to deploying to production</a>, so it would not have a performance impact. Yeah, that is the best solution. Currently in the project I am working on the JS is processed by our CMS, so it can generate different outputs, one of them being a flag to display/hide debug messages.

The MooTools just released something very interesting for MooTools 1.3: . While in use, it throws exceptions if someone in the dev team does not use a class as defined by the Interface. What is very interesting is that it can be removed prior to deploying to production, so it would not have a performance impact.

]]> By: Pau Sanchez http://dev.enekoalonso.com/2010/05/16/performance-matters/comment-page-1/#comment-26518 Pau Sanchez Tue, 18 May 2010 07:00:48 +0000 http://dev.enekoalonso.com/?p=543#comment-26518 Still, a good idea would be to provide a debug version which logs errors (e.g: firebug), so developers can use it during development, to know they are not doing anything wrong. Of course, I agree is not a good idea to use it in production/live site. Still, a good idea would be to provide a debug version which logs errors (e.g: firebug), so developers can use it during development, to know they are not doing anything wrong.

Of course, I agree is not a good idea to use it in production/live site.

]]>