Re:Decompiling Hyper-V Manager to rebuild it from source
by actionfromafar on Tuesday May 07, 2024 @07:06AM
(#40284204)
For years there were patches distributed for pine (or was it qmail?) back when it had a proprietary license, it kind of reminds me of that.
Re:Decompiling Hyper-V Manager to rebuild it from source
by prmoustache on Tuesday May 07, 2024 @08:31AM
(#40284702)
This is also how Apache (hence the name) and the Berkeley Software Distribution (BSD) were born.
Re:Decompiling Hyper-V Manager to rebuild it from source
by wolrah on Tuesday May 07, 2024 @08:31AM
(#40284697)
> I don’t know what I’m missing here but something about this whole idea rubs me the wrong way. Who in their right mind is going to do this in a production environment where there is no apparent possibility to have a shared repository for the updates?
They said right at the beginning:
> The primary goal of decompiling Hyper-V Manager is really to assess its value as a potential open source project, which is what I'm hoping Microsoft can be convinced to do.
Re:Decompiling Hyper-V Manager to rebuild it from source
by awakecoding on Tuesday May 07, 2024 @11:09AM
(#40286579)
Thank you for clarifying - I am in no way suggesting that locally patching a decompiled Hyper-V Manager makes sense beyond its experimental value. Having gone through the exercise, it confirmed it's potential value as an open source project, but this can only realistically happen if Microsoft open sources Hyper-V Manager like they've done for many things in the past, especially software that is no longer actively developed.
I don’t know what I’m missing here but something about this whole idea rubs me the wrong way. Who in their right mind is going to do this in a production environment where there is no apparent possibility to have a shared repository for the updates? And no possibility of any support or warranty (for what it’s worth). It’s worth about the price of whatever clicks the blog post generated.
It’s not like the software is that old. I don’t blame him for disliking the powershell interface but this isn’t the answer.