﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Joe commented on JAOO - Day I</title><description>While I agree that .NET has a killer tool stack, so far I've been fairly impressed with Netbeans for Ruby.  I can't speak much on profiling or monitoring, but debugging in Netbeans from the little I've seen is very similar to debugging in .NET.  Also, Capistrano for deployment is easier to configure than NAnt, although I'm still working on getting it implemented.  And best of all, the tools are always improving.  Free helps too, but I understand that in the enterprise space free is less important.
</description><link>http://ayende.com/2796/jaoo-day-i#comment7</link><guid>http://ayende.com/2796/jaoo-day-i#comment7</guid><pubDate>Tue, 25 Sep 2007 12:35:14 GMT</pubDate></item><item><title>Ayende Rahien commented on JAOO - Day I</title><description>Avi,
  
I wasn't aware of RegisterWaitOnSingleObject, that changes thing, I'm going to check this out, but I am going to assume that several millions waits is going to put some strain on the system.
</description><link>http://ayende.com/2796/jaoo-day-i#comment6</link><guid>http://ayende.com/2796/jaoo-day-i#comment6</guid><pubDate>Mon, 24 Sep 2007 21:06:59 GMT</pubDate></item><item><title>Ayende Rahien commented on JAOO - Day I</title><description>No take, haven't looked at it.
</description><link>http://ayende.com/2796/jaoo-day-i#comment5</link><guid>http://ayende.com/2796/jaoo-day-i#comment5</guid><pubDate>Mon, 24 Sep 2007 20:55:07 GMT</pubDate></item><item><title>Avish commented on JAOO - Day I</title><description>Regarding "wait without blocking an OS thread" - could you elaborate? How is that different from ThreadPool.RegisterWaitOnSingleObject, for example? (I know that one does block a thread, but it's just one thread no matter how many times you use it...)
  
</description><link>http://ayende.com/2796/jaoo-day-i#comment4</link><guid>http://ayende.com/2796/jaoo-day-i#comment4</guid><pubDate>Mon, 24 Sep 2007 20:32:42 GMT</pubDate></item><item><title>Troy Tuttle commented on JAOO - Day I</title><description>"...development is actually a small part of a software project, and there is a lot of other things that I don't think that Ruby does as well as other platforms (profiling, debugging, deployment, monitoring, etc)."
  
  
I agree.  If you have worked as a team lead in a corporate environment for any significant amount of time, you realize language concerns are usually secondary to the tool stack, team dynamics, technical leadership, and developer expertise geared toward maintaining existing applications.  That’s not to say software languages are not important.  They are just a small part of the overall development environment.  
  
</description><link>http://ayende.com/2796/jaoo-day-i#comment3</link><guid>http://ayende.com/2796/jaoo-day-i#comment3</guid><pubDate>Mon, 24 Sep 2007 17:25:04 GMT</pubDate></item><item><title>shawn commented on JAOO - Day I</title><description>Speaking of functional languages, what's your take on F#?
</description><link>http://ayende.com/2796/jaoo-day-i#comment2</link><guid>http://ayende.com/2796/jaoo-day-i#comment2</guid><pubDate>Mon, 24 Sep 2007 17:20:03 GMT</pubDate></item><item><title>shawn commented on JAOO - Day I</title><description>Speaking of functional languages, what's your take on F#?
</description><link>http://ayende.com/2796/jaoo-day-i#comment1</link><guid>http://ayende.com/2796/jaoo-day-i#comment1</guid><pubDate>Mon, 24 Sep 2007 17:20:03 GMT</pubDate></item></channel></rss>