<?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 ghempton</title><link>http://disqus.com/by/ghempton/</link><description></description><atom:link href="http://disqus.com/ghempton/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 29 Dec 2014 16:12:34 -0000</lastBuildDate><item><title>Re: takidashi</title><link>http://takidashi.com/rspecs-let-like-behavior-in-mocha.html#comment-1763612264</link><description>&lt;p&gt;This approach works ok for one layer of `let`-like dependencies, but breaks down after that. E.g. what if `@kind` was also dependent on another variable that is lazy?&lt;/p&gt;&lt;p&gt;In case anyone is interested, I created a separate `lazy-bdd` interface that is the same as `bdd` but has RSpec-style `lazy` and `subject` macros: &lt;a href="https://www.npmjs.com/package/mocha-lazy-bdd" rel="nofollow noopener" target="_blank" title="https://www.npmjs.com/package/mocha-lazy-bdd"&gt;https://www.npmjs.com/packa...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 29 Dec 2014 16:12:34 -0000</pubDate></item><item><title>Re: 10 Things You Can Do With EPF (That You Can't Easily Do With Ember Data)</title><link>http://codebrief.com/2013/07/10-things-you-can-do-with-epf/#comment-1190236403</link><description>&lt;p&gt;Some of these points may not be true anymore. ED does use promises now, however last time I checked they were limited to simple operations. EPF bundles flushing arbitrary model graph changes into a single promise.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Tue, 07 Jan 2014 02:28:30 -0000</pubDate></item><item><title>Re: Moonlighting is the New Job Interview</title><link>https://grouptalent.com/blog/moonlighting-is-the-new-job-interview#comment-842080384</link><description>&lt;p&gt;Getting paid is part of moonlighting.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 25 Mar 2013 18:12:37 -0000</pubDate></item><item><title>Re: Bricolage - On Task Systems</title><link>http://blog.evantahler.com/blog/on-task-systems.html#comment-841347934</link><description>&lt;p&gt;Meant to say task system. I actually discovered the framework and switched to it after attempting to patch together a complex string of regular queues. It's pretty impressive, but is surprisingly low on the radar.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 25 Mar 2013 01:08:02 -0000</pubDate></item><item><title>Re: Bricolage - On Task Systems</title><link>http://blog.evantahler.com/blog/on-task-systems.html#comment-841265989</link><description>&lt;p&gt;What are your thoughts on "workflow systems" (e.g. &lt;a href="https://github.com/jmettraux/ruote" rel="nofollow noopener" target="_blank" title="https://github.com/jmettraux/ruote"&gt;https://github.com/jmettrau...&lt;/a&gt; ). Seems like the next logical abstraction above your definition of a task system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Sun, 24 Mar 2013 22:40:38 -0000</pubDate></item><item><title>Re: Moonlighting is the New Job Interview</title><link>https://grouptalent.com/blog/moonlighting-is-the-new-job-interview#comment-838737499</link><description>&lt;p&gt;IANAL (and its always good to understand whatever employment agreements you've signed), but from what I've seen, what you mention above only applies to work done that is directly related to said company or done using their computers/equipment.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Fri, 22 Mar 2013 14:56:57 -0000</pubDate></item><item><title>Re: Why We Don't Use Heroku</title><link>https://grouptalent.com/blog/why-we-don-t-use-heroku#comment-830366144</link><description>&lt;p&gt;Fair point, there is still some dev overhead. The goal here, however, would be to ultimately have basic Heroku-style configurations be extremely well-tread waters (such as how setting up authentication is with devise for example) that would not require significant dev time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Fri, 15 Mar 2013 14:12:38 -0000</pubDate></item><item><title>Re: Information Technology: sometimes simple, most of the time not: We Should Expect To Pay For Small Open Source Projects</title><link>http://www.itistrivial.com/2013/02/support-open-source-developers.html#comment-807937660</link><description>&lt;p&gt;Instead of being afraid of other Type 0 projects (and re-writing the functionality yourself) you should collaborate and contribute to said project.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Thu, 21 Feb 2013 23:50:52 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-647967362</link><description>&lt;p&gt;Also responded on SO&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Wed, 12 Sep 2012 12:48:01 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-647960438</link><description>&lt;p&gt;The view property is set, but not of the controller you would expect. The view will be set on the controller who's connectOutlet method is being called (e.g. applicationController as opposed to itemsController.)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Wed, 12 Sep 2012 12:41:55 -0000</pubDate></item><item><title>Re: Hacking the CoffeeScript Redux Compiler</title><link>http://codebrief.com/2012/08/hacking-the-coffeescript-compiler/#comment-621318726</link><description>&lt;p&gt;Gotcha. Thanks for the info and the great project :).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Thu, 16 Aug 2012 14:54:54 -0000</pubDate></item><item><title>Re: Hacking the CoffeeScript Redux Compiler</title><link>http://codebrief.com/2012/08/hacking-the-coffeescript-compiler/#comment-621303101</link><description>&lt;p&gt;That is really cool. Can you introduce entirely new syntax this way?&lt;/p&gt;&lt;p&gt;E.g. Ember's create method takes a an object expression rather than a block expression. I was thinking I was going to have to modify grammar.pegjs to support this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Thu, 16 Aug 2012 14:35:54 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-618277571</link><description>&lt;p&gt;Is there any chance you could submit a pull request to the example?&lt;/p&gt;&lt;p&gt;It is my impression that there might be some router api changes for the actual 1.0 release, but nothing that wouldn't be easily refactorable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 13 Aug 2012 14:51:41 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-595566077</link><description>&lt;p&gt;Ember.Route is part of the upcoming 1.0 release.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 23 Jul 2012 14:22:48 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-594990257</link><description>&lt;p&gt;You need to use Ember.Route. Technically, you need an Ember.State subclass that includes the Ember.Routable mixin.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Sun, 22 Jul 2012 20:24:03 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-594989737</link><description>&lt;p&gt;Sorry, don't have time to explore this in PhoneGap, I would make sure a bug is filed on GitHub&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Sun, 22 Jul 2012 20:22:48 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-590302017</link><description>&lt;p&gt;lol what makes you think 0.9.4? I just updated ember to the very latest as of right now and the example still works. Handlebars needed to be included separately.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Tue, 17 Jul 2012 12:41:52 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-589895029</link><description>&lt;p&gt;This will work with v1.0 when it is released. This is based on unreleased functionality.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Tue, 17 Jul 2012 00:52:32 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-589894447</link><description>&lt;p&gt;This is based off of the latest HEAD of the repo. I'm not certain this functionality has been officially released yet.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Tue, 17 Jul 2012 00:51:41 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-581559318</link><description>&lt;p&gt;Thanks for the fix. Care to make a PR?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Jul 2012 01:30:31 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-581548848</link><description>&lt;p&gt;It supports push state. I will think about a migration blog post.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Jul 2012 01:24:47 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-581548171</link><description>&lt;p&gt;It works for me, what browser are you using?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Jul 2012 01:24:25 -0000</pubDate></item><item><title>Re: Anatomy of an Ember.js App Part I Redux: Routing and Outlets</title><link>http://codebrief.com/2012/07/anatomy-of-an-ember-dot-js-app-part-i-redux-routing-and-outlets/#comment-581547683</link><description>&lt;p&gt;As far as I know `App.router.send('items')` shouldn't work. The send method on statemanager/router just invokes an event. If there was a method called items defined that called router.transitionTo then it would change the state.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Jul 2012 01:24:09 -0000</pubDate></item><item><title>Re: The Top 10 Javascript MVC Frameworks Reviewed</title><link>http://old.codebrief.com/2012/01/the-top-10-javascript-mvc-frameworks-reviewed/#comment-492490286</link><description>&lt;p&gt;What do you mean by async issues? Does Angular.js have a run loop?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Apr 2012 16:56:51 -0000</pubDate></item><item><title>Re: The Top 10 Javascript MVC Frameworks Reviewed</title><link>http://old.codebrief.com/2012/01/the-top-10-javascript-mvc-frameworks-reviewed/#comment-492465674</link><description>&lt;p&gt;Thanks for the corrections. I will correct Angular.js to AngularJS shortly, however I need to dig deeper into Angular to verify that view composition is indeed a first-class citizen in the framework and not more of a helper mechanic.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gordon Hempton</dc:creator><pubDate>Mon, 09 Apr 2012 16:29:23 -0000</pubDate></item></channel></rss>