What if Micro$oft gets screwed?

OK I admit it I'm pro-ms, but I still have a question lets say M$ does get split up (it will) whats going to happen to Visual Basic? Its Microsoft Visual Basic and Microsoft controls the VISUAL BASIC COMPILERS IT PRODUCES THEM!

AND WHAT HAPPENS WHEN WIN BECOMES "UNPOPULAR" WHATS going to happen to all thos Visual Basic programmers?

Those are just some questions I came up with.

SO UNLESS YOU PEOPLE ARE PLANNING TO PORT VB TO UNIX/LINUX/SOME OTHER OS

I GUESS WE ARE: SCREWED

[code]
Private Sub DeepCrap
on error blame microsoft
if microsoft = screwed then
blame aol
end if
end deep crap

Ok, firstly review MS corporate structure. They were ready for being split into even more than two parts.

Now when the folks at MS OS make new API and other niceties they will have to make the schematics openly available to everyone before the MS Applications can use them.

VB is fine and is not going away!!!!!!!!

Besides 64 bit Intel chips are going to be here next year or following year, a separate OS company can aim directly at this technology, rather than tying it into any Application strategy.Hmmmmm....thinking about that l might move to stop purchase of third party 32 bit controls.