Is VB finally dead?
-
Run!!! :~
-
Run!!! :~
-
The VB6 syntax is dead, but her soul lives vicariously through C# and VB.NET.
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link -
the last post I replied started with I have not used vb is about 15 years... may be it is reincarnating it self :( X|
Yusuf Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]
-
Don't get my hopes up. Marc
-
What are doing browsing the VB forum?!? ;P
Tx, but I know the difference. ;P
-
I wish, still have loads of it to maintain :( It's preferable to the (even larger codebase of) foxpro we have to maintain though....
-
d@nish wrote:
And he pulled everyone working in VB with him.
Not quite. I am the Flying Pennsylvania Dutchman, doomed to program in VB and its descendants 'til the end of time because I recommended writing a package in VB/Access instead of C/C++ in 1994, my reason being that "those programmers are cheap and easily disposable." Three years later, I was helping convert that Access app into a Web app, and have never written anything significant in C/C++ since :sigh:
-
It is in colloquial American English, meaning 疫病神 in Japanese.
-
Meh. C# is certainly elegant, but when I'm thinking out loud and have to read a line of code out, I go right back to using VB.Net syntax - words take far less time to say than symbols
LOL obviously you are NOT a native C speaker.
-
I just read something a while back that indicated VB6 will still be fully supported in Windows 7. Microsoft can't kill VB6. What makes you think codeproject and its 6 million + minions can?
kinar wrote:
I just read something a while back that indicated VB6 will still be fully supported in Windows 7. Microsoft can't kill VB6. What makes you think codeproject and its 6 million + minions can?
VB6, like COBOL before it, has too many binaries out there to let it die.
-
I wish, still have loads of it to maintain :( It's preferable to the (even larger codebase of) foxpro we have to maintain though....
Dave Parker wrote:
It's preferable to the (even larger codebase of) foxpro we have to maintain though....
Now the death of VFP is truly desirable LOL...and only slightly more likely than the death of VB.
-
I wish, still have loads of it to maintain :( It's preferable to the (even larger codebase of) foxpro we have to maintain though....
-
LOL obviously you are NOT a native C speaker.
-
Nope. I learned QBASIC, then legacy VB (and its variations), then VB.Net, then C#, then C++. I'm now learning JavaScript and assembly
Computafreak wrote:
Nope. I learned QBASIC, then legacy VB (and its variations), then VB.Net, then C#, then C++. I'm now learning JavaScript and assembly
*nods* My first programming language was a version of Dartmouth BASIC (the original dialect) as implemented on the APPL time sharing system provided by GE. My user interface was a teletype terminal; my storage medium was punched tape. By the time I got my first permanent programming position, I'd learned FORTRAN, COBOL, Pascal, and BAL through classwork, and had taught myself C, which is the primary language I used professionally for the next eight years. All told, counting script languages like Bourne shell and REXX, I've produced professional work in at least fifteen different languages, with some where I worked in two or three different dialects (BASIC) or library sets (C/C++). Currently I use VB6.0, VB.NET, C#, Javascript, SQL, VBScript, DOS Batch, and some proprietary script stuff, with an occasional C/C++ project. Come to think of it, I'll throw in HTML/CSS (always together) as an additional "language" (just to see what abuse I can attract for it :laugh:).