|
Christian Graus wrote: every coder I've known who knew one language and refused to ever use another was using vb6 or vb.net
I certainly have known a few of those, but that is far more true in my experience with JavaScript programmers. Though a few decades ago, I remember a number of COBOL programmers like that, also.
I did not understand the value of not moving forward.
|
|
|
|
|
If I were younger, and still had a long career ahead of me, I would consider learning another language but it would probably be Python. Maybe C++ due to it's portability. But I must confess I still use a lot of software written in VB.Net. I still code in it as well. I have not found anything I could not do with it yet, so still works for me. I think some of the VB haters may be thinking of old MS Basic and that ilk which was pretty, well, basic. But VB. Net has very little in common with these ancient dialects. Today's VB has pretty much all the tools of other modern languages and the GUI building capabilities are awesome...
|
|
|
|
|
I found switching between VB.NET and C# is not much of a challenge. Same underlying framework, just as few differences in syntax.
|
|
|
|
|
dandy72 wrote: ChatGPT
I don't know what to make of that.
|
|
|
|
|
I queried it instead of Google. That's all that means.
I rather like the summaries it generates, rather than following link after link which lead to questionable results.
|
|
|
|
|
Ok. In your defense, I just had a ChatGPT bot go off in my face without having clicked on any link anywhere. So all queasy feelings aside, you may proceed to the keep 
modified 3-Nov-23 13:55pm.
|
|
|
|
|
I've asked the Bing AI programming questions and I am thrilled with the absolute confidence with which it tells me bullshit
|
|
|
|
|
At least you can recongnise it is bullshit... I don't want to imagine how many wannabe coders are now copy+pasting from it and wondering why it doesn't work, which actually would be the best case, worst one is it compiles and works, but not as it should.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
As with any topic you ask any AI about, you're free to take the results at face value. Or not.
I've asked it for code snippets before. At least with code, it's generally easy enough to determine whether something works or not.
|
|
|
|
|
|
|
Yes. I also use C#. I don't do much anymore. I have a website built mostly in VB.net continuously expanding since 2005. At 80, the brain is not as sharp as it once was. I didn't start serious programming until about 2000. I used Microsoft Basic on a $3000 Epson CPM machine in 1983. When I started using VBA for Excel around 2000, I found that most of the MS Basic worked with little change. The people at this site have been quite helpful over the years.
|
|
|
|
|
I got serious about coding in 1999, and it was this site where I learned, I don't have a degree. So yes, it's been very helpful. I am 54
|
|
|
|
|
While I don't visit often these days, I consider this site instrumental to my professional success. In my late 20's and early 30's I basically learned industry programming by religiously reading all the latest CodeProject articles. I don't know that I could have transitioned from VB to C# without all the knowledge I assimilated from this site over that decade. I was so grateful that I even wrote a dozen or so articles myself, hoping to give something back to the community.
|
|
|
|
|
I haven't touched it in years. I mean a loooooong time. But, then again, I do web development mainly these days. But, last service I made for a job was in C#. Me no not use VB.NET.
Jeremy Falcon
|
|
|
|
|
I used it a few times. I used VB6 a lot more, my company bought a product written in classic ASP and VB6 and I had to convert it. In 2011, a guy was using VB6 because he refused to learn new things.
My work is nearly all web now, the odd mobile app
|
|
|
|
|
I had to work on a VB.NET WinForm program I wrote almost 15 years ago. Someone found an edge case bug in the program that I had to fix. I find that switching languages is not difficult for me. I mostly use C#.NET now, but I used VB.NET (and VB3 and VB4) for many years. Anyway, I fixed the bug and brought the program up to .NET 4.8. It was kind of fun actually. Beats when I had to work in Assembler and Fortran 77. 
|
|
|
|
|
It's still alive?
I don't think before I open my mouth, I like to be as surprised a everyone else.
PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com
Latest Article: SimpleWizardUpdate
|
|
|
|
|
Yeah apparently. I saw someone else post about it, this is a reaction post
|
|
|
|
|
I worked on a legacy app about 10 years ago written in VB and had to relearn the language just enough to do the work required and hated every second of it.
Only other time was about 40 yrs. ago worked on a motor tester using HP basic and some of their hardware. It wasn't so bad as I remember but that was all I cared to do even back then. Was using assembler at the time and taught myself C and then C++ as soon as it became available.
I don't think before I open my mouth, I like to be as surprised a everyone else.
PartsBin an Electronics Part Organizer - Release Version 1.3.0 JaxCoder.com
Latest Article: SimpleWizardUpdate
|
|
|
|
|
Most of my VB work was VB6, for the same reasons, to update a legacy app
|
|
|
|
|
Yeah... it needs more than a #2 double tap[^]  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 3-Nov-23 3:53am.
|
|
|
|
|
Not dead, but "done".
We will ensure Visual Basic remains a straightforward and approachable language with a stable design. The core libraries of .NET (such as the BCL) will support VB and many of the improvements to the .NET Runtime and libraries will automatically benefit VB. When C# or the .NET Runtime introduce new features that would require language support, VB will generally adopt a consumption-only approach and avoid new syntax. We do not plan to extend Visual Basic to new workloads. We will continue to invest in the experience in Visual Studio and interop with C#, especially in core VB scenarios such as Windows Forms and libraries.
TTFN - Kent
|
|
|
|
|
|
Christian Graus wrote: Left to die on the vine
Do not worry or be sad... Seeing how much VB6 still is alive and kicking (often in the balls). I suppose you will have VB.Net until you retire.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
