Passing Second-Class Arguments

Before it's current incarnation, I was frustrated by my own, soon-to-be-renamed, Proxy object. [Mind you, I don't mean the upcoming E5 Proxy object.] As a function manager, Proxy offers the benefit of passing secondary execution information, to it's managed routines. (These "extra" arguments permit comprehensive forking.) As with many function managers, this well-intentioned practice wound up restricting the number of arguments allowed in managed routines, resulting in a polluted signature.

Proxy and the ES5 (Harmony) Proxy

I didn't know it then, but Proxy is a native object in ECMA-Script 5 (ES5), the next web programming language. What this means is that I must change the name of my Proxy object to something else - yet to be determined. Moreover, I'm sure there will be inquiries (from all two of you) about the differences and similarities between my Proxy object and "theirs".

Learning to Open-Source via Proxy

The Internet is a relentless, fast-paced, consumer of content, and I'm a bit of a recluse. My engagements had been brief and trifling; irc chatting, a blog comment here, a forum post there. Then, as a test use of github.com - a popular code-sharing service - I published Proxy. It was my debut in the open-source JavaScript world¹, and I was determined to see it through to the end. However, in the reverse time-warp that is the Internet, I've learned that the end never comes...

Proxy - You've come a long way, baby.

I began this post three weeks ago and should have published it then. For it has been an exciting three weeks, for me. I'm proud to announce Proxy, my first opensource JavaScript project, is available on github.com. Alas, this post is only about the journey to that destination...