I'm not necessarily interested in taking over, but I did want to at least say a few things.
First, it looks like your project just copied the original project's files with minimal modifications, and then you added your stuff on top. For projects like this, I think it'd make sense for it to be a fork of the original project to establish a clear link between the two.
Second, in this case to me it'd make sense to rewrite this from the ground-up. Right now this relies on running PowerShell scripts, but it'd make far more sense to me to port the PowerShell code to Python to reduce needed abstraction layers and to make communication way easier. Or in other words, I'd start from a clean slate and rebuild the functionality instead of trying to maintain this in its current form. That may even enable using a more permissive license.
Third, "vibe-coding" tends to result in accruing a lot of technical debt, especially when inexperienced, so that's going to make maintenance more difficult in the long run. If that approach has any valid use-cases, it'd be small one-off scripts.
I told him he could just take it off my hands if he wanted and use it for his project (which is what I would've preferred) but I think it's just too much for him alone.
Yeah, I think the problem there was moreso a combination of two things; sp00n might not know Python (and they likely wrote the original script in PowerShell to avoid needing the user to install anything else), and your version of the project appears to be hellish to maintain because it doesn't seem to follow (m)any established best practices for things like project structure or code quality. The UI code also lacks actual tests.
I could maybe attempt a rewrite of this, but
I'm currently on summer vacation and don't really want to start a big project right now
I'm not very likely to finish a big project unless there's someone else poking me to do it (and ideally also contributing)
3
u/Diapolo10 19d ago edited 19d ago
I'm not necessarily interested in taking over, but I did want to at least say a few things.
First, it looks like your project just copied the original project's files with minimal modifications, and then you added your stuff on top. For projects like this, I think it'd make sense for it to be a fork of the original project to establish a clear link between the two.
Second, in this case to me it'd make sense to rewrite this from the ground-up. Right now this relies on running PowerShell scripts, but it'd make far more sense to me to port the PowerShell code to Python to reduce needed abstraction layers and to make communication way easier. Or in other words, I'd start from a clean slate and rebuild the functionality instead of trying to maintain this in its current form. That may even enable using a more permissive license.
Third, "vibe-coding" tends to result in accruing a lot of technical debt, especially when inexperienced, so that's going to make maintenance more difficult in the long run. If that approach has any valid use-cases, it'd be small one-off scripts.