What it is so great about managed code

"urn:schemas-microsoft-com:office:smarttags" />
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Robert
Hess
from .NET Show fame invited me
and a few other notables to drop by the next taping of the .NET Show to revisit
what is so great about managed code.
style="mso-spacerun: yes"> I think this is GREAT because sometimes
we get so focused on one angle of the technology: Web services, ASP.NET, client
side programming, etc that we lose sight of the big picture.
style="mso-spacerun: yes">
"urn:schemas-microsoft-com:office:office" />

style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">

style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Suggestions on what I should
cover?What do you think are the
core benefits of managed code? What
do you think Microsoft doesn’t talk enough about wrt to managed code?
style="mso-spacerun: yes"> Love to get your
feedback!

Don’t tell us stuff we already know 🙂 (ie. we already know the core benefits of managed code, so feel free to mention them, but don’t spend more than 30 seconds on them). The .NET show seems to always ends up talking about old, boring stuff that everyone already knows (except that one episode when they talked about that damn poster for 2 hours…). With all the great minds at MS, you would think that they could make the show at least as interesting as .NET Rocks…

Performance. Especially performance compared to native code. Many people are still thinking that native code is always faster than managed code. Tell us why it sometimes isn’t. Performance of the garbage collector should also be covered. The early Java is suffered because of its so stupid garbage collector. CLR’s gc isn’t that stupid for the first release, so tell us how not stupid it is.

Well, I was really impressed by seeing Eric’s allocation profiler for the first time. It really shows how the GC works in a graphical way, so it is easy to understand why this is a good thing. The whole GC obviously one of the biggest benifits of the managed world.

Well, the best thing I think about managed code is how MS keeps raising the bar and reducing the load on developers.. No longer do we have to develop code to look after security we can just hook into the stuff developed by microsoft. Also, the sanding box is great and gives people the confidence to run applications over the web.

That said.. I agree with Jesse and give us some insights that aren’t widely publised.

More on the patterns and practices for using Attributes/Reflection/CodeDom. Also if you can highlight some of the Extensibility mechanisms within the Framework (may be more details on contexts/Interception/Appdomain). Maybe point to Rotor code while explaining the benefits of .NET