This is the possibility.
They hold their swords with their right hand since most people are right-handed. So in order to attack or defend yourself, you must ride your house on the left side. That must be the reason.

VB > C

There i said it. While you guys are writing your perfect code, i'll be making millions of my ugly, only maintainable by me, VB code. Then i'll use some of my free time to kiss Gates' ass.

*kiss* *kiss*

100's of accidents?? Umm, that's not exactly something you can blame on the side of the road you drive on....

By the way, why is driving on the left better? If everyone does it, seems to me it'd all be the same?? Left, right, they are just directions...

This has become silly. First off, writing good code is paramount, and is up to the coder to make sure it is just that. Second, in the real world, programs are becoming larger and more complex everyday. Hence, the need for a good IDE which DeVStudio is. As I am no MS fan, that is hard statement to make, but one that is none the less true. The abillity to write large projects, effficently, and have a decent method to manage and debug such large projects is one thing it can do.

Linux, though very close, has not quite reached that point yet. The world of programming has evolved to the point of Toolkits and API's. C is still one of the most popular languages as C++, C#, MFC, .NET, etc, are all built on C. These Toolkits, API's, etc, are now the building blocks in which programs are written. Be it with QT, GTK, KDE, etc.

Where does Visual Basic fit in here, not totally sure beyond DataBase FrontEnd programming and a few other small apps. No matter who puts the tools out, they are intended to speed up development. How these tools are used, well, they have no control of that. Some are bad, made on good intentions, others do as they were designed.

I'm hoping that soon, the Linux community will get it together as it is so close, and release the ultimate development IDE. Maybe it's already out there and haven't found it yet. What I have found is close, oh so close, but not quite there.

Roadhog

You know, here is an example on the reality of things:

