<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Google Closure.. will you register your code with the Borg?</title>
	<link>http://www.johnon.com/715/google-closure.html</link>
	<description>I think there's an opinion on that subject lying around here somewhere....</description>
	<pubDate>Fri, 24 May 2013 04:24:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Johannes</title>
		<link>http://www.johnon.com/715/google-closure.html#comment-130256</link>
		<pubDate>Tue, 30 Mar 2010 09:58:53 +0000</pubDate>
		<guid>http://www.johnon.com/715/google-closure.html#comment-130256</guid>
					<description>Well, this post is flawed in multiple ways. I'm not sure if you have any understanding of web development and javascript in particular.

&lt;em&gt;&lt;strong&gt;That's a declarative statement, authoritative sounding, but complete false. &lt;/strong&gt;Welcome to my blog. &lt;/em&gt;
First, you do not have to use the Google Closure Compiler web service. The compiler is also available as Java code which you can run locally; effectively, that means big G will never even see your source code.

&lt;strong&gt;&lt;em&gt;Step back to when this post was written; you can't rewrite history. &lt;/em&gt;&lt;/strong&gt;&lt;em&gt;And if you can now download and run it locally, so what? Just as Google claimed Chrome was "open source" because they offered a separate product "Google Chromium" with source that could be compiled yourself, didn't change the fact that Chrome was closed source. They don't disclose Chrome's code in the Chromium package... it's a separate package. That's slight of hand. I don't know if you are a Googler or just a fanboy, but your statements here appear disingenuous.&lt;/em&gt;
Second, assuming they could mark a site as "safe" (not even sure what you mean with this) just because the library they host on their servers has not been altered is simply hilarious. The point of a library is to provide some common tools that you can use in your own code. The library itself does not change anything on your site; it's only your own code that you write on top of the library tools that does something with your site.

&lt;strong&gt;I'm glad you find it "hilarious". I wish you made sense, though. &lt;/strong&gt;&lt;em&gt;You started by stating I misunderstood how js operates, yet this statement of yours is clearly confused. If I run a jquery plugin, which is open source so I can customize the code, it is no different than  "my  own code". If I only run jquery pulled from Google's CDN, it's not my own code. Google has already admitted it inspected the hosted code. What more do you need? Again, you appear to have an agenda. &lt;/em&gt;
Third, if Google really had the ability to parse, and understand javascript code automatically, there would be no way to prohibit them from simply downloading the code you host on your server. It does not matter whether you send them the code actively, or if you make the code available through your website. As soon as it is publicly reachable they can get it if they actually want to.

&lt;em&gt;&lt;strong&gt;Silly boy.&lt;/strong&gt; How much work would it be for Google to "download the code I host" on my server.. for every website on the Internet? Too much. So Google will try and manipulate the marketplace to help shift things towards Google, such as encouraging use of the CDN for js code. Sounds like you not only buy their story, but support and promote it.
&lt;/em&gt;

