Anders Hejlsberg - What's so great about generics?
- Posted: Jun 15, 2004 at 9:16 AM
- 271,127 Views
- 14 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…”
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?
This is the first time that I have found the concept of generics has been communicated clearly. Thanks.
A simple, clear, understandable explanation. I wish he would have taught CS at my college.
One thing that bothered me: The interviewer kept saying 'yea', 'yep', ect while Anders spoke.
My advice: just let the Anders answer the question uninterrupted, otherwise it is distracting. I noticed the same thing during the previous museum video
Sorry 'bout that. I'm working on pretending like I'm an android and not interacting at all with the people whom I ask questions. I'll get better at it.
Charles
Charles: yup!
Dang it's hard to keep quiet during interviews, isn't it? Plus, when Anders is talking it sure is natural to agree with him.
CC
Collection classes without generics is sort of efficient, (until you pull a dog out of the hat rather than a rabbit
You see, instantiation of these automagically created beasties might not be painful, unless you are a third party tools/library developer. Consider - your latest and greatest library is shipping to millions. It uses the latest whizzy templates (generics). Oops. It has to instantiate every possibility - go look at the nastiness in GCC or other compilers before you commit to using Generics - or better still, go look at Python and give up on strong typing. I say this as someone like Anders from the M2 school of thinking. Along the way I've ditched strong typing in favour of strong design philosophy. Automatic compilation has made us all lax. We shouldn't forget that at the end of the day a tool is only as useful as the girl wielding it...
I'm pleased to see templates. I want them (but like all things in moderation).
The really cool thing about .NET generics is that it doesn't replicate the code for every type like most other compilers have to. It's all done with fancy run-time type checking that actually makes them a really efficient tool, rather than the number one cause of code bloat.
Very Simple and cool explaination.
the download video keeps asking me about a user name and password
how can i get them??
Remove this comment
Remove this thread
close