IoC/Dependency Injection

[Orangy Tang]

LoC is what Java has above most other languages- I can guarantee pretty much any Java app I write will end up with at least twice as many LoC as it's equivalent in another language

Someone's obviously not been programming in C or C++ recently then.

[Breakfast]

I have of late, wherefor I know not, largely been writing with scripting languages.

I don't really use languages where I have to roll my own memory management- nothing has given me any compelling reason to in the last ten years and I'm not sure anything will as scripting language runtimes get better.

In fairness, C# is only a bit less verbose than Java, but it's a sigificant bit that would certainly incline me towards it in a situation where all other factors were equal...

[purpleguitar]

I have one major gripe with C#:  "properties".  These implicit accessors and mutators force a view of design where your objects are white boxes.  This is contrary to all good OO design principles.  Sure, an expert would know when to use properties and when to avoid them, ... and we're all experts, so the code will all be good, right?  Bringing this back on track, the syntactic simplicity of breaking good design principles leads to higher coupling and therefore dependencies, and not all the injections in the world will help you then.  (Okay, it's only slightly on topic, but it seemed like an opportune place to give my standard C# rant.)