<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for britg</title><link>http://disqus.com/people/britg/</link><description></description><language>en</language><lastBuildDate>Sun, 06 Sep 2009 12:13:01 -0000</lastBuildDate><item><title>Re: Netflix&amp;#8217;s DRM Turned Me Into a Pirate</title><link>http://britg.disqus.com/netflix8217s_drm_turned_me_into_a_pirate/#comment-16063076</link><description>I also agree the same.&lt;br&gt;&lt;a href="http://www.premierhealthcareonline.com/" rel="follow" rel="nofollow"&gt;affordable health care &lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">affordablehealthcare</dc:creator><pubDate>Sun, 06 Sep 2009 12:13:01 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.disqus.com/server_side_javascript_continued_8211_nodejs_plus_example/#comment-12978321</link><description>Sweet! That works :)&lt;br&gt;&lt;br&gt;Thanks britg, very fun stuff! I'm planning to build a small comet server using node.js&lt;br&gt;&lt;br&gt;Best,&lt;br&gt;John</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">john</dc:creator><pubDate>Mon, 20 Jul 2009 18:58:58 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.disqus.com/server_side_javascript_continued_8211_nodejs_plus_example/#comment-12970950</link><description>Hey John - from your console output, it looks like you are making requests to the wrong script.&lt;br&gt;&lt;br&gt;"example.js:28 ..."&lt;br&gt;&lt;br&gt;The name of the script, if you used the same copy from the github repo, should be 'gamelobby.js'&lt;br&gt;&lt;br&gt;Let me know if that helps!</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: The Brave New World of Server-Side Javascript</title><link>http://britg.disqus.com/the_brave_new_world_of_server_side_javascript/#comment-12141300</link><description>You may also want to look at the open source M/DB:X which is an HTTP-interfaced hybrid JSON/Native XML Database.  JSON objects are converted to and stored as XML DOMs which can be analysed, modified, transformed and searched in the XML domain and returned as JSON strings. See &lt;a href="http://www.mgateway.com/mdbx.html" rel="nofollow"&gt;http://www.mgateway.com/mdbx.html&lt;/a&gt; for more information</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob</dc:creator><pubDate>Sat, 04 Jul 2009 07:54:42 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.disqus.com/server_side_javascript_continued_8211_nodejs_plus_example/#comment-11986345</link><description>Very cool, will watch its progress on github :)  I like the Sinatra-esque lightweight approach.</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.disqus.com/server_side_javascript_continued_8211_nodejs_plus_example/#comment-11978023</link><description>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.</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.disqus.com/nginx_proxies_with_firephp/#comment-11499027</link><description>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.</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.disqus.com/nginx_proxies_with_firephp/#comment-11498943</link><description>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!</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.disqus.com/the_brave_new_world_of_server_side_javascript/#comment-11283665</link><description>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;br&gt;&lt;br&gt;# Comet-based data monitoring capabilities through HTTP Channels with Bayeux transport plugin/negotiation support&lt;br&gt;&lt;br&gt;# Data-centric capability-based object level security with user management, Persevere is designed to be accessed securely through Ajax with public-facing sites</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.disqus.com/three_cheers_for_cakephp_backwards_compatibility/#comment-5583502</link><description>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.</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 - No One Likes Working With Time</title><link>http://britg.disqus.com/results_are_in_no_one_likes_working_with_time/#comment-5140017</link><description>No problem, Ryan.  Thanks for writing the plugin!</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 - Part 1</title><link>http://britg.disqus.com/integrating_cakephp_with_bbpress_part_1_10/#comment-5011635</link><description>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;br&gt;&lt;br&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;br&gt;&lt;br&gt;Hope that helps - and yes, I apologize that I have not finished part 3 - it&lt;br&gt;kills me as well!</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;</title><link>http://britg.disqus.com/it8217s_hard_to_like_the_php_8216elite8217/#comment-4996030</link><description>No I totally agree that it would seem that I didn't get it from the draft you read. Over half the things written were snippets to random comments I never posted.&lt;br&gt;&lt;br&gt;Yes, I'll finish the article and publish after I chill out and get some perspective. If you write something mean and mean it, it's hurtful. If you write something mean and don't mean it, it's playful. :-D</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">terry chay</dc:creator><pubDate>Thu, 08 Jan 2009 16:28:27 -0000</pubDate></item><item><title>Re: It&amp;#8217;s hard to like the PHP &amp;#8216;Elite&amp;#8217;</title><link>http://britg.disqus.com/it8217s_hard_to_like_the_php_8216elite8217/#comment-4994848</link><description>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.</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 - Part 1</title><link>http://britg.disqus.com/integrating_cakephp_with_bbpress_part_1_10/#comment-4990265</link><description>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.</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 - Michelob Winter&amp;#8217;s Bourbon Cask Ale</title><link>http://britg.disqus.com/the_winter_beer_of_2008_michelob_winter8217s_bourbon_cask_ale/#comment-4788267</link><description>God yeah it's damn smooth and the hint of Vanilla is the kicker.</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 - Part 2</title><link>http://britg.disqus.com/integrating_cakephp_with_bbpress_part_2_95/#comment-3273453</link><description>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!</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</title><link>http://britg.disqus.com/who_google_chrome_affects_the_most/#comment-3036363</link><description>Now *that* would be a truly amazing happening... microsoft innovating in the JS engine world!  ;-)  Joking aside, it seems MS's style is more to just add on to the JS core with proprietary API than to really re-do the internals... and when they do muck with the internals, we get some crappy results!  However, it is clear that IE8 is coming with a big re-write of the JS engine under the hood, which is long overdue.&lt;br&gt;&lt;br&gt;But honestly, I doubt MS will try to get into that game.  They may surprise us, but I'd imagine they are quite a ways behind.  I suspect they will try to prevent the game from being a "my JS versus your JS" kind of a game, because that's one they'll probably lose, going up against the open-source community.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kyle Simpson</dc:creator><pubDate>Tue, 14 Oct 2008 00:33:52 -0000</pubDate></item><item><title>Re: Who Google Chrome Affects the Most</title><link>http://britg.disqus.com/who_google_chrome_affects_the_most/#comment-2996971</link><description>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;br&gt;&lt;br&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;br&gt;&lt;br&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.</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><item><title>Re: Who Google Chrome Affects the Most</title><link>http://britg.disqus.com/who_google_chrome_affects_the_most/#comment-2994455</link><description>I'll definitely grant you that the V8 engine is impressive in some respects.  But also after having tested a number of my projects (javascript, flash, etc) in it, and finding more than a couple of bugs, I still think it's got a ways to go.  &lt;br&gt;&lt;br&gt;But then again, even if we granted that Chrome, and Firefox, and Safari/Webkit *all* adopted this V8 engine... microsoft surely won't ever touch it.  And again, for the forseeable future, content authors are not going to be able to make decisions that largely ignore (or marginalize) such a big share of the end-user community.&lt;br&gt;&lt;br&gt;Will there be plenty of niche applications which target the speed and efficiency that V8 (and others) can achieve?  Yeah.  And will those same engines certainly speed up a lot of the other apps that are deliberately cross-browser for the mainstream?  Yeah.&lt;br&gt;&lt;br&gt;But that's still a far cry from saying that just because some (or even a good share) of the browsers out there *can* run javascript faster that content authors will be able to ignore microsoft's share and develop apps which run great, but only on 50% of user's machines, and on the other 50% run crappy.  No, the truth is, for a long while, they'll still have to leverage technology which is consistent (albeit less performant, and certainly less "open") for the broad audience.&lt;br&gt;&lt;br&gt;I don't think V8 will reduce flash's share.  What I think it *will* do is force them to keep up with improvements in performance and broad browser delivery  -- something they've been at for quite awhile.&lt;br&gt;&lt;br&gt;And what's great is that this will be good for the overall web community. Just don't be so quick to uninstall that flash plugin yet!  :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kyle Simpson</dc:creator><pubDate>Fri, 10 Oct 2008 23:24:23 -0000</pubDate></item><item><title>Re: Why Aptana is Quickly Becoming the Killer Stack</title><link>http://britg.disqus.com/why_aptana_is_quickly_becoming_the_killer_stack/#comment-2942295</link><description>Thank you very much! &lt;br&gt;It works in Aptana Studio, build: 1.2.0.017963, and I'm not using the pro version. &lt;br&gt;Best Regards&lt;br&gt;Andrija</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrija</dc:creator><pubDate>Wed, 08 Oct 2008 12:42:36 -0000</pubDate></item><item><title>Re: Why Aptana is Quickly Becoming the Killer Stack</title><link>http://britg.disqus.com/why_aptana_is_quickly_becoming_the_killer_stack/#comment-2935026</link><description>Check out the response to the word wrap issue report here:&lt;br&gt;&lt;a href="http://support.aptana.com/asap/browse/STU-534?focusedCommentId=18301#action_18301" rel="nofollow"&gt;http://support.aptana.com/asap/browse/STU-534?f...&lt;/a&gt;&lt;br&gt;&lt;br&gt;He explains how to turn on wordwrap.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 08 Oct 2008 08:55:11 -0000</pubDate></item><item><title>Re: Big in Japan wins the Android Challenge, raises money and has big plans for Google Android development</title><link>http://venturebeat.disqus.com/big_in_japan_wins_the_android_challenge_raises_money_and_has_big_plans_for_google_android_developmen/#comment-2409041</link><description>Big props to the Dallas startup scene!  Congrats Biggu and Rylan and Alex</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 17 Sep 2008 18:48:22 -0000</pubDate></item><item><title>Re: How Apple Picks Which Apps Make It to the App Store | ShaunGish.com</title><link>http://shaungish.disqus.com/how_apple_picks_which_apps_make_it_to_the_app_store_shaungishcom/#comment-2408720</link><description>that could be just about the funniest thing I've ever seen</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 17 Sep 2008 18:22:19 -0000</pubDate></item><item><title>Re: Using the Zend Framework in CakePHP</title><link>http://britg.disqus.com/using_the_zend_framework_in_cakephp/#comment-2406367</link><description>Interesting - i guess the most extensible solution would be to check if&lt;br&gt;there is a semicolon and add it if there is not - like your case.&lt;br&gt;Thanks for sharing</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 17 Sep 2008 15:43:26 -0000</pubDate></item></channel></rss>