<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Elegant Code - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-bbaf89be" type="application/json"/><link>http://elegantcode01.disqus.com/</link><description></description><atom:link href="http://elegantcode01.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 22 Feb 2012 11:52:58 -0000</lastBuildDate><item><title>Re: When Opportunity Knocks Answer the DAMN Door!</title><link>http://elegantcode.com/2012/02/21/when-opportunity-knocks-answer-the-damn-door/#comment-446000202</link><description>Thanks guys.  I'm looking forward to new and exciting challenges.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Lagunas</dc:creator><pubDate>Wed, 22 Feb 2012 11:52:58 -0000</pubDate></item><item><title>Re: When Opportunity Knocks Answer the DAMN Door!</title><link>http://elegantcode.com/2012/02/21/when-opportunity-knocks-answer-the-damn-door/#comment-445530520</link><description>Congrats with your career move. The best of luck.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JanVanRyswyck</dc:creator><pubDate>Wed, 22 Feb 2012 01:26:01 -0000</pubDate></item><item><title>Re: When Opportunity Knocks Answer the DAMN Door!</title><link>http://elegantcode.com/2012/02/21/when-opportunity-knocks-answer-the-damn-door/#comment-445434868</link><description>Congrats man. Good luck with this great new opportunity.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason</dc:creator><pubDate>Tue, 21 Feb 2012 23:14:38 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: TranslatorService.Speech</title><link>http://elegantcode.com/2012/02/17/nuget-project-uncovered-translatorservice-speech/#comment-442672558</link><description>I worked on a large project using the MS translator API and was really impressed with the API functionality, which includes Speak().  Worth checking out - &lt;a href="http://www.microsofttranslator.com/dev/" rel="nofollow"&gt;http://www.microsofttranslator...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarod Ferguson</dc:creator><pubDate>Sat, 18 Feb 2012 03:51:09 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: FakeO</title><link>http://elegantcode.com/2012/02/14/nuget-project-uncovered-fakeo/#comment-440261221</link><description>I've written a test data generator that is available as a nuget package ( &lt;br&gt;&lt;a href="http://nuget.org/packages/TestDataGenerator" rel="nofollow"&gt;http://nuget.org/packages/Test...&lt;/a&gt; ) also sources on github here ( &lt;br&gt;&lt;a href="https://github.com/etishor/TestDataGenerator" rel="nofollow"&gt;https://github.com/etishor/Tes...&lt;/a&gt; )</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Iulian Margarintescu</dc:creator><pubDate>Wed, 15 Feb 2012 18:00:05 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: FakeO</title><link>http://elegantcode.com/2012/02/14/nuget-project-uncovered-fakeo/#comment-440134219</link><description>I'm wondering if this is like Moq for entity/property bag objects.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Erik</dc:creator><pubDate>Wed, 15 Feb 2012 15:44:00 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: Disruptor-net</title><link>http://elegantcode.com/2012/02/11/nuget-project-uncovered-disruptor-net/#comment-437367501</link><description>I really like these revealed secrets! Keep 'm coming!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark</dc:creator><pubDate>Mon, 13 Feb 2012 02:51:06 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-436932184</link><description>FYI: Norton WebSafe has your site listed as a threat.  Anybody that has Norton Internet Security Installed and gets a search return with your site in it, sees a caution flag.  More info: &lt;a href="http://SafeWeb.Norton.com" rel="nofollow"&gt;SafeWeb.Norton.com&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jay</dc:creator><pubDate>Sun, 12 Feb 2012 13:54:40 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-432435788</link><description>For the record, I like Node.js. I also like Lego. With Lego I can building something simple quickly. With Node.js I can build something simple quickly. Both are clever ideas. Of course, I would use neither for something I have to rely on.&lt;br&gt;I also have to say that it was because of this video that I got excited when Ryan Dahl announced he was stopping down from Node.js.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Heath</dc:creator><pubDate>Tue, 07 Feb 2012 18:42:02 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431761813</link><description>One of the best ways to get ideas across in software is by crafting good designs.  Of course, that falls on deaf ears if newcomers don't actually study existing software (good and bad) to understand its design rationales at a deep level.&lt;br&gt;&lt;br&gt;I'm also curious what class of people you are referring to specifically as "unix greybeards".  That stereotype, when used in the pejorative, connotes the BOFH sysadmin type, who are merely users in the Unix ecosystem, and which is a far cry from the Dennis Ritchie/Bill Joy/Richard Stallman sort of folk that actually built the software that runs much of the world.  (And whose designs and code bear studying.)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Wang</dc:creator><pubDate>Tue, 07 Feb 2012 05:26:59 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431482555</link><description>You want to know who's to blame for the wheel getting constantly reinvented in IT? It's all the old programmers who absolutely *suck* at getting their ideas across, leaving them to be reinvented by better communicators later. Unix greybeards have a reputation for a reason.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">LindaM</dc:creator><pubDate>Mon, 06 Feb 2012 22:32:08 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431173252</link><description>Microsoft classic asp runs JavaScript server side ten years ago,</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anthony</dc:creator><pubDate>Mon, 06 Feb 2012 16:40:40 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: Chronic</title><link>http://elegantcode.com/2012/02/01/nuget-project-uncovered-chronic/#comment-431129465</link><description>Hey Peter,&lt;br&gt;&lt;br&gt;This may be my lack of understanding how to use the project, however when I write the following tests (in the link below) I see different results than what I would expect. (Not sure if this is because the NuGet project is out of date form the source, but it looks like Install-Package chronic brings in 0.1.0)&lt;br&gt;&lt;br&gt;&lt;a href="http://codepaste.net/6figyb" rel="nofollow"&gt;http://codepaste.net/6figyb&lt;/a&gt; &lt;br&gt;&lt;br&gt;Any thoughts?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason</dc:creator><pubDate>Mon, 06 Feb 2012 15:54:40 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431099128</link><description>Node was not by any means the first app server written in JavaScript. That would be Netscape Livewire.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rmangi</dc:creator><pubDate>Mon, 06 Feb 2012 15:22:22 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431091557</link><description>So you think node is about applying event driven programming to web development?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarod Ferguson</dc:creator><pubDate>Mon, 06 Feb 2012 15:14:04 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431090217</link><description>"Whilst I am deeply interested in Node, the ideas of lightweight HTTP servers etc. I think the jury is still "out" on whether or not Node is a "great" thing."&lt;br&gt;&lt;br&gt;I share your perspective. The post was not intended to endorse node. The superlatives in question (and this post) were regarding the story of how node came to be. The metoeric rise of the community, the most watched repo on github, the fact that a blog post now makes you a fanboy (the divide), etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarod Ferguson</dc:creator><pubDate>Mon, 06 Feb 2012 15:12:40 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431080496</link><description>&lt;a href="http://teddziuba.com/2011/10/node-js-is-cancer.html" rel="nofollow"&gt;http://teddziuba.com/2011/10/n...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 06 Feb 2012 15:02:18 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431038614</link><description>I think a blog post is the perfect amount of 'hype and superlatives' at this time.&lt;br&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jodo</dc:creator><pubDate>Mon, 06 Feb 2012 14:17:32 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-431023100</link><description>&amp;gt;I probably would have guessed something along the lines of a Stanford research lab.&lt;br&gt;&lt;br&gt;And this would be why everyone mocks node fanboys.  Why on earth would you think applying an ancient technique like event driven programming to web development would come from a research lab?  Not even getting into the obvious fact that event driven programming is a terrible match for web development, it has been used for network servers for decades.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 06 Feb 2012 14:01:04 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: Chronic</title><link>http://elegantcode.com/2012/02/01/nuget-project-uncovered-chronic/#comment-430891377</link><description>I checked the class BasicExpressionsTests that you mentioned case sensitive issues for Tomorrow and ran the tests.  I didn't see any issues running the following code.  This doesn't work for you???&lt;br&gt;        [Fact]&lt;br&gt;        public void Tomorrow_is_parsed_correctly()&lt;br&gt;        {&lt;br&gt;            Parse("Tomorrow").AssertStartsAt(DateTime.Now.Date.AddDays(1));&lt;br&gt;        }</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Seewald</dc:creator><pubDate>Mon, 06 Feb 2012 11:44:20 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: DynamicXaml</title><link>http://elegantcode.com/2012/02/05/nuget-project-uncovered-dynamicxaml/#comment-430731994</link><description>Hello Daniel,&lt;br&gt;as creator of this still quite pre 1.0 package, I would like to chime in: You can write &lt;strong&gt;BindContent("Text")&lt;/strong&gt;, the darned thing about using dynamic in this context is that the whole lambda resolution business is done by the compiler. Inference of delegate type for lambdas breaks down in the dynamic scenario, so you have to specify the type of your lambda expression yourself, which is why the property of the DataContext to be bound is specified as a string. &lt;br&gt;&lt;br&gt;For this the project has some helpers that set the correct type for some operations, but by thinking about your suggestion a new helper should be possible that will allow you to do this:&lt;br&gt;&lt;code&gt;&lt;br&gt;// This op sets bind to a fixed, known type;&lt;br&gt;var bind = X.ContextBinder&amp;lt;TypeOfObjectInDataContext&amp;gt;();&lt;br&gt;// bind is some func type whose return is understood by DynamicXaml&lt;br&gt;_builder.Start&amp;lt;Button&amp;gt;().BindContent(bind(x =&amp;gt; x.Text));&lt;br&gt;&lt;/code&gt;&lt;br&gt;&lt;br&gt;I will see if I can implement it in the near future.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frank Quednau</dc:creator><pubDate>Mon, 06 Feb 2012 07:31:03 -0000</pubDate></item><item><title>Re: Solving the upload progress bar problem&amp;ndash;The History of Node.js</title><link>http://elegantcode.com/2012/02/06/solving-the-upload-progress-bar-problemthe-history-of-node-js/#comment-430690545</link><description>Whilst I am deeply interested in Node, the ideas of lightweight HTTP servers etc. I think the jury is still "out" on whether or not Node is a "great" thing.&lt;br&gt;&lt;br&gt;At the moment it is marketing itself entirely wrong - nobody cares about Async I/O, programmers have been doing those for years thanks to things like .NET. &lt;br&gt;&lt;br&gt;The real advantages of Node is quick'n'dirty JavaScript application servers, embracing of the HTTP/REST/WebSocket model for application design and, as its name suggests, being truly "cloud ready" through the separation of concerns via deploying separate and network-distributed "nodular" components which mesh together to form an integrated system.&lt;br&gt;&lt;br&gt;Node is fundamentally an architectural pattern that can be applied to countless technologies. What is to stop somebody producing a NetNode or JavaNode? A mini-HTTP cloud-ready server directly paired with a JVM or CLR? Sounds good to me.&lt;br&gt;&lt;br&gt;So let us wait and see first what actually comes out of it before resorting to hype and superlatives :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nbevans</dc:creator><pubDate>Mon, 06 Feb 2012 05:31:48 -0000</pubDate></item><item><title>Re: NuGet Project Uncovered: DynamicXaml</title><link>http://elegantcode.com/2012/02/05/nuget-project-uncovered-dynamicxaml/#comment-430623660</link><description>Would be even nicer if they had expression overloads for stuff like BindContent. Then you could write BindConten(b =&amp;gt; b.Text)&lt;br&gt;&lt;br&gt;Daniel</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Marbach</dc:creator><pubDate>Mon, 06 Feb 2012 01:22:56 -0000</pubDate></item><item><title>Re: &amp;ldquo;Don&amp;#8217;t be a meme, but a movement&amp;rdquo;</title><link>http://elegantcode.com/2012/02/02/dont-be-a-meme-but-a-movement/#comment-429435728</link><description>Thanks</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JanVanRyswyck</dc:creator><pubDate>Sat, 04 Feb 2012 10:25:03 -0000</pubDate></item><item><title>Re: &amp;ldquo;Don&amp;#8217;t be a meme, but a movement&amp;rdquo;</title><link>http://elegantcode.com/2012/02/02/dont-be-a-meme-but-a-movement/#comment-428402738</link><description>Ya, to be fair it is not all social medias fault for me either. I caught the entrepreneurship bug a few years ago and entered the whole new world of being a business owner. A huge time commitment to say the least! That said, just re-targeting a small amount of time 'consuming' SM into 'publishing' thoughts into blog posts is time well spent.&lt;br&gt;&lt;br&gt;And FWIW, I very much enjoy your blog Jan. Always great topics, so thanks ;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarod Ferguson</dc:creator><pubDate>Fri, 03 Feb 2012 02:14:26 -0000</pubDate></item></channel></rss>
