HanselMinutes on 9 - #2 - Weapons and Debugging the .NET Runtime
- Posted: Apr 03, 2007 at 10:03 AM
- 24,921 Views
- 16 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Very few Channel 9 videos begin with the firing of a trebuchet.
This is one of those videos.
Scott and I barged in on Vance Morrison, an architect on the .NET Runtime team, and spent some quality time with him assaulting a wall (we won - the wall didn't even put up a fight) and then talking about Vance's job, which turns out to be quite the challenge.
Vance didn't have much time, so Scott and I were very thankful for the few minutes we got, but Scott was able to dig right down to the interesting stuff quickly. Scott's good at that ![]()
There are more HanselMinutes on 9 videos coming. It seems people dig these things, so we're going to release a few more from the first session, and then put together another set, most likely at Mix.
Thanks again to Scott Hanselman for doing this, and to Carl Franklin for letting us use the "HanselMinutes" name.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Is that a sterling engine on his monitor?
Who knows.
I mean, the guy has a frikkin' trebuchet on his desk. Who knows what else is in that room or on his machines
Word.
More coming, littledawgg
No. You're probably not the only one. I think it's cool, as it tells me right off the bat that the guy probably knows his stuff.
But, the main reason I'm replying is that I realized I could have three comments in a row that ended with smileys
MS has paid out so much money on patents, but a lot - think the Fraunhofer license mess up - of it is frivolous. If they were so concerned about the patent, as a weapon, then why dies MS get patents on the CLR, but publish the CLI as a standard ... so there is that recognition to the world that "this knowledge has to be shared, but you should have to do some work or pay us if you can't figure it out from the specifications yourself".
Alright, I'm just talking....
That's the story that's usually trotted out to defend Microsoft's filing for software patents when it is supposedly against them on principle, but it doesn't really wash. Having a big arsenal of patents didn't help Microsoft defend against Eolas or the mp3 suit. The horse-trading of patent rights does go on, but it is not actually a defense because your oppoenent has no obligation to deal. The only thing that can get Microsoft off the hook in the Eolas case is someone else's patent as an example of prior art not ackowleged on the 'plug in' patent and in the case of the mp3 suit, a technicality of patent law itself.
Clearly having your employees file for patents, as long as it doesn't distract too much from development, is good business because those patents can become very valuable when a horse-trading opportunity occurs. However, they do not for any such thing as a defense - they are more of an investment really.
That's the odd thing - Microsoft publishes specs for the CLR as a standard, but then patents several of the mechanisms employed in their implementation. Why is that? OK, I already said that the patents form an investment or sorts, but isn't it a bit strange that microsoft publishes the specs for a system - one that it provides an implementation of and which isn't intended to be multi-platform and so there's really no need for anyone else to re-implement it - and by doing so, baits other developers to infringe patents that it has filed for? Possibly Microsoft has no itention of using those patents to squash independently developed CLR implementations, but there is no guarantee of that.
What I find disturbing about the patent cubes in particular is that in creating a nice little reward for it's employees, it's also unwittingly created a sinister symbol of what a software patent actually is. I see each one of those cubes as a prison cell for the idea that the particular patent covers. Some smart employee had a great idea for something and now it's locked up in a box so that nobody can use that idea without Microsoft's permission. I'd actually be gutted to have one of those cubes because it would mean that an idea I came up with was now locked up and nobody else, no other company or individual, could make use of that idea even if they had a better use for it than I did.
That's what he meant by that "EBP" stuff.
Sure they could... if they licensed the technology from you.
Nice. Glad to see Vance on c9. We need more VM.
Scott is probably more familiar with ETW than he himself realizes. In Hanselminutes podcast #52 he talks in detail about end-to-end tracing. I can't be %100 sure, but I gotta believe that the framework ultimately calls EventWriteTransfer() from the ETW API to do its thing there.
I've been working with ETW a lot recently (in C code) (and XML for the manifests, of course). But I haven't seen that there is any facility for a "new feature" with "the ability to crawl the stacks" as Vance puts it, in ETW. I would greatly appreciate any pointers to more info on that topic. I read Osterman's blog entry but that didn't clarify this point for me.
Remove this comment
Remove this thread
close