v0.6.1

[kRHYME7]

Hi Friends!

I'm the author of Hyde-CLI, and I want to share some updates with you.

My initial vision for Hyde-CLI was to serve as a workaround and wrapper for some features of Hyprdots that the owner did not want to add. Over time, I added several features that have proven helpful to a few users. I’m happy that even 2 to 5 people find these features useful. However, with Hyprdots now deprecated, Hyde-CLI has lost its main purpose.

Should I Archive This Repository?

My initial plans were to deprecate this repository and create a separate CLI. However, this decision might change based on the current situation.

Reasons to Deprecate:

1. I want this repository to only link to Hyprdots and avoid breaking changes.
2. It’s challenging to rewrite the large Bash codebase, which is hard to debug and lacks sufficient tools for long-term maintainability.
3. That’s it...

Reasons to Build a New CLI on Top of This:

1. For users, it would provide a smoother transition from Hyprdots to HyDE.
2. HyDE's script now offers various APIs, allowing a CLI, TUI, or GUI to interact with it easily. This means we could potentially clean up Hyde-cli's codebase.
3. The package is already installed, and the AUR package is well established.

Realizing these points, I believe I should consider salvaging this repository and reusing it to build the new CLI. While it might be difficult to start, this decision could be worth it. I am uncertain at this point, so your comments will be my deciding factor.

BTW, I would prefer the rewrite to be either python or in GO.

God bless!

Please let me know your thoughts on whether I should archive this repository or build an improved CLI on top of it.

---

What's Changed

• doc: Update README.md to include site by @rubiin in doc: Update README.md to include site #90
• fixed typo by @rohit-burman in fixed typo #97
• Feature: Use get reset --hard instead of git pull for updating repo by @zeerayne in Feature: Use get reset --hard instead of git pull for updating repo #98
• fix "Hyde-istall" typo by @boulder-roller in fix "Hyde-istall" typo #101
• CORRECT INSTALLATION URL by @JoeArchV in CORRECT INSTALLATION URL #103

New Contributors

• @rohit-burman made their first contribution in fixed typo #97
• @boulder-roller made their first contribution in fix "Hyde-istall" typo #101
• @JoeArchV made their first contribution in CORRECT INSTALLATION URL #103

Full Changelog: v0.6.0...v0.6.1

---

This discussion was created from the release v0.6.1.

[live4thamuzik]

I'd love to see HyDE-CLI keep going. It is a great tool for quickly syncing an existing HyDE install as well as adding, removing HyDE themes.

Another aspect of HyDE-CLI I really like is that I can avoid some of the tasks that I would typically comment out of the scripts after cloning the repo. For example, I just stick with bash shell and use oh-my-posh for a themed prompt. HyDE-CLI will let me press escape and skip that. I can also get around any modifications to GRUB, systemd-boot, pacman.conf, and nvidia setup. (I already handle those settings with my bash script to install Arch.)

[dieBakterie]

I personally would start from scratch since it's an hell of work to migrate this poorly code base as you yourself said. It's cleaner/less bloat and people who use hyprdots can keep using this hyde-cli/repo and fix stuff theirself if something is missing or not working... also migrating /switching from hyprdots to hyde just is a ton of work for us since a ton of problems that are avoided with an fresh/clean install or even just with using a new user for installing hyde and del the old one...

[Niumination]

Great Job,, king👍👍👍 hyde-cli is the greatest tools, since i use it first time when using old hyde by prasanthrangan

[Shykid002]

Maintain it and Build on top of it easily.

[chrollorifat]

I personally recommend starting from scratch..everything..so that we can build a maintainable, clean and easy to debug codebase..preferably with go or rust. If it is go, i think i can also contribute a lot as i wanna learn go.

[ghost]

It is better to create a new cli to avoid problems etc.

[chrollorifat]

@kRHYME7 also, it would be nice if he can make the new cli accessible to other distros such as nixos.

[boulder-roller]

that's a hydenix problem

[kRHYME7]

It should work on nixos .. Just install it without sudo and PREFIX=$HOME/.local/share

[rubiin]

Lets go with Go. Should be more performant and there are great cli frameworks like cobra which provide shell completions and soon. Example , pokego

[Rastafaustian]

I'll argue for whichever method you believe will produce a better product sooner.
If you choose to go with a fresh start and you're concerned about users upgrading from Hyprdots to HyDE, maybe adding something to Hyde-CLI that will notify users about HyDE or help guide them along the upgrading process could be a solution.

[fatelessdev]

Create a seperate cli from scratch but please inherit all the features from the original hyprdots project

[cocksoft]

Create a new one from scratch for HyDE, archive this one as a fallback for Hyprdots users.

[Stan-breaks]

I support the rewrite , especially with go.

[aarsh21]

I would like to contribute if you are going to rewrite it also , go is better at CLI and i think you should also look into this.

[chrollorifat]

@kRHYME7 my bro, i think majority are suggesting to make a new cli with go. Time for you to make your decision, i guess.

[boulder-roller]

thing is most people have no idea what they're talking about (me included lets be real 😔)

[chrollorifat]

thing is most people have no idea what they're talking about (me included lets be real 😔
that doesn't mean @kRHYME7 should wait for eternity though. That's what we call procrastination. lets be real, @kRHYME7 was in a dilemma between two choices and he just needed that extra push to choose one or the other, not like he needed our concrete hyper super duper analysis by weighing the pros and cons of every minute details.

[chrollorifat]

and it's better to start asap.

[prime-run]

promise me cobra and I'm on board

[kRHYME7]

Thanks so much for all the support and feedback on HyDE-CLI so far. I really appreciate everyone who has used it, helped out, or shared their thoughts — it means a lot to me.

After thinking things through, I’ve decided to go with hydectl (the Go-based CLI) moving forward. Most of the features from HyDE-CLI will be included in hydectl, except for the restoration and installation parts, which I believe should be handled separately as their own tool.

By the way, this repo was created more than 5 months ago—I just hadn’t started working on it until now. So here it is, guys!

I hope to get the same kind of support and collaboration in this new project as we had here. Let’s keep pushing forward together and make something even better!

Thanks again, everyone!
God bless!