Movie line of the week answer
I didn't expect to get many answers for this one. It's an older film and there's nothing special about the line to make it ring in the readers head, but that was the idea. I had one guess, and one guess only.
The correct answer is...
Help for VB6'ers
Thanks to a link from Tommy Williams VB6 folks now have some help making the transition to the .NET world.
A company to watch...
Two of the three Visio founders are at it again. They've formed a new company and found office space in downtown Seattle. They're joined by the Visio 1.0 development lead, and rounded out by some old time Microsoftie I've never heard of.
Keep a watchful eye on The Graw Group, and yes there's a good story behind that goofball name.
Movie line of the week
It never fails... Early in the week I have all kinds of great movie lines, I'm thinking them up left and right, right and left. Thursday rolls around and I can't remember a single one... Don't you hate it when that happens.
Here's the best I could come up with...
Ah, so it's a test you're looking for. We don't do tests!
Ok, quick, what movie! Send your guesses here
This line comes from one of my favorite films. It has some of the best FX I've ever seen, especially given the time the film was made, 1981. I've seen it a zillion times and will probably see it a zillion more.
Scobleizer: "...I do agree that now Microsoft should focus on helping VB6'ers make the leap over to .NET (you're seeing leaps in that direction in the next version of Visual Studio, code-named Whidbey). And they should focus on getting new programmers (like me) into the .NET world." - Leave your VB 6 code alone, keep the environment, update your apps as you see the need. Legacy is legacy is legacy. The Office team is going through the same thing, right? They have ancient apps built on a mix of Win32 API's, COM, and now some .NET components. They'll continue to support that code base and make changes where they need to. Moving forward they'll spend their time on new stuff, ok at least some of them will. Old time VB coders need to move on, move on to C# or Java. If you're going to continue to make your living on Windows move to C#, if you want to run on other platforms move to Java, or keep a super close eye on Project Mono. C# is the new C++ for Windows coders. If you're moving to .NET jettison VB, and VB.Net, move to the new darling, C#.
Folks will take that statement in a bad way. Don't. You haven't lost your investment in VB6. If you need access to newer technologies figure out how to make the new .NET code work with your VB6 code. That's exactly what's going to happen with a LOT of applications moving forward. Sun will never create a VB clone because it doesn't serve their strategy, it's all about Java! If they made a bigger investment in GREAT development tools, which I hear they're finally doing, they'll get more developers to make the leap. Making a VB6 clone doesn't help them one bit, besides you can get pretty close to VB today with REALBasic, which currently runs on Windows and Mac, but I've heard they're evaluating Linux as a possible platform.
So has anyone out there written any articles on using .NET components from VB6, or doe the VB'ers just want an easy migration path?
SuperBowl and Beef
Just got my Harris Ranch special offer email, yum. Steaks and the SuperBowl, what could be better! Order now!
Old Radio blog
My old Radio blog, yeah I used it as a Harry Potter tracking tool before letting my subscription die.
Funny how I remembered that old URL.
More interesting Longhorn news
CNet News: "...Don Box said the company will not invest much more in Component Object Model (COM) and Distributed Compound Object Model (DCOM)--Microsoft's mechanisms for sharing objects between programs." - Developers of legacy applications will need to keep the pressure on Microsoft moving forward to make sure you get the information you need, now. The Office team is going to have to deal with the same problems as everyone else, they just have the benefit of walking down the hall, or over to another building to ask a question. Even though the article says they won't be investing time in COM that's ok, what more do you need from COM to continue to make your existing applications work? Nothing. The only thing you're going to need to keep your old apps up and running is a good interop layer and you can bet it'll have to be good or the Office team would throw their collective self down on the floor and kick and scream until they get what they want. There are a bunch of different ways to approach the problem. I recently pointed to an article that explains a few.
I'm sure someone will only read the top level line, the one I pasted into this post above. It makes people read stuff, doesn't it? Later he says "Box stressed that COM and DCOM are not dead. 'Only now are some groups inside and outside Microsoft finally taking advantage of COM,' he said. 'Our commitment to COM is not finished…but our annual $6.8 billion R&D spend is not going on OLE32.DLL,' said Box, referring to the dynamic linked library that COM uses. ", so relax and get back to work on the next release of your old apps.