Hi Alex, Yes, definitely true. I am no Microsoft fan myself, but I think people are being just a little too harsh over this issue of Visual Basic compatibility etc.
Microsoft has good reasons for removing Visual Basic support even if some of us don't necessarily agree with them. Its not because they are lazy or have some sinister plan to screw everyone over. This change has been in the works since 2001, and Microsoft made it known that when .Net 1.0 and Visual Basic .NET were released Visual Basic 6 was deprecated and moved to legacy support. In 2008--a full seven years later--Microsoft officially dropped Visual Basic 6 support altogether. Its not like this all happened over night and Visual Basic 6 developers weren't put on notice. In a case like that I have to side with Microsoft because they maintained support for Visual Basic 6 long after it was deprecated and replaced by Visual Basic .NET. They also made it known that they were no longer continuing to support VB 6, and were actively recommending people switch as early as 2002/2003. If accessible game developers continued to use VB 6, ignored what was being said, etc its their own fault. They have no one to blame but themselves for not beginning to switch over to .NET years ago. I for one am happy to See David Greenwood planning to upgrade one of his games using newer APIs and programming languages rather than continue using VB 6 which was designed for a completely different era of computer hardware and software. Cheers! On 12/11/11, Alex Kenny <alexkenn...@gmail.com> wrote: > While I'm not usually the person who will jump to Microsoft's defense, > I don't think it's really fair to say they were too lazy to bother > adding VB compatibility. After all, Windows 8 will still run games > written in VB, but I'm guessing it will require the same tweaks that > Vista and 7 do, namely registering the DirectX 8 libraries. > > While MS will be breaking VB support partly to force people to remove > .NET, another In 1998, most people were using Windows 9X, which is an > entirely different OS architecture than even Windows XP. > > The older code or components get, the more difficult it is to keep > them working as a product evolves, and the more potential problems it > can cause. Off the top of my head, I can think of at least two major > Windows security problems that were the result of code that had been > in Windows for several decades, most likely to maintain > backward-compatibility. > > While I agree that MS breaking VB compatibility is going to cause huge > problems in the audio games community, there are certainly technical > reasons why MS is doing it beyond laziness and forcing people to > upgrade. > --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gamers@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
