There's no place you can legally download VB6. Sure, there're pirated copies but aside from being illegal most of them are infested with malware.
For a legal copy try eBay. There's usually some copies for sale there but the price can be a bit steep. The only other option is a MSDN subscription and they cost a fortune.
I wish I could say that it runs great on Windows 10 but it doesn't. You'll need a utility written by an Italian user just to install it and not everything works. It's usable but doesn't work nearly as well as it does on earlier versions of Windows.
Microsoft does not support the IDE on Windows 10, just the runtime.
It's too bad that popularity doesn't extend to employers because if it did I'd still have a coding job. There're jobs for VB.Net but I never could wrap my brain around the .Net framework and that entire object-oriented programming thing was just too complicated for me.
As for the community doing it... there's been so many "New VB6s" announced with lots of hype and promises. After awhile they just quietly disappear. VB64 seems to be the latest since the page for it is gone. I don't see how getting the source code for VB6 would change that.
I'm in the state of Colorado, USA. There's still some classic VB work available but it's all maintenance of older programs that would cost too much to rewrite. However, they won't hire you if you don't know .NET because you're expected to work on that as well. I never could wrap my brain around it because it was way too complicated.
The lack of classic VB work is the reason I'm a "retired" coder.
Well, I suspect that Microsoft sees it differently. All the products you mentioned were intended to make money. While they didn't succeed they don't regard the time spent on them as wasted. On Windows 8 at least, the improvements they made under the hood were rolled into Windows 10.
Open sourcing VB6 won't make them a dime and it will take up valuable developer time. So as far as they are concerned it's not worth doing.
No, they can use as many developers as they want for the review. But no matter what the number MS will still regard it as a waste of developer time better spent elsewhere.
A couple of weeks ago I was at a wedding where I ran into another developer. We got to talking about the good old days of VB6 and I told him that some people had requested that Microsoft open-source it and that MS had said that it "wasn't practical". I have no idea what they meant by that so I asked him if he did.
He didn't but he did know who to ask. His son works for Microsoft as a developer. He emailed me today to pass on what his son told him. Anything being open-sourced has to have no third-party code in it and must have a full line by line code review by a qualified person.
His son didn't know if VB6 had any third-party code and nobody he asked knew. For the review a C++ developer would have to go over every line in the source code. It would be a time consuming process and the company has better uses for its developer's time.
So unless MS sees real value in doing this, such as some major customers asking for it, it's not going to happen.
So nobody has an answer to my question? If there's nobody that's willing or able to update VB6 then it just gives Microsoft an excuse to do a code dump. We'd be no better off than before.
Heck, we'd be worse off because then they could say we got what we wanted.
Is there ANYBODY that's committed to working on the VB6 codebase if Microsoft releases it? If not then we need to stop asking them to open source VB6. It's just a distraction from getting a new version.
Isn't VB6 written in C++? Bringing it up to date is going to be a lot of work. Who's going to do it? What do we do next if Microsoft agrees to this?