r/visualbasic • • Apr 12 '21

RAD Basic: a 100% compatible Visual Basic 6 solution

Hi!

I'm Carles Royan and I've just begin a Kickstarter campaign for finishing the development of RAD Basic, a 100% compatible Visual Basic 6 solution. I've been developing it for two years, you could review demo videos on Kickstarter page, YouTube and website.

Let me sharing with you the kickstarter page:

https://www.kickstarter.com/projects/koss3982/rad-basic-a-100-compatible-visual-basic-6-solution

And website:

https://www.radbasic.dev/

I think VB6 has room as a language nowadays and it could be evolved without loosing backward compatibility.

I hope you could help in crowdfunding campaign.

Thanks!!!

20 Upvotes

30 comments sorted by

4

u/bz922x Apr 13 '21

As a small software house with a 500k VB6 application, this is an interesting idea. Converting our application to VB.Net will be a multi-year effort even with automated conversion tools like mobilize.net That said, this is a daunting project. If we were to commit to using RAD Basic, we would need bug-for-bug compatibility with the VB6 form controls. This is not a small task, as we would need datagrid, flexgrid, and datacombo controls to all throw the same events in the same order as VB6. In addition we have several self drawn user controls that make extensive use of line drawing and mouse events. I'll talk to the other developers about RAD Basic.

2

u/koss3982 Apr 13 '21

I know it is not a small task. The new runtime isn't based in COM, as the design has cross-platform in mind. But COM (ActiveX) is a first citizen. The support is as easy and transparent as in VB6. You could review the planned components which will be rewritten at: https://www.radbasic.dev/components.php

for the other components not listed, you could continue using OCX from VB6 runtime. You are retricted to 32-bit, or use Soho library (shipped in RAD Basic) for COM surrogate and "mix" 64-bit application with 32 bit component, demo: https://www.youtube.com/watch?v=YbcShyhze5g

About compatibility: any different behavior is treated as a bug.

2

u/lmatonement Apr 13 '21

Microsoft VB6 as far as I can tell is still alive and well in Microsoft Visual Basic for Applications available with Microsoft Office, right? Obviously that can't create stand-alone applications or libraries, but what's your interest in Microsoft Visual Basic 6? I used it a lot back in the day, but I don't like it, nor do I think it should exist as a language.

By the way, I think it's somewhat funny how little love you're getting for this project, even in /r/visualbasic ! But, hey, live your dream! Be the change you want to see!

2

u/koss3982 Apr 13 '21

Thanks for your encouragement. VB6 is not as bad as it seems. Maybe it is not shinny and fancy as rust or golang, but it works. And there is a lot of application out there which still are actively maintained in Vb6, as the cost of rewritten it is too high.

I have love of part of the community, but really I thought I have more support in crowdfunding campaign. Well, let's see how it goes..

4

u/[deleted] Apr 13 '21

[removed] — view removed comment

2

u/lmatonement Apr 13 '21

Dude, it's held on for like 25 years or longer!! That's an amazing stretch for such a foul development environment! I guess Microsoft Office in the browser would use javascript somewhat like what Google is doing?

2

u/[deleted] Apr 13 '21

[removed] — view removed comment

0

u/lmatonement Apr 13 '21

I certainly never used Microsoft Visual Studio 2019 for working with Microsoft Visual Basic for Applications! The IDE that showed up most recently when I was working on some Microsoft Visual Basic for Applications code (when working with Microsoft Access) was what appeared to be exactly the same as the Microsoft Visual Basic 6 IDE! Object Browser and everything! Either you're talking about developing modern Microsoft Visual Basic (.NET) applications, or maybe there's a way to use Microsoft Visual Studio to edit Microsoft Visual Basic for Applications applications of which I'm not aware.

1

u/Will_Rickards Apr 13 '21

Interesting but i think the project timeline is unrealistic bordering on pure fantasy. I think you're at least two years from something usable on existing projects. And all the stretch goals and future stuff would be after that.

