<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for britg</title><link>https://disqus.com/by/britg/</link><description></description><atom:link href="https://disqus.com/britg/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 04 Dec 2013 13:59:13 -0000</lastBuildDate><item><title>Re: About</title><link>http://britg.com/about/#comment-1150615761</link><description>&lt;p&gt;Hey Dave, yup I noticed that change was made. I have an update in the works that I can hopefully submit to Apple soon. In the meantime here's an open source repo with the change made if that helps: &lt;a href="https://github.com/britg/New-Relic-Menus" rel="nofollow noopener" target="_blank" title="https://github.com/britg/New-Relic-Menus"&gt;https://github.com/britg/Ne...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 04 Dec 2013 13:59:13 -0000</pubDate></item><item><title>Re: SPDY and Its Relation to WebSockets</title><link>http://britg.com/2012/03/15/spdy-and-its-relation-to-websockets/#comment-584147485</link><description>&lt;p&gt;Hah, I forgot when Bill had mentioned it -- ok, I promise it's changed now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 11 Jul 2012 09:20:59 -0000</pubDate></item><item><title>Re: Complex Gesture Recognition in iOS &amp;#8211; Part 2: The iOS Implementation</title><link>http://britg.com/2011/06/17/complex-gesture-recognition-in-ios-part-2-the-ios-implementation/#comment-324538592</link><description>&lt;p&gt;Thanks! I've got an app in the works but it's slow going. I hope to have it done soon, and I'll definitely make a post about it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 01 Oct 2011 13:37:14 -0000</pubDate></item><item><title>Re: New Relic Menu Bars: Multiple Application Support</title><link>http://britg.com/2011/07/04/new-relic-menu-bars-multiple-application-support/#comment-265422423</link><description>&lt;p&gt;Thanks! Good call. I'll definitely add this to the next version.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 26 Jul 2011 10:29:12 -0000</pubDate></item><item><title>Re: New Relic Menu Bar Performance Monitoring App</title><link>http://britg.com/2011/06/21/new-relic-menu-bar-performance-monitoring-app/#comment-239188380</link><description>&lt;p&gt;I don't know, as I'm only running 10.6 -- Let me know if you're running something else and it doesn't work.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 30 Jun 2011 21:20:15 -0000</pubDate></item><item><title>Re: New Relic Menu Bar Performance Monitoring App</title><link>http://britg.com/2011/06/21/new-relic-menu-bar-performance-monitoring-app/#comment-239188201</link><description>&lt;p&gt;Thanks! Ok, good to know. I'll work on multiple account management next!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 30 Jun 2011 21:19:43 -0000</pubDate></item><item><title>Re: New Relic Menu Bar Performance Monitoring App</title><link>http://britg.com/2011/06/21/new-relic-menu-bar-performance-monitoring-app/#comment-231906671</link><description>&lt;p&gt;Thanks! I'm planning to add a few more features and put it on the Mac App Store. If that doesn't work out, I'll share it on github for sure. In the mean time,  you can check out this older project that's open source: &lt;a href="https://github.com/crossforward/rpm-status" rel="nofollow noopener" target="_blank" title="https://github.com/crossforward/rpm-status"&gt;https://github.com/crossfor...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 22 Jun 2011 10:43:50 -0000</pubDate></item><item><title>Re: TotalFinder 1.0 - a sneak peek</title><link>http://blog.binaryage.com/totalfinder-sneak-peek/#comment-42739179</link><description>&lt;p&gt;Quite possibly the funniest thing I have ever seen. Bravo, bravo.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 01 Apr 2010 15:02:26 -0000</pubDate></item><item><title>Re: Quick Look: WebGL and Web Sockets</title><link>http://britg.com/?p=1303#comment-39426698</link><description>&lt;p&gt;Hey Pl4n3 -- awesome that you're working on an RTS in WebGL!  Your demo throws an error in Webkit nightlies, though -- "Error: 0:3: 'uniform' : cannot initialize this type of qualifier" (with wegGL enabled)&lt;/p&gt;&lt;p&gt;Which browser are you recommending for the demo?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Fri, 12 Mar 2010 15:38:19 -0000</pubDate></item><item><title>Re: TotalFinder with tabs!</title><link>http://blog.binaryage.com/totalfinder-with-tabs/#comment-29561258</link><description>&lt;p&gt;Awesome work!  Looking forward to try this out.  I appreciate your walking through your development process -- very interesting, indeed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 12 Jan 2010 20:41:47 -0000</pubDate></item><item><title>Re: On Stack Overflow Careers</title><link>http://britg.com/2009/12/10/on-stack-overflow-careers/#comment-25450888</link><description>&lt;p&gt;Thanks for clarifying.  I'll update the post to point to your clarification.&lt;/p&gt;&lt;p&gt;Glad you like the theme, but I can't really take  any credit for it, haha.  It's from &lt;a href="http://Woothemes.com" rel="nofollow noopener" target="_blank" title="Woothemes.com"&gt;Woothemes.com&lt;/a&gt; -- Bueno: &lt;a href="http://www.woothemes.com/2009/11/bueno/" rel="nofollow noopener" target="_blank" title="http://www.woothemes.com/2009/11/bueno/"&gt;http://www.woothemes.com/20...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 10 Dec 2009 11:46:04 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-12970950</link><description>&lt;p&gt;Hey John - from your console output, it looks like you are making requests to the wrong script.&lt;/p&gt;&lt;p&gt;"example.js:28 ..."&lt;/p&gt;&lt;p&gt;The name of the script, if you used the same copy from the github repo, should be 'gamelobby.js'&lt;/p&gt;&lt;p&gt;Let me know if that helps!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 20 Jul 2009 16:39:41 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-11986345</link><description>&lt;p&gt;Very cool, will watch its progress on github :)  I like the Sinatra-esque lightweight approach.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 01 Jul 2009 13:47:44 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-11978023</link><description>&lt;p&gt;True, I plan to make some updates, the first of which is to use POST on the /join URL and enforce it.  Also, I will implement a reaper process to clear stale joins.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 01 Jul 2009 10:34:49 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11499027</link><description>&lt;p&gt;And yes, I think Jack support is a great move for the project -- I think it'll find more adoption on Jack than Jaxer.  Nothing wrong with Jaxer, but I have a feeling that Jack will be widely adopted going forward just because of it's WSGI/Rack approach.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:30:22 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11498943</link><description>&lt;p&gt;Very cool project you put together!  I will definitely give it a try -- I'm finding that I can't live without FirePHP now.  I'm sure that will carry over to my server-side JS projects and this sounds like the perfect solution.  Cheers!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:25:23 -0000</pubDate></item><item><title>Re: The Brave New World of Server-Side Javascript</title><link>http://britg.com/2009/06/08/the-brave-new-world-of-server-side-javascript/#comment-11283665</link><description>&lt;p&gt;Interesting, thanks for pointing me to those two projects.  Perservere looks very interesting, and I immediately associated it with CouchDB because of the RESTful HTTP interface and JSON storage.  But two bullets that jumped out at me that I don't know that CouchDB can tout yet is (plus I'm sure there are many more differences):&lt;/p&gt;&lt;p&gt;# Comet-based data monitoring capabilities through HTTP Channels with Bayeux transport plugin/negotiation support&lt;/p&gt;&lt;p&gt;# Data-centric capability-based object level security with user management, Persevere is designed to be accessed securely through Ajax with public-facing sites&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 18 Jun 2009 22:51:54 -0000</pubDate></item><item><title>Re: Three Cheers for CakePHP Backwards Compatibility</title><link>http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/#comment-5583502</link><description>&lt;p&gt;Yeah, I agree about ActionScript camel casing.  Some languages just _feel_ like they should be camelcased and other _feel_ like they are underscored -- usually correlated to whether they are OO or not.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 27 Jan 2009 12:01:49 -0000</pubDate></item><item><title>Re: Results are in &amp;#8211; No One Likes Working With Time</title><link>http://britg.com/2009/01/15/results-are-in-no-one-likes-working-with-time/#comment-5140017</link><description>&lt;p&gt;No problem, Ryan.  Thanks for writing the plugin!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 15 Jan 2009 11:18:39 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress &amp;#8211; Part 1</title><link>http://britg.com/2008/08/23/integrating-cakephp-with-bbpress-part-1/#comment-5011635</link><description>&lt;p&gt;Well, my first approach when I get time to revisit would be to use the same&lt;br&gt;cookie mechanism i'm already using in my cake app - namely the cookie&lt;br&gt;handler.  I usually dont rely just on Sessions for my user login, but set a&lt;br&gt;cookie also.&lt;/p&gt;&lt;p&gt;I would extend the Cookie handler built into cake to tap into the same&lt;br&gt;libraries that BBPress is using (either by duplication or inclusion), and&lt;br&gt;when I set my cake cookie I also set a BBPress cookie, and a session&lt;br&gt;variable if BBPress requires one.&lt;/p&gt;&lt;p&gt;Hope that helps - and yes, I apologize that I have not finished part 3 - it&lt;br&gt;kills me as well!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Fri, 09 Jan 2009 09:19:21 -0000</pubDate></item><item><title>Re: It&amp;#8217;s hard to like the PHP &amp;#8216;Elite&amp;#8217; *UPDATE from Terry</title><link>http://britg.com/2009/01/08/its-hard-to-like-the-php-elite/#comment-4994848</link><description>&lt;p&gt;Ouch, that's unfortunate that it got posted before you could finish your train of thought.  I've redacted my "this guy doesn't get it" statement - the rest of your argument is a lot more thought out.  Are you going to pub it on your blog?  Won't get heard here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 08 Jan 2009 15:25:28 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress &amp;#8211; Part 1</title><link>http://britg.com/2008/08/23/integrating-cakephp-with-bbpress-part-1/#comment-4990265</link><description>&lt;p&gt;No, unfortunately I haven't taken the time to finish this out or the project&lt;br&gt;that this was for!  I really hope to revisit soon.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 08 Jan 2009 11:18:20 -0000</pubDate></item><item><title>Re: The Winter Beer of 2008 &amp;#8211; Michelob Winter&amp;#8217;s Bourbon Cask Ale</title><link>http://britg.com/2008/12/25/the-winter-beer-of-2008-michelob-winters-bourbon-cask-ale/#comment-4788267</link><description>&lt;p&gt;God yeah it's damn smooth and the hint of Vanilla is the kicker.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 30 Dec 2008 16:52:15 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress &amp;#8211; Part 2</title><link>http://britg.com/2008/08/25/integrating-cakephp-with-bbpress-part-2/#comment-3273453</link><description>&lt;p&gt;Thanks, yes I really intend to write part 3 - but unfortunately the project&lt;br&gt;I was doing this for has been put on hold for the moment!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Fri, 24 Oct 2008 09:10:11 -0000</pubDate></item><item><title>Re: Who Google Chrome Affects the Most: Adobe</title><link>http://britg.com/2008/09/02/who-google-chrome-affects-the-most/#comment-2996971</link><description>&lt;p&gt;Haha, yes good points all around.  I do agree that this is a good thing for&lt;br&gt;web developers in general because it does force Adobe to keep up with speed&lt;br&gt;and accessibility of ajax in flash.&lt;/p&gt;&lt;p&gt;In response to your Microsoft point - they don't necessarily have to adopt&lt;br&gt;Google's technology for V8 to have an affect on Adobe.  Since MS and Google&lt;br&gt;are so competitive, I can see a scenario where Microsoft comes out with&lt;br&gt;their own new-fangled js engine that touts more and better features than V8&lt;br&gt;etc, etc.  This will lead to the web tech conversation switching tone from&lt;br&gt;"ajax vs flash" to "google's js tech vs MS's js tech".  This is bad for&lt;br&gt;Adobe.&lt;/p&gt;&lt;p&gt;I do agree with you that flash isn't going anywhere even in this scenario.&lt;br&gt;It's all up to Adobe and where they take the platform.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 11 Oct 2008 07:57:06 -0000</pubDate></item></channel></rss>