I hear both a and b. But also c. c means: The code is probably almost untested, unsecure and unsupported.

For your first and last (bonus) question: I write in VB and mostly Winforms. Why still WinForms or other older technologies? Because older technologies are proven. And invested in. I have build a complete ecosystem around Winforms during my career, that will cost a fortune to migrate to WPF or any other GUI framework. Further, the ease of the designer and also the ease of runtime generated UI code - not matched by any other GUI framework. And, as most of my software will run on Remote Desktop - al lot of them with high latency and none with GPU acceleration - no other framework gives the same userexperience (performance) as WinForms. Why VB? Because I started out as a Basic Programmer in the nineties, and VB does all I need. The Bonus question - why you don't see much VB on Code Project or anywhere else. That's because we learned. As soon as you ask your question in VB, you are not taken seriously. So, we just convert anything to C# before we ask a question. The same for an article. If it's VB, the chance is really small that it will be allowed. So, also in this case, we convert it to C# and publish it without a problem. Or just gave up and do not try to share anymore.

First, What is Visual Basic? We have VB (classic), VB-Script and VB (.Net) The first one (VB Classic)is dead - the last version was released in 1999. But it's coming back to live; google on TwinBasic and RadBasic. The second one is dying (VB-Script) - Microsoft is phasing out this version of VB. And I think that should have been done years ago, as it is only something to be used by Ransomware parties. The third one (VB.Net). Officially? It's alive. Really? It's dead as the language is not evolving anymore. But, just like for VB Classic, VB.Net is reviving. There is a second implementation (Mercury), OpenSilver is 100% supporting VB.Net, enabling VB to do Xaml, WebAssembly and mobile, and former head of VB, Anthony D. Green has started to take up the task of supporting the VB language, adding language structs and features. So, the answer is Yes and No. Depending on what you think VB is and if Microsoft support defines dead. As I see the projects outside Microsoft, VB classic and .Net both have a bright future. But if you want to depend on MS only, they are both dead.

You completely miss the point. Before the internet there was no such thing as SSL or TLS.

We wrote it much better back then. Now we have internet, we have to find out everything ourselves as nothing gets documented, go to code project and other sites to ask other users how things work. Before the internet, everything was properly documented, so we didn't need those forums. So the answer is that it is much harder now than it was before the internet.

In my experience, no matter how many developers a company has, only one developer knows about a given project. So, in almost all cases it is a lone developer ...

For VB6, you might want to look at the RADBasic project[^] or the TwinBasic project[^]. For VB.Net, you could look at Remobjects Mercury[^]

We marveled at our own magnificence as we gave birth to AI.

I think Exceptions should be handled where they can be handled. Input data should always be validated - on any level. Not doing this in the low level code is the cause of the majority of the security bugs. By example: buffer overflow, caused by the high level part (wrong data in the parameters), not checked and not handled in the low level code, and voila, we have a security problem.

Really? :) :laugh: :-\

No, they worsen it :-\ :-\

You are taking this code seriously?

Hmmm, you are right. The the improved improved version.

function IsEven(number) {
if (number === 1) return false;
else if (number ===2) return true;
else if (number > 2) return IsEven(number - 2);
else return IsEven(number + 2)
}

Now it does negatives too ;P EDIT: because I get serious reactions on this code The code above is how NOT to do it - it's satire.

If someone really uses it, he or she deserves it ;P

That can be done better with a recursive function:

function IsEven(number) {
if (number === 1 return false;
elseif (number === 2) return true;
else return IsEven(number - 2);
}

Now it does all positive numbers :laugh: EDIT: because I get serious reactions on this code The code above is how NOT to do it - it's satire.

I just use ISO 8601 UTC date/time for technical communication and in the cases the date/time should be stored as a string - when stored as a date (without time zone information), I store it as UTC. For display, I just use the settings of the user - show it in his/her format and time zone.

I am advocating for a non-Microsoft implementation of VB/VB.net. I already have the contacts and interest of a programming language manufacturer. If you want this to happen, vote on this on Another version of VB · Issue #491 · dotnet/vblang · GitHub[^] Let us (and Microsoft) know that you want a Visual Basic that is maintained and supported for every development target!

I did a few goverment jobs - they all failed. None of my other projects ever failed. In Goverment projects, nobody cares if it is ever finished. And - in my experience - almost all externals are sitting there to make as much hours as possible so even they do not want the project to succeed. So I don't do any goverment project anymore; it's just a waste of time.

And so you see - everything has it use :)

I still do some projects - just for fun. So If you want, I can enlighten your burden and take the project from you. That is - if it pays enough of course.

Then there is only one thing left to do: find a job where you don't have to work with Microsoft either. If I see your rant, it would be really better for your heart.