4 ms·
They might start charging for it but heck Microsoft still supports running VB6 applications on modern Windows. Not a fanboy by any measure but killing projects
by TavsiE9s 4y ago
They might start charging for it but heck Microsoft still supports running VB6 applications on modern Windows.
Not a fanboy by any measure but killing projects and products left, right, and centre isn't something they usually do.
- benatkin 4y agoYes, but what about VB6 itself? "Where can I install/buy Visual Basic 6?" https://social.msdn.microsoft.com/Forums/azure/en-US/49c35ab3-ead2-43d1-9fa8-69aa277a8d9c/where-can-i-installbuy-visual-basic-6?forum=vssetup https://social.msdn.microsoft.com/Forums/azure/en-US/49c35ab...
- _gabe_ 4y agoThere's nothing wrong with no longer wanting to distribute a 25 year old application that you no longer support development tools for. However your comment is completely disingenuous. One of the first links I ran into was a massive support article from Microsoft about how they will still allow VB6 applications to run on Windows and gave detailed instructions/tools on upgrading a Visual Basic project so you can continue development and don't lose all the work. > While the Visual Basic 6.0 IDE is no longer supported, Microsoft's goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. The resources available from this page should help you as you maintain existing applications, and as you migrate your functionality to .NET.[0] This is much better support than other companies provide for discontinued platforms. Do you personally want to be on the hook for a version of your software you wrote/released 25 years ago? Especially if you've released what you consider to be improved upgrades of the software? Would you even be willing to help users upgrade from your 25 year old software? If the answer to any of those is no, then you're providing a very skewed perspective on what reasonable support for a product looks like. And once again, Microsoft is still writing articles 20 years after the initial release to help users upgrade. For all the bad crap Microsoft does, completely abandoning widely used frameworks is not one of them. [0]: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6.0-documentation https://learn.microsoft.com/en-us/previous-versions/visualst...
- benatkin 4y agoMoving the goalposts are we? I repeat. Their backward compatibility isn't amazing. It may be good but let's stop pretending Microsoft deserves special kudos for what's actually a mixed bag in terms of backward compatibility. And look at the sibling comment to mine about bad backward compatibility with data, in the case of Microsoft Word. Edit: not a sibling comment. Here: https://news.ycombinator.com/item?id=35296368 https://news.ycombinator.com/item?id=35296368
- Kwpolska 4y agoWhy would you want to buy the VB6 IDE? If you’ve got legacy VB6 stuff to maintain, you’ve probably got a 20-year-old license for the IDE already. If you somehow do not, you can buy a Visual Studio subscription [0] and get it. Supporting something does not necessarily mean they sell new licences. [0] https://visualstudio.microsoft.com/subscriptions/#software-and-downloads?cat=visual-studio-enterprise-subscription-with-github-enterprise https://visualstudio.microsoft.com/subscriptions/#software-a... > "Download complete list of software" lists VB6 as available.
- benatkin 4y agowell, if it's so great that you can run old apps, what if one of those old apps you run, you want to make a tiny change to it? but there's gonna be security issues. still it shows that Microsoft's legendary (albeit narrow) backward compatibility doesn't really mean a whole lot, except for sounding cool > you’ve probably got a 20-year-old license for the IDE already As for this, no, someone could pick up an old app written by someone else, or lost their copy of the license, or maybe the license belonged to a company they no longer work for. Also it apparently doesn't apply to the person asking the question...
- Kwpolska 4y agoYou can get a copy of the VB6 IDE with a Visual Studio subscription if you really need it. It works on Windows 11 — you can search for "visual basic 6 windows 11" on YouTube to see it in action (I’m not linking to any videos, since those videos tend to suggest less legal ways to acquire software).
- verdverm 4y agoThey recently killed off their AR/XR teams which were really good tbh, made me sad...
- nextlevelwizard 4y agoWhole point is that Dockerhub dared to ask for money instead of hosting your stuff for free and paying for the bandwidth. The reason why Github is free for normal users it that Microsoft extracts value out of the code you host there, by at least training their LLM. Same will apply for your docker containers. This is part of the Embracing open source. Now they have already started selling Copilot and with CopilotX bringing new AI assisted stuff to code reviews and pull requests even more people will migrate over. This is part of the Extending. Then after they have everyone they can get to use Github and they have extracted all value from your code they will move to the last step and ask you to pay for hosting your stuff and while git is free to use and you can setup your own servers the general UX will be so much better that even hobbyist will pay. This is the Extinguishing
- benatkin 4y agoOr they could make it so if someone pays $30/mo they can get a notification every time someone visits their GitHub. This is a reality for LinkedIn which is also owned by Microsoft. Don't let Microsoft ever get away with saying they respect privacy...
- palata 4y ago> Don't let Microsoft ever get away with saying they respect privacy... Don't let any of the Microsoft-sized Big Tech companies ever get away with saying they respect privacy, I would say
- zdragnar 4y ago> The reason why Github is free for normal users GitHub has always been free for normal users, even before MS bought them out. It is a pretty classic loss leader to get developers so comfortable with it in their personal work that they push their employers to pay for organization accounts. Neither your extend nor extinguish meet the classic definition of either. They aren't changing the spec of git. Having a nice UX doesn't count as extinguish. Literally anyone can set up gitea or another git server. They might not get the cool toys like copilot, but that isn't git. This is not EEE, this is watering down EEE to look not nearly as terrible as it actually was back in the day. If anything, it looks like a shill for MS trying to get people to forget what EEE actually was.