<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: How Big is Your Javascript Library?</title>
	<atom:link href="http://brennan.offwhite.net/blog/2007/02/25/how-big-is-your-javascript-library/feed/" rel="self" type="application/rss+xml" />
	<link>http://brennan.offwhite.net/blog/2007/02/25/how-big-is-your-javascript-library/</link>
	<description>My Experiences with Software Development</description>
	<pubDate>Mon, 08 Sep 2008 07:15:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Brian Deacon</title>
		<link>http://brennan.offwhite.net/blog/2007/02/25/how-big-is-your-javascript-library/#comment-16910</link>
		<dc:creator>Brian Deacon</dc:creator>
		<pubDate>Tue, 06 Mar 2007 16:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://brennan.offwhite.net/blog/2007/02/25/how-big-is-your-javascript-library/#comment-16910</guid>
		<description>Hey Brennan,

All good points, a nice post.  I'm sort of a newbie in this space, but I know that toolkits like DOJO and GWT also add an additional approach in only including in the download the portions of the library that you are actually using, which gives a big size benefit.  GWT has a big focus on this, but that is pretty much a java solution, although technically you could include GWT in an ASP.Net application.  But the team working on such a project would probably feel squiggly moving back and forth between a java-based GWT client-side code model and a .Net server-side model.

The Java Posse had a good interview in episode 88 (http://javaposse.com/index.php?post_id=140955) where they talked about a lot of these issues.

Brian</description>
		<content:encoded><![CDATA[<p>Hey Brennan,</p>
<p>All good points, a nice post.  I'm sort of a newbie in this space, but I know that toolkits like DOJO and GWT also add an additional approach in only including in the download the portions of the library that you are actually using, which gives a big size benefit.  GWT has a big focus on this, but that is pretty much a java solution, although technically you could include GWT in an ASP.Net application.  But the team working on such a project would probably feel squiggly moving back and forth between a java-based GWT client-side code model and a .Net server-side model.</p>
<p>The Java Posse had a good interview in episode 88 (http://javaposse.com/index.php?post_id=140955) where they talked about a lot of these issues.</p>
<p>Brian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
