

InterviewSolution
1. |
Solve : .net? |
Answer» Hi every body Hi every body Do your own homework.VB6 (often referred to as VB classic) as stated uses it's own run-time objects & procedures. MS decided with the first installment of .NET to completely revamp the language- get rid of all that silly stuff from the old, MS-DOS BASIC's. Visual Basic .NET is a good language, in my opinion, it isn't really Visual Basic anymore- it's close, but it feels different. It is, however, a great language in and of itself. Personally, I do most of my development in VB6; I barely touch .NET at the current time. It doesn't suck, though- it's just different. Some people resist change fiercely ) I am a Linux person, so it is hard for me to say that anything Microsoft is good. But I think that VB6 was one of the better things they made. pragma I know that both VB and VB.NET rely on a framework to operate. I think the VB framework is better than .NET because it is SMALLER and faster. I also have heard that Microsoft created .NET to make programs harder to port to other operating systems. Quote from: Linux711 on July 05, 2009, 10:29:30 PM I am a Linux person, so it is hard for me to say that anything Microsoft is good. But I think that VB6 was one of the better things they made. And VB6 is easier () Quote from: Linux711 on July 05, 2009, 10:29:30 PM pragma Yeah that's right. They spent millions of dollars and thousands of man hours just to spite the Linux community, because Microsoft is super villain evil. Right now Bill Gates is laughing his *censored* of in his fortress of doom. I really hate having to be the one defending Microsoft here, because I'm really not that big of a fan. They have done plenty of things wrong, but lets at least get the facts straight. The truth is that Microsoft created the .NET framework to make it easier and faster to develop software for the Windows platform, and perhaps most importantly, make it easier to port software between different Windows platforms. Is software that relies on .NET harder to port to another platform? No not really, .NET code is compiled to byte code, just like Java. In theory this can be execute on any platform with a .NET virtual machine, again just like Java. It is not an evil scheme, just good business sense, to only support it on their own platforms. Microsoft have no interest in creating another Java. But Microsoft have done absolutely nothing to stop other people from PORTING the .NET framework. Ever heard of Mono? In fact Microsoft is indirectly sponsoring Mono through their partnership with Novell. IMO it would be easier to port a .NET APPLICATION then it would a application made with VB6... So that whole "They did it to make it harder to port" nonsense doesn't really work. VB6 compiles to either P-Code or Machine code; either way, it always outputs a windows executable. .NET programs compile, as pragma said, to bytecode. All that's needed is a CLR for the other OS's- and given the fact that WINE essentially duplicates the windows API itself I don't see the task of creating a CLR for Linux or mac as too difficult for the Linux people. |
|