<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>

<title>Meshly -  popular  tagged with mochikit </title>
<link>http://www.meshly.com/popular/tag/mochikit/</link>
<description>Meshly Channel feed for all</description>
<pubDate>Fri, 05 Dec 2008 02:13:46 +0000</pubDate>
<generator>http://www.meshly.com/</generator>
<language>en</language>
	<item>
		<title>Bringing the browser to the server</title>
		<link>http://www.meshly.com/post/bringing_the_browser_to_the_server</link>
		<comments>http://www.meshly.com/post/bringing_the_browser_to_the_server#comments</comments>
		<pubDate>Wed, 11 Jul 2007 00:33:28 +0000</pubDate>
		<dc:creator>stella</dc:creator>
		<description><![CDATA[&quot;This weekend I took a big step in upping the ante for JavaScript as a Language. At some point last Friday evening I started coding and didn&#039;t stop until sometime mid-Monday. The result is a good-enough browser/DOM environment, written in JavaScript, that runs on top of Rhino; capable of running jQuery, Prototype, and MochiKit (at the very least).<br/>The implications of this are phenomenal, and I&#039;m not the only one who&#039;s interested in it what this could mean for server-side JS development.&quot;<br><br>]]></description>
	</item>

</channel>
</rss>