I'm have this group project, it's an application, that's due by the end of the summer. Between the 4 of us we have experience in C, C++, Perl, Java, VB, etc. We all love C++, we all love C, but those 2 were the first to go. Why? Because from experience we know that while the 2 languages offer amazing flexibility, in the end we spend more time debugging than actually coding. In the end we picked VB.net simply because of the IDE (Visual Studio). VB might not the best looking language, it may not be the fastest, but when it comes to RAD development VB is a good choice. Personally all of us would've rather used another language (i for one would've prefered Java), but because time is important to us, we picked VB as the profitable solution.

I have come to an opinion resently. Linux is awesome, but do to the fragmented support it has, it will be an underdog to Micrsoft. With the recent announcement by Sun that they will be releasing java source code i think that will be a major step in the right direction however, The linux community needs to come together and use the resources of slackware for the command line structure and redhat for the popular design and GUI from KDE, and Gnome. Microsoft has something like 9 billion going into software R&D every year! There is no way that the linux community can keep up with that! However, I believe that linux has one thing that Billy dosn't have anymore, and thats passion for whats hes doing. The linux community has passion and hope that one day everyone will be able to share sofware freely and contribute to the work of Linus without lawsuits and (MIB) looking over your shoulder wondering if your going to be shot for the software you just made. Thats why I'm attracted to Linux, because i want to contribute to Linus's work and show that i can do something with my life that dosn't require makeing other peoples lives poorer because they had to buy this software and it cost 300+ dollars or more. Call me an idealist if you want be this is truely a free concept and will change the morals of how we do buisness in the USA and around the world. This shows how we are evolving from a kings and lords society to unity and respect for each other. It shows how even though my generation has a problem with athority, its only because we want to question our leaders and ask them why does it has to be this way? Why can't we share what we have to make other peoples lives better.......... sorry i started to preach....... but you get the point......... Linux has compassion and thats why i've made the change!

Don't forget that a shit load of people don't really care what OS they are using as long as they can do whatever work they are doing. Linux is very powerfull, but not very userfriendly to people who just want to get some work done (none programming related, etc). To me Linux is a fun little toy to play with, but most of the time i really don't have the time to configure it all and write my own scripts. Sometimes you just want something that won't be in your way... XP is decent in that respect. I don't love as much as others, but as long it's not in my way of being productive with whatever i'm doing, i'm fine with it.

longhorn isn't written in VB because VB is too high a level language for writing an OS.
they probably wrote it in c, c++ or beter yet C flat major

You what? Let's get this straight - first you say that people don't care what OS they run, and then you say that they don't like Linux because something-or-other? Surely that is contradicting yourself? Sure, some distros are heavy going in that you need to configure this, edit that, etc, etc, but not all of them. Have you not heard of Mandrake and SuSE? If you want something that works well out-of-the-box, requires viturally no 'configuring' - you may need to tell it a little about your graphics preferences, such as what resolution you like working at and colour depth, but mostly they get the card setup right; you also may need to give it a help with how you want to connect to a LAN if a nic is present; neither of these, I believe, are done for you in Windows so you can't complain about that in Linux - and does everything the average user needs, then Linux is for you.

I have maintained for a good long while now that the 'average user' would be brilliantly suited to Linux. They are not going to put undue strain on their machines - pehaps a little web surfing, sending a few emails, writting letters, etc, etc - and they are not in the market to be fiddling with stuff. If you discount the distros that present you with a minimal system and you need to configure stuff yourself, ie just go with Mandrake, SuSE, RedHat, etc, etc, then what's the problem? These distros are heavily tested before release, so the majority of problems arise when you start installing software that didn't come with the OS, or you start fiddling with settings - neither of which the 'average' user is going to do. Linux is just as useable as Windows and can suffer in the same way. The common denominator here is the user. If the user fiddles, things may break. If they do not, then they won't.

Oh, and Frieza, I know. It's called sarcasm.

Well, don't mixed up with the language and the tool. The language itself of the Visual Basic is very lousy but the visual tool creating the language is very easy for faster development of small application (or) non-serious programmers. I agree with that.

But the most important thing is the language itself. I'm not saying that tools are not important but these visual tools will come out sooner or later. Somebody will surely do it some time. For example, Sun had already released the beta version of the "Visual Basic like Java IDE". Then I think "Borland" will also follow this footstep to compete with Sun. In Linux "KDevelop" is a bit of visual IDE and somebody will do "Visual Basic like IDE for Linux" some time. No doubt about it. So those who like visual tools use these tools and those hard-core programmers use their bare hand to write codes.

So my point is , if the language is good and well-designed, there is a lot of flexibility for all kind of programmers whether you use visual IDEs or use bare-hand. But if the language is lousy, like Visual Basic, you have no choice but to use the visual tools because there is no way you could write this lousy code by bare-hand.

iv seen those MS visal basic editors at my school a few times, i realy dont see the point in haveing seprate programs to program in, all it was , was some stupid thingy that could have mutliple windows inside it to edit things, and some dumb toolbars to insert premade code into the documents, personaly id much rather just take a regular text editor and a compiler and im happy, but for a nobrainer language like visual basic wich cant be good sence not even MS uses it to write there programs, if you want a simple language to make easy GUI's, look at java, not overly hard to use, need a simple language for comand line? java or python, theres more then enough languages without MS adding half-cracked languages to the pot,
hmm mybe if you wrote the code right in the first palce you wouldent have to debug it? (actualy i doupt anyone could do that, theres bound to be small misspellings or a forgoten ; or other symbol, but there not realy ahrd to fix as the compiler usual givs the line of code were the error acured, but any big problems should be avioded if you simpily new what the comands are your using)

If you actually look at Visual Basic in a more accurate way, there's a huge bug on it. It has a 64 bits data-type called date, used to represent integers from 1 January up to December 9999. Meaning that any application written today with Visual Basic will most likely be unusable on the year 10.000. It's a fact, and it's called the Y10K-Problem. So, one more reason to avoid it

I'm working on it, give me some time
Big problem, I assure you all. This little bug is going to crash the entire universe. 20 million that VB won't be around in 7996 more years.

I think with the release of SuSE and Mandrake as profit-driven linux, hopefully this'll help the entire Linux community as a whole, since their product's budget will improve tremedously, and their source code available (without having to download it from some shady warez site) developers will have access to top o' the line code. At first I was kind of angry when I heard they're going corporate. But then I realized just how important it really is, since we'll be able to see the source and change it! Bill Gates, hold on to your fanny

Yes, and we all write code that's great from the first try run.
And i'm not talkling about a little one page script. I'm talking about writing full blown applications with multiple interacting components. The perfect scenario would be that every member of your team would write and test his/her code to the max. Making sure that 'all' possible cases were accounted for. But unfortunatly not a lot of people do that, or do a good job of it. We have all been brought up differently when it comes to coding and in a project you have to realize that the code people write ain't going to be the best at times.

Even if all the code everyone wrote individually were perfect, that still doesn't mean that when you put it all together it'll work wonderful. That's where you might resort to some long debugging sessions, figuring exactly where somethign went wrong. You could've avoided it all had you spent more time planning and designing, but even the best of plans can't describe everything. No man is perfect so no plan can ever be.

It's really unfortunate at times. Any mistake you make that's logical, etc (not your syntax stuff) could've been avoided if the whole project was planned out better and everyone knew what was going on and why they are writing their components and how they are going to fit together. But the truth is you can't be prefect. So what can you do about it? For one you could try to make your plan better. But what if you are not that experienced in that area? What if you are just starting up with designing large applications? In terms of coding you could implement some rules and ask that all members follow it (such as using XUnit type testing frameworks will developing their code). All these rules will hopefully decrease the number of errors that could happen in components.
When it comes to programming language, you'd like to pick one that will not be in your way. Especially if you are new at it. Ok that seems strange right? But the truth is when you program you don't always end up programming in the language you know best. After all, it's a team project and everyone has different skills. So you want to pick a language that is at least not too difficult to comprehend and more importantly won't bug you down with low level details that you just might not be concerned with.

Going back to the project i'm in right now. We have 4 people of varying skill levels. We've all done basic C/C++ before. Basic in that we've never done anything highlevel in it (ie, not gui apps, etc). We've also done VB and Java. In both of those we DID end up doing some GUI. We also remember how much time we individually spent 'making our code run' while writing in C/C++. Yeah the point is that we learned from our mistakes and so when we came to VB/Java we were smarter and wrote better code.

The point sitll remains, we ended up picking VB initially (more on that later), simply because it was 'easier' for us to start writing productive code with it. We don't know how to write GUI apps with C++, we've never encountered them. So we picked a language that we had exposure in. Truth is we all deep down wished we could've done with C++, but we remember how long we spend making even the simplest of things work, but here we had a huge task at our hand. So yeah, we picked VB because of time constraint. We simply don't have years to work on it, we need to get it done in 3.5 months. So the best solution was to select a language that introduced the least problems for us right of the start. Something that was easy to get going with fast.

You know, personally, i've been defending VB in areas such as RAD on a few occasions. But the reality is i can't stand the language myself. I find it to verbose, it's annoying at times. So why is it still a good choice? Only if you don't know shit and want to get something done fast. That's if you use VB + Visual Studio. Drag and drop gui development is just plain fast. Does it produce the best of code? Hardly, it's bloated, ugly, code. But that's the reality of our programming age, clients want things done quicklyl, they don't care that you are writing this amazing code in C++ (though they should), they want to see results. Then at the end it ends up biting them in the ass when their application ain't perfect and needs patching, etc...

Oww yeah, as an updated, i'm currently moving the team away from VB and to Java. I'm tired of MS's deeper stupidities, and i like Java a lot more as a language. This whole post might be contradictory at first (it seems i'm going for VB, yet then pick Java afterall), but not if you look at it as a thought process. You write and you come to some senses at the end.

Anyway hope this elaborates a bit on what i've said previously.

PS: I hate MFC, i wish it died.

yes i know , i was trying to play off of that to make a little joke of my own