VB6 is the Cobol of my generation.

2

u/JamesWjRose Apr 13 '21

.\VB6 is the Cobol of my gen

This is such a perfect analogy. As another stated that they still use VB6/vba, and people still use Cobol... But to think that a person could build a replacement is just wrong and going to fail.

1

u/koss3982 Apr 13 '21

There are new releases of cobol language nowadays. I don't know if you think it will fail technically or ideological. VB6 or Visual Basic Classic is listed month by month on TIOBE index. Some months on top 10 and others on top 20. From popular C/C++/C#, java, Swift, rust, go and co. there are other languages used as well: VB6, Delphi, R, Perl, ... And fortran is used too!!

So, it is a shame there are a lot of companies using VB6, an environment which last version is before 2000's and with unmaintained IDE and runtime maintained in just works mode.

I think it has come a solution other than rewrite your applications or continue the agony...

1

u/JamesWjRose Apr 14 '21

All true and good statements... Except that it is unlikely that a single person can create function for function match. A language is an immense undertaking and as mentioned by another poster here unlikely to happen in one more year, op has mentioned that he has worked on this for one year already, and only two years to make a new language is just unrealistic, and without matching functionality projects can be upgraded.

Hell, just writing the code to upgrade a project is HUGE.

However, I could be wrong.

0

u/koss3982 Apr 14 '21

I've worked for two years. And I have a lot of experience with compilers and parsers. If you use a tool (I use ANTLR) and do only frontend parser (I translate to C, and CLANG make IL/optimizer and output binary), really it is not as hard as it seems. Math operation, array access, context control, etc. When you have implemented more than one compiler, it's always the same (with little details, of course). What really need effort is Runtime Library (a thing a lot of people underestimates but need more effort than compiler itself).

COM, String manipulation, memory management, etc. has to be implemented in Runtime Library, and it is in development for RAD Basic. Visual Components are in development too, and you could use OCX from VB6, so, you can switch between environments easy.

The project is BIG, I really know it as I'm worked two years and I estimated the backlog of tasks. But it is not huge, if you use tools as I did. If you implement parser by hand, you do backend compiler tasks, etc. Then, you are right, the project is HUGE.

2

u/koss3982 Apr 13 '21

Sorry, I'm disagree with you. The project timeline is calculated carefully with work done, tasks backlog, estimation of effort and 100% dedication. This isn't ny first compiler and a lot of work has done, as you could see in demo videos

2

u/renatojabreu Apr 14 '21

I started working with VB6 reccently and would love to see something like this.

1

u/Extra-Bar-2235 May 21 '25

Angefangen mit kleinen PocketPC mit 500 Zeilen Basic bis zum C64 und dann 80xx PC. Damals mit eine HD mit 20MB konnte ich QB richtig genießen. Später VB1 drauf spielen lassen, DOS!!! Und Heute begeistert mich immer das VBA in MSACCESS in der FIRMA und Ich finde es wirklich in Ordnung und spannend. Für mich ist ein Hobby und wird ein Hobby bleiben, da ich schon eine alter Herr bin. Aber ...

Heute beschäftigt mich sehr stark mit der Welt außerhalb MS der mit abweisende Entscheidung ..., und daher ist für mich eine Plattform übergreifende lösung ein muss. Ich fange ein bisschen an mit LAZARUS auf Linux. Ein "uraltes" aber dank der PASCAL Community immer aktuell. Vielleicht sollte sich RAD Basic auch auf die LCL-Komponentenbibliothek oder ähnlich basieren

Noch ein Aber ...
Zur zeit benutze ich PURE BASIC Lizenziert. Weil ich vermeide alle Software Lösungen die ein Monatlichen Tarif bieten. Einmal kaufen und dann meins.

-3

u/JamesWjRose Apr 13 '21

Hello,

I started with VB 2.0 and worked with each version through .Net... And let me be perfectly clear here. VB is dead. Even VB.Net is no longer having features added, but VB6? Yea that shit has been dead for more than decade.

