This message was edited by xbob at 2003-5-25 7:9:59
: : True, which probably is why you never see a game developer studio seeking VB programmers, for example ;)
: : However, I do believe that VB can be used for many applications where speed isn't that important (otherwise it would have left the market long ago).
: : [/blue]
:
: True, but still, I feel Visual anything should be used as a learning tool to teach new coders what stuff does. I mean, if you point and click and make a window, and then look at the actual source, you can begin to udnerstand whatever language it is you're doing. Me myself, I don't see ANY instance where an app that is not coded halfway decent should be used.
:
: For instance, you know when Valve got the Quake II engine and made Half-Life? Originally HL was playable on a P133 which is still printed on the bottom of the boxes they sell. However, this is a plain lie. In version 1.1.0.0 they ported the regular C/C++ to Visual, and the requirements quadrupled. Where before I played it on a P2/233 with 128mb ram and a 16mb Voodoo3/2000, I had to play it on a friend's P2/450 to make it run with any kind of framerate, even in hardware modes. I could run it on the 233, but below 640x480 in resolution and with all the details turned off so the game pretty much looked like Doom with 3D models. They ruined what was well on it's way to becoming my favorite game. That is why anybody that codes Visual without doing any hand-coding to their works, has no f*(#ing business calling themselves a programmer. They're not programmers, they're a$$es who saturate the market and keep real coders like myself or others who know how to code out of a job. I hope every last one of those people dies a horrible, horrible death. It maybe extreme, but people like that have kept me out of the job I love and that Visual BS has ruined one of my favorite games. Oh and I forgot to mention, after it went Visual and the dynamic memory allocation stuff was broken, they went to static, and everybody and his brother wrote a trainer or hack for the game, so now 75% of the online community cheats.
:
: Sorry if thatwas long-winded and a bit harsh, but there isn't a soul alive who can contradict what I've said. I'm NOT angry at people who use Visual stuff and then hand-code parts of the app as well, because they obviously know SOMETHING about coding and can improve the code that the Visual app was just generating. I'm peeved with those who can only point and click, and possibly type menu names and entries, who probably don't know anything more about a computer than how to turn it on and start Visual Whatever, and possibly shut it down. I know of many people who just hit the power button and never use shutdown. Ah well let me shut my mouth before I wind up getting into another area.
:
: -Sephiroth
:
:
We seem to share the same opinion on Visual products. For instance, at my first job as a programmer I wrote a mail distribution system using Java. I used Visual J++ since that was the IDE installed on the system when I began working there. However, even though the program didn't have any obviouis errors it crashed after running on the server for some time without returning any useable error information. So, after hours of debugging I still couldn't find any errors and decided to convert the project to Sun JDK, and, vola; no problems nor crashing despite that fact that no functionality had been altered ;)
The advantage of using Visual products, however, is that you can learn them in a week or so, and thus they decrease developing time and expenses. Still, unless I could code my Visual programs from scratch using NotePad or some other text editor and link the LIBs ans OBJs manually, I wouldn't concider myself a programmer (take that! *giggles*) ;)