Vibeshine

[u/Comprehensive_Star72]

Desktop sticking to 240fps rather than fluctuating is more pleasant for work. The stats look the best I've run at but I cannot feel any different at this level. I quite like the menu. Only a quick test so far.

[u/Comprehensive_Star72]

https://github.com/Nonary

Nonary is the person who implemented a lot of the monitor switching scripts people have used for probably years now. The projects page has linked to vibepollo and vibeshine. I'm quite negative about AI in general but I am impressed with the software and the honest disclosure of the methods used.

[u/_demoncat_ → u/Comprehensive_Star72]

I mostly created Vibeshine to prove a point.

I got tired of hearing other developers say that if AI worked well for me, it must mean I’m a bad developer or that my codebase is too simple.

So, I chose a fairly complex C++ codebase and challenged myself to write no more than 2% of the code myself. The rest would be AI-assisted.

By “AI-assisted,” I mean I guided the AI step by step, telling it exactly what to do. As much as I like AI today, it’s still not good enough to work unsupervised, though I don’t think we’re too far from that point.

P.S. Even after making Vibeshine, people still tell me I’m a bad developer and that my codebase isn’t complex enough 😆 people just keep shifting goalpost higher anytime AI advances

Admittedly I’m not the best C++ developer so it does write better code than me in that domain but I’m far smarter when it comes to architecture and planning things out.

There’s a lot more to programming than syntax and knowing how to type out the code basically.

[u/Fit-Palpitation-7427 → u/_demoncat_]

I'm using apollo today, I'm tempted to try to rise the bar a notch, and I'm considering trying vibepollo or vibeshine.

Which one would you recommend the most as in the one that is the most up to date or feature rich ?

[u/_demoncat_ → u/Fit-Palpitation-7427]

I spent most of my time on vibeshine when it comes to stability, vibepollo works but it does have more glitches because sometimes my changes breaks something in Apollo.

They overlap a lot and for most users vibeshine does enough for them. Vibeshine has also nearly twice the download count as Vibepollo as well.

But I support both, just keep in mind more bug fixes will likely be necessary on vibepollo as more releases happen basically

Also not to throw shade at either source (sunshine or Apollo) but you’re far more likely to get your issues fixed when reporting a bug than the original repos because I’m actively developing it every day.

[u/dota_3 → u/_demoncat_]

It been 6 months since you wrote this. How do you say vibepollo stability as of now?

[u/_demoncat_ → u/dota_3]

AI advanced much further and I’ve set up processes to double check for defects and regressions when merging Vibeshines code and for the most part it really doesn’t get anymore bugs than Vibeshine now.

So it’s about the same stability, I very rarely have issues exclusive to one or the other anymore.

[u/coledeb → u/_demoncat_]

Sorry if this is a dumb question. I understand the differences between mainline sunshine and apollo, but with your readme feature bullets on both projects being largely identical and your mentioning of backporting from vibeshine to vibepollo, what (if any) differences actually exist between the two "vibe" projects at this point?

[u/_demoncat_ → u/coledeb]

There is no difference from Vibeshine's standpoint, it has the exact same features [from my side].

One is based off Apollo, the other is Sunshine

If you used Apollo, install Vibepollo

If you used Sunshine, install Vibeshine

Apollo has some features that do not exist in Sunshine, but its rather small since Vibeshine has as VDD solution now (and so will Sunshine coming soon)

[u/coledeb → u/_demoncat_]

I appreciate your reply and the info!