The most aggravating thing to hear from customers at the PDC? “But I heard from (someone) that VB is (going to be dropped/going away/dead) and that we should switch to (insert language here).” (I hope it goes without saying to loyal readers that this is not true. Otherwise, I’m mystified why I keep getting that check in the mail every month…) It’s not the customer’s fault they got faulty information, but it’s still aggravating nontheless.
I will say that this is so far a very, very, very small piece of the customer interactions I’ve been having here at the PDC. The general consensus seems to be that Whidbey is really going to hit it out of the park for VB users, which is wonderful validation for the hard work the team has been doing. Now we’ve just got to ship it!
(Hmmmm… I wonder if you play some of Don’s songs backwards you’ll hear “VB is dead.” I’ll have to have a chat with Mr. Box about that…)
Where can we find more info on the guts of edit and continue – what the vb.net team had to implement as well as what the CLR team did to implement it?
Also I have seen it mentioned that VB.NET doesn’t expose all possible EnC features in the CLR – what and why?
Just some curious questions…. perhaps a blog entry if you get the chance.
I couldn’t really talk about the guts of edit and continue before, but since Jonathan Keljo’s talk at the PDC (ARC413, "CLR Under the Covers: "Whidbey" CLR Internals) covered it, I suppose it’s fair game… Expect something soon!
And as for the Paul McCartney reference, there was a period of time in the late sixties/early seventies where there was an urban legend going around that Paul McCartney was dead but that the Beatles weren’t admitting to it. There were all kinds of supposed "signs" like Paul’s appearance on the Sgt. Pepper’s album cover. There were also those who claimed that if you played "I Am the Walrus" backwards, you’d hear John Lennon saying "Paul is dead. Paul is dead." (Hence the joke about Don’s band.) I’m sure a Google search for the phrase "Paul is dead" will reveal the whole story.
Hmmm… that’s explains why the reference was lost on me 😉 I either missed that timeframe altogether or just plain slept to many times since then 😀
Pingback: Julia Lerman Blog
Jesus, VB hasn’t been dead yet! I’m a seriou Beatles fan, and I know what you mean by mentioning McCartney’s episode. But, I think VB is still on-going.
I know this blog entry is ancient but here goes anyway:
VB may not be dead, but it is the red-headed stepchild of Windows development. Most .NET developers use C#, and VB developers prefer VB6 to VB .NET, only using VB .NET for .NET Framework technology, not VB .NET.
VB programmers still hang onto VB6 because 32-bit programming didn’t become obsolete as quickly as 16-bit programming did for VB3. I am old enough to remember the reaction VB3 programmers had when VB4 came out; it was similar to the reaction VB6 programmers had to VB .NET.
Once 64-bit computing becomes prevalent with Longhorn and 64-bit Intel/AMD processors, the VB6 diehards will adapt or die. 32-bit computing isn’t going to last.