You NEED to rethink this, cause we have C# and your idea is just, well, bad. Sorry

6

u/Moonbouncer89 Apr 13 '21

I use it daily in the government. Not that I want to be specifically, but until MS Office makes an alternative available, it's gold.

2

u/JamesWjRose Apr 13 '21

Just because you use it does not make it worth a third party replacement.

And there is a replacement, it's called .Net

I mean no disrespect to op, it's simply that this is absolutely a bad idea

2

u/Moonbouncer89 Apr 13 '21

Agree about .Net and C#

0

u/koss3982 Apr 14 '21

No problem, no disrespect, it is your opinion :)

But, I disagree (if not, I don't begin with it, obviously). It is need a third party replacement not because you use it (as a user), but because you write code in it (as a developer).

.NET is a framework, and the replacement would be VB.NET. But there isn't a easy transition. In fact, anything beyond small applications fail. So, people continue using VB6 because the cost for rewrite it is huge. And Microsoft said it ceased development of new features for VB.NET. And go for C# is a huge write.

My opinion is this situation is worse than COBOL. COBOL have support (IBM publish new releases) and is maintained. But VB6 has zero maintenance (Microsoft fix runtime when one Windows Update breaks it). So, it is an agony, a stagnant situation, wondering if some day You WILL HAVE to rewrite it for continuing work with last windows (or ship your application in a VM). In fact, I know an application which is shipped in Windows XP box, as it doesn't run in Vista/7/8/10.

So, I think for people continuing working with VB6, needs a compatible solution with easy transition. This is the main goal and main reason 1.0 release won't introduce language enhancements. It is focused all in compatibility.

6

u/EkriirkE VB 6 Master Apr 13 '21

VB just stopped getting new versions at VB6. It is still used actively in many systems, I used to consult for Sage MAS500 which is a large commercial ERP system written upon it

0

u/Comfortable_Gate_878 Sep 04 '26

VB6 isnt dead, I wrote a nice little program using it only two weeks ago for a stock control system saved the company a fortune to perform such a little task that there existing software couldnt do.

1

u/JamesWjRose Sep 04 '26

How appropriate that you respond to a FIVE YEAR OLD post. LOL

Yes, VB6 is dead. Just because you use it doesn't mean its not dead.

3

u/[deleted] Apr 13 '21

[removed] — view removed comment

2

u/JamesWjRose Apr 13 '21

You are absolutely correct that there are so many applications left in that language. However, there is VB6 and it's old tools that are fully formed and work. There is not a need to use a 3rd party, not fully baked new langage to replace that. If new or updated development on a VB6 app is needed, use Visual Studio 1997 (or whatever was the last version) a 3rd party tool is not going to have all the features and abilities that the old version of VB6 has.

Then if the issue is to rebuild/upgrade, then choose .Net and there is an upgrade process so you don't lose all your previous work and can continue with a language that is currently supported and open source.

Sorry, I promise I am not shitting on OP, just the idea (not all ideas are good) This is not the help VB6 developers need, that's why I mentioned how I used the language for nearly 20 years, before moving to C# permanently.

I don't want OP to believe that this is a good idea and have them waste their time. If they choose to disregard what I say, at least they made a choice with information. If I am wrong, and I often am, then YAY for them! (no sarcasm, really YAY!!)

Anyway, thanks for listening. Have a great day.

2

u/Fergus653 Apr 15 '21

Every feature I loved in VB6 was easily provided in one form or another, in C#. I don't see how any proficient VB programmer would have trouble adapting to C#.

C# is better in so many ways, yet it can still make 32 bit COM visible DLLs which you can produce to replace parts of your old legacy VB systems with. Why wouldn't you just concentrate on seperating out all the functionality that you can into seperate libraries, until eventually the legacy base code is smaller than the .Net replacement?

2

u/JamesWjRose Apr 15 '21

Yea, I am just not seeing the value. But hey, I've been wrong before. I made my point, op is free to continue and if it does work, Bravo!