"Inheritance is a mechanism used to achieve categorization and to facilitate polymorphism. Using inheritance you can build a hierarchy of concepts separated in categories at different levels of abstraction. By doing this, you can efficiently use another OOP concept, polymorphism, which allows the same control code to manage all objects in a category even if they are different in their implementation."

http://www.google.com/search?hl=en&q=define%3A+polymorphism&btnG=Google+Search

looks like code re-use to me.

I already made a code generator for NHibernate that works alot like SubSonic, I'll have to get a blog up and running and post it one of these days.

Forgive me if I'm wrong but isn't using the "readonly" terminology for this is slightly misleading? The readonly in C# specifically states that it can only be set once, within the constructor or declaration whereas with this you could set it anywhere within the class, multiple times.

No, my point was about OOXML, which is supposed to be a standard but is in fact a proprietary format that will have to be reverse engineered. You're also throwing out silly red herrings that have nothing to do with the argument at hand. You obviously have an axe to grind against OSS developers, and I could personally care less.

The entire purpose of a standard is so that you don't have to reverse engineer it to be compatible, saying they'll have to reverse engineer it is just admitting that the standard is completely worthless.

Also, if you think reverse engineering something for 100% compatibility is so easy I highly suggest you join a field in which your talents can be used in that manner.

The reason ODF won't be able to compete is an education/business issue, not a technical one. Many businesses use Microsoft Office for their documents and Office does not support the ODF file format without a plugin, so to be able to interact with your clients you must use the same formats that they use. This obviously means you're going to have to get copies of Office for your business if you intend to interact with other businesses that use it (without looking like some kind of document format evangelist), which cascades and creates vendor lock in to Microsoft products. This is, of course exactly what Microsoft, or any business for that matter would want; and has been their practice for some time now.

If you had paid attention to the whole debacle you may understand why people are upset. It's a poor standard, it hasn't been implemented anywhere (including microsoft office), and it does nothing but give Microsoft the go ahead to convince uninformed managers that using their office product will comply with the ISO requirements that many businesses have. If it had been an actual technical review it would have failed, but Microsoft pulled a lot of strings and got it through. So now Microsoft will have a proprietary file format that no one can implement and stifle real competition yet again for the foreseeable future.

Btw, I love quite a few Microsoft products, and program in .net, that doesn't mean I'm going to condone shady business practices.

i'd like my 30 seconds back please.

probably the best list I've seen (a few tools I'll check out that I haven't heard of before), but no mention of firebug?

"I don't think I trust that they won't be duplicated."
I didn't see an answer for this one in the article. Does duplication actually happen?

I don't know anything about Windsor so I can't comment as to whether this would help, but to get around the annoying rebuild aspect of monorail I just put my controllers in App_Code/Controllers and setup my web.config like so.

<monoRail>
<controllers>
<assembly>App_Code/Controllers</assembly>
</controllers>
<viewEngine viewPathRoot="views" customEngine="Castle.MonoRail.Framework.Views.NVelocity.NVelocityViewEngine, Castle.MonoRail.Framework.Views.NVelocity" />
</monoRail>

Just save the controller and it auto compiles for you the next time the site is accessed.