Adding runtime checks for invalid usage is something we have policy against. It adds to the code size as well as to the runtime cost.

I totally agree. Developers should be responsible for their usage of APIs or third party libraries, while these should focus on working as efficient as possible given the correct parameters. Being Javascript a non-strongly-typed language, checking the parameters passed to every function are right at runtime would be a huge overkill.

Related Posts:

• March 15, 2010 -- More updates to Mooml coming soon (0)
• January 28, 2010 -- Dojo y yo (0)
• May 6, 2010 -- Tech talks at LEVEL Studios (0)
• January 28, 2010 -- Things to do (0)

• Using Closure Compiler to detect Javascript syntax errors and remove warnings.
• Using QUnit to test a REST api
• The power of WebSockets and how the way browsers and servers interact with each other will change in the future.

Related Posts:

• May 22, 2010 -- More WebSockets, now with Python! (9)
• March 15, 2010 -- More updates to Mooml coming soon (0)
• January 28, 2010 -- Things to do (0)
• March 14, 2011 -- Staying busy (0)

So, I got it working, using RegEx, but seems like it is way slower than eval. I have to do some performance testing and do some research to see if there is any way I can improve the performance. Hope to have version 1.1 ready soon.

Related Posts:

• April 28, 2010 -- Mooml 1.2.3 – Bye, bye, with() (3)
• March 24, 2010 -- Mooml 1.1 – No more eval(), say Hi to Mooml.Template and Mooml.Templates (0)
• February 19, 2010 -- Having fun with Mooml & Twitter (0)
• May 16, 2010 -- Performance matters (2)

Some cool stuff about Dojo

Reading Dojo’s documentation I have finally understood something that I was wondering how it works. It’s nothing really complicated, but it’s actually very cool: dojo.require

Javascript requests to the server are asynchronous (not sure if synchronous request can be done). So we depend on callback functions to continue the flow of your program. That means that when we put dojo.require('somefancyjs'); on a line, the execution does not stop and it continues to the next line of code while the browser downloads that file from the server in the background.

Looks like Dojo puts those requests on some kind of array, array that is checked when you use dojo.addOnLoad() which does not execute your callback function until all elements of the array have been downloaded. That is very cool because that means you can do as many dojo.require’s as you need. The down side is that you need to put your code inside a callback function, which is not very bad when working with objects.

Next, I have to find out how goog.require works ;)

Related Posts:

• May 16, 2010 -- Performance matters (2)
• January 28, 2010 -- Things to do (0)
• May 6, 2010 -- Tech talks at LEVEL Studios (0)
• March 15, 2010 -- More updates to Mooml coming soon (0)

• Try Appcelerator (downloaded.. don’t like it very much, have to spend more time with it)
• Install iPhone SDK 3.2 (downloading installing…)
• Study LinkedIn API
• Study Twitter API
• Take a look at YQL
• Play with Google Closure JS library
• Play with Dojo JS library

That’s it for now. Let’s see if I can find time to do all those.

Updated

Related Posts:

• May 6, 2010 -- Tech talks at LEVEL Studios (0)
• January 28, 2010 -- Dojo y yo (0)
• June 30, 2009 -- iPhone 3.0 geolocation with Javascript (1)
• June 14, 2011 -- Titanium Studio and Titanium Mobile 1.7 (0)