Paul, this scandal will reflect badly on your name. Please put this idea on review, it will make many many people happy! We can provide active development for the new VB6 compiler for FREEEEEEEEEEE, what do you want more than that ?
In MS VB6 last only until 2024, in React OS or Open Source Community, VB6 last forever. Lets help the ReactOS developers to make VB6 run smoothly and flawlessly on that OS. Push this app >>>http://community.reactos.org
If you dont want to switch OS or Reversed Engineer the VB6. Help the author of GAMBAS (a VB6 clone,http://gambas.sourceforge.net/en/main.html) to add support on windows (GAMBAS is currently run on Linux but there is also an attempt to run it windows).
Its now time to leave MS, Windows, and the Visual Studio. Just like the symbian developers did to nokia.They walked out from their office after the announcement that nokia was dropped symbian OS.
Lets move and help the open source community especially the React OS, GAMBAS, WINE, and other VB6-clones and attempts.
Here are two GREAT alternative products to VitrolBasic.NET. It's time to take our loyalty, money, and business elsewhere. Since so many businesses are jumping ship from Windows and Microsoft, and moving to Linux, it's time we did the same. Let Microsoft dig its own grave.
One of the main attraction of using windows is the ease of developing apps for it using vb6. If microsoft declined to return vb6, then abandon and uninstall your windows. Make a contribution to ReactOS. A open-source version of windows to make it stable.
Oh, that is SO short-sighted. With a committed developer base, a new head of steam, imagine the coup that MS could have brought off if they had decided to create a new RAD tool like VB6 that was compatible :
1. Ensured compatibility with VB6. 2. Extended the language, new functionality fed via the committed dev base 3. Made the IDE compatible with the old 4. Given the new language 64bit support 5. Given it cross-platform support.
How many would have committed to it? How many would have dived back into the Windows fold. How many would have paid £200-£300 to get back in?
To echo what Karl Peterson said: "Paul, in a word, that's ****. Clearly a 64-bit version is possible, as you've already demonstrated with Office. Which, just as clearly, is why you feel it's untenable to release it as OSS. After 15 years, is it really still impossible for Microsoft to present an *honest* answer to their customers?"
Paul, do you remember when you said "It isn't cost effective to keep rewriting code to get back to functional equivalence" ? Why do you want us to do that now ?
Or when you said "VB6 is still the product to beat in performance." ?
Also guys... rather than continuing our wasted efforts to coax a dying Microsoft to revive VB6, perhaps we should throw all our strength and talent behind a cross-platform product called PureBasic. Microsoft is soon going the way of the wooly mammoth, and so is Windows. It's time we move to newer and BETTER technologies that aren't part of a huge sinking ship...
Microsoft will NEVER open source VB6 because of the fact that it is that good. Microsoft wants to forcefully dictate the direction in which computers and software are going rather than allowing the consumers and market to do so. Therefore, this new evil form of Microsoft (sans Bill Gates) will absolutely not want to compete with one of its own former products driving the direction of computing technology. So, with that guys - who cares anymore? Let these new idiots at Microsoft do the same thing that new comers and know-betters have done to virtually every other corporation in which they have infiltrated... drive it into the ground. I think we can help them out on this.
PAUL, REMEMBER THIS: You said the same thing in 2008 and six years later VB6 IS THE FIRST MICROSOFT LANGUAGE IN ALL CORNERS AND POLLS ON THE INTERNET. LET DOWN THE PRIDE AND BUILD A NEW VB6. If you have NO people specialized in smart compilers (like Microsoft had in 1996-1997) then WE OFFER OUR HELP !!!
Anyway, thanks for the confirmation of 2024, yet it is a beautiful thing from your part !
I wonder if Microsoft actually believe this statement will stop the campaign for an updated version of the VB6 programming language ? All it has done is make Microsoft even less trusted than they were. Developers worldwide have and will continue to request VB6 to be updated or open sourced.
The abandonment of the VB6 programming language has always been a question of trust. Clearly we now have to look for a replacement. Clearly, also, that replacement cannot be from Microsoft - they simply can't be trusted. Who would consider moving to, say, VB.Net knowing Microsoft could abandon it next week.
Paul, in a word, that's ****. Clearly a 64-bit version is possible, as you've already demonstrated with Office. Which, just as clearly, is why you feel it's untenable to release it as OSS. After 15 years, is it really still impossible for Microsoft to present an *honest* answer to their customers?
No I don't think you listened (again) Arrogance has been MS's Achilles heel on several occasions. Vista, the Metro (Win 8 debacle) and the decision to Kill VB 6 and tell developers that it for their own good (no matter how many man-years are required t port their applications). In all situations beta users told MS that there were MAJOR problems, but MS kept the blinders on wasted several year promoting the un-defensible; change for the sake of change just won't be tolerated by educated users Same goes for VB6 it was and is a better language than VB.NET, that's why it is still being used by so many developers, still the fifth most popular language in use today. Their decision on VB6 support is again Arrogant, their decision to not let the VB6 community pursue it's own enhancements through open source is both childish and stubborn. MS says they don't expect us to throw away our code, but that is exactly what they expect us to do; what has NEVER made business sense was killing off VB6 off, is it is the best programming languages MS has developed, period. And why can't the VB6 IDE continue to install/function properly under Win 7/8....poor decisions thought to force developers migrate, no real technical issues that could not have been overcome with the brilliant minds that MS has doing development (vs the mgt delusions to hobble it's VB6 developers),
check Basic4android which allows you to make Android App using VB like language. i am using it for over 1 yr now. and it is fantastic. the creator of B4A also released a Basic4Java which is a VB like IDE but ouputs Java, so our App can run on cross platform.
Lets just put it this way... vb.net aint the language basic. Suddenly it was .net all over. And still it is. It does not make better or faster programs. It does not make easier to use programs. Toolkit come and goes. What Gui framework? One thing in common: all needlessly complex and syntax hungry. Xml? Really? Why do we have json? Because xml is a overengineered piece of garbage... Its just not practical and certainly not human readable. I really still like the concept of vb6. Lean and mean. Can be used next to c if one wants. How is it possible that ms neglected and ignored such a massive company success? Who decided to put it in the wastebasket and came up with .net? Get some common sense... Btw dont get me started on powershell. You want that complex non forgiving piece to replace the cmd and vbscript engine? Wooo you really lost it. Just as .net it is pushed hard... Damn get your act together ms.
For those looking for an alternative, check out www.xerocoder.com. It is not refined yet, but will let you code in BASIC, C++, JAVA, or PASCAL and is cross platform. They are promising a VB6 importer soon, So go to their website and let them know you want it.
As the old saying goes "Remember who brought you to the dance." MS has forgotten that. If their hot shot programmers can write .Net, they should be able to handle writing an up graded VB6.
Biggest problem is MS feels they can do no wrong. I took a had look at VB.Net. Like others have said, it is big, fat and hard to work with compared to VB6. MS forgets that most of the businesses we write programs for are very small businesses, and they don't want to pay for the extra time it takes to develop in .Net.
I have found that I can make Access act like VB6 and produce some pretty nice programs. Also, there is one set of programs MS won't mess with and that is MS Office. They know with Office people can move to OpenOffice for FREE and read and write the MS formats.
Personally, I am converting some things to Access. Also, I am looking at PowerBasic. It creates very small EXE files and doesn't need runtimes. There is a product called FireFly that is similar to VB6 IDE and works with PowerBasic. For using ODBC drivers with this, there is a product called SQL Tools from Perfect Sync. Then SQL Tools can connect to any ODBC driver.
So, if you don' want to leave Windows, here is one solution, and I am sure there are many others.
MS needs to remember that when a customer becomes unhappy with the products offered, it gives the customer a reason to look around.
Paul, If it was so hard to keep old technologies then why was Visual Foxpro kept around another 9 years after VB6 was abandoned?
The simple fact of the matter is MS was hoping the loyal VB6 developers would just blindly follow MS's commands and jump blindly into the total **** that is .NET. Instead what they did is **** off their loyal developers and lost a very large percentage of them to other non MS languages.
To this day .NET has less features than VB6, is slow and bloated and has about 10x distribution size compared to VB6.
It seems clear that hundreds of thousands of developers pleading to Microsoft are going to be ignored, meanwhile MS just keeps losing market share in virtually all markets they are in and they wonder why. If you could have programmed a Windows phone with VB6 with Windows Phone came out Microsoft would own the mobile market now, instead they just keep losing share and keep wondering why.