&lt;em&gt;You're welcome to come here and discuss or even argue my points, but if you start by calling me out and then add nothing but  nonsense (or propaganda-- I can't tell yet) you are not welcome. &lt;strong&gt;Come on, make yourself welcome. Try harder?&lt;/strong&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Well, this post is flawed in multiple ways. I&#8217;m not sure if you have any understanding of web development and javascript in particular.</p>
<p><em><strong>That&#8217;s a declarative statement, authoritative sounding, but complete false. </strong>Welcome to my blog. </em><br />
First, you do not have to use the Google Closure Compiler web service. The compiler is also available as Java code which you can run locally; effectively, that means big G will never even see your source code.</p>
<p><strong><em>Step back to when this post was written; you can&#8217;t rewrite history. </em></strong><em>And if you can now download and run it locally, so what? Just as Google claimed Chrome was &#8220;open source&#8221; because they offered a separate product &#8220;Google Chromium&#8221; with source that could be compiled yourself, didn&#8217;t change the fact that Chrome was closed source. They don&#8217;t disclose Chrome&#8217;s code in the Chromium package&#8230; it&#8217;s a separate package. That&#8217;s slight of hand. I don&#8217;t know if you are a Googler or just a fanboy, but your statements here appear disingenuous.</em><br />
Second, assuming they could mark a site as &#8220;safe&#8221; (not even sure what you mean with this) just because the library they host on their servers has not been altered is simply hilarious. The point of a library is to provide some common tools that you can use in your own code. The library itself does not change anything on your site; it&#8217;s only your own code that you write on top of the library tools that does something with your site.</p>
<p><strong>I&#8217;m glad you find it &#8220;hilarious&#8221;. I wish you made sense, though. </strong><em>You started by stating I misunderstood how js operates, yet this statement of yours is clearly confused. If I run a jquery plugin, which is open source so I can customize the code, it is no different than  &#8220;my  own code&#8221;. If I only run jquery pulled from Google&#8217;s CDN, it&#8217;s not my own code. Google has already admitted it inspected the hosted code. What more do you need? Again, you appear to have an agenda. </em><br />
Third, if Google really had the ability to parse, and understand javascript code automatically, there would be no way to prohibit them from simply downloading the code you host on your server. It does not matter whether you send them the code actively, or if you make the code available through your website. As soon as it is publicly reachable they can get it if they actually want to.</p>
<p><em><strong>Silly boy.</strong> How much work would it be for Google to &#8220;download the code I host&#8221; on my server.. for every website on the Internet? Too much. So Google will try and manipulate the marketplace to help shift things towards Google, such as encouraging use of the CDN for js code. Sounds like you not only buy their story, but support and promote it.<br />
</em></p>
<p><em>You&#8217;re welcome to come here and discuss or even argue my points, but if you start by calling me out and then add nothing but  nonsense (or propaganda&#8211; I can&#8217;t tell yet) you are not welcome. <strong>Come on, make yourself welcome. Try harder?</strong></em>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: john andrews</title>
		<link>http://www.johnon.com/715/google-closure.html#comment-129542</link>
		<pubDate>Mon, 16 Nov 2009 23:50:58 +0000</pubDate>
		<guid>http://www.johnon.com/715/google-closure.html#comment-129542</guid>
					<description>Yes, Google Points. Nice and simple. But, Google will probably want that to be binary, as in  1 you're in and 0, you're out.</description>
		<content:encoded><![CDATA[<p>Yes, Google Points. Nice and simple. But, Google will probably want that to be binary, as in  1 you&#8217;re in and 0, you&#8217;re out.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon Henshaw</title>
		<link>http://www.johnon.com/715/google-closure.html#comment-129535</link>
		<pubDate>Sun, 15 Nov 2009 16:22:24 +0000</pubDate>
		<guid>http://www.johnon.com/715/google-closure.html#comment-129535</guid>
					<description>I suppose then it should be called "Google (dis)Closure"

All I want to know is if I pull my js libraries from Google, will they count it as part of my page load time? And if I get 1 Google point for hosting my js on their servers, but my local files load faster than their overloaded js servers (refer to vague, non-descript, non-committal message from Matt about how 2010 being the year of the speedy site), will I lose 1 Google point, thus negating my original point?

(Oh, and while I just made up Google points, I encourage you to spread my lies.)</description>
		<content:encoded><![CDATA[<p>I suppose then it should be called &#8220;Google (dis)Closure&#8221;</p>
<p>All I want to know is if I pull my js libraries from Google, will they count it as part of my page load time? And if I get 1 Google point for hosting my js on their servers, but my local files load faster than their overloaded js servers (refer to vague, non-descript, non-committal message from Matt about how 2010 being the year of the speedy site), will I lose 1 Google point, thus negating my original point?</p>
<p>(Oh, and while I just made up Google points, I encourage you to spread my lies.)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Keith</title>
		<link>http://www.johnon.com/715/google-closure.html#comment-129496</link>
		<pubDate>Thu, 12 Nov 2009 03:28:48 +0000</pubDate>
		<guid>http://www.johnon.com/715/google-closure.html#comment-129496</guid>
					<description>I couldn't help but smile when I read the Google Closure page...sounded just a bit too smooth, a bit to warm and fuzzy...which always makes me think "What is the underlying agenda here?" So, I guess the theory is, "If we (G) can't keep up with js "innovations" then let's encourage the developers to work within the guidlelines of what we CAN read/see."

To be frank, it's all getting a little too weird. Had an interesting dinner table discussion with a few mates last weekend that kicked off with the notion "What if Google broke one day?" Needless to say, these kind of stealth encroachments "in the interests of quality" make many people nervous. Do we really want a completely Google world?

As always John, insightful and makes one slightly paranoid.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t help but smile when I read the Google Closure page&#8230;sounded just a bit too smooth, a bit to warm and fuzzy&#8230;which always makes me think &#8220;What is the underlying agenda here?&#8221; So, I guess the theory is, &#8220;If we (G) can&#8217;t keep up with js &#8220;innovations&#8221; then let&#8217;s encourage the developers to work within the guidlelines of what we CAN read/see.&#8221;</p>
<p>To be frank, it&#8217;s all getting a little too weird. Had an interesting dinner table discussion with a few mates last weekend that kicked off with the notion &#8220;What if Google broke one day?&#8221; Needless to say, these kind of stealth encroachments &#8220;in the interests of quality&#8221; make many people nervous. Do we really want a completely Google world?</p>
<p>As always John, insightful and makes one slightly paranoid.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bloggind Developer</title>
		<link>http://www.johnon.com/715/google-closure.html#comment-129482</link>
		<pubDate>Mon, 09 Nov 2009 17:43:00 +0000</pubDate>
		<guid>http://www.johnon.com/715/google-closure.html#comment-129482</guid>
					<description>You can find more details on using Google Closure API with ASP.NET at C# Wrapper for Google Closure Compiler - http://www.bloggingdeveloper.com/post/C-Wrapper-for-Google-Closure-Compiler-Compressing-Javascript-Files-on-the-fly-with-ASPNET-and-Closure-Compiler.aspx</description>
		<content:encoded><![CDATA[<p>You can find more details on using Google Closure API with ASP.NET at C# Wrapper for Google Closure Compiler - <a href="http://www.bloggingdeveloper.com/post/C-Wrapper-for-Google-Closure-Compiler-Compressing-Javascript-Files-on-the-fly-with-ASPNET-and-Closure-Compiler.aspx" >http://www.bloggingdeveloper.com/post/C-Wrapper-for-Google-Closure-Compiler-Compressing-Javascript-Files-on-the-fly-with-ASPNET-and-Closure-Compiler.aspx</a>
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
