EWW Configuration status

[TheRealGramdalf]

I'm looking at using your bar configuration in my new Hyprland system, and I'm wondering as to the status of the eww configuration - it seems like you primarily use ags now, and the status in terms of maintenance for eww isn't quite clear to me. In any case, I'm curious:

• Does/will the EWW version continue to receive updates?
• Do you intend to upstream gross to nixpkgs? I wasn't able to find it/an open PR.
• Is it possible to use this configuration in a home-manager configuration without passing your dotfiles repository as an input?
• Are the scripts still required, or have they been superseded by gross?
  • Semi-related, do the scripts still require the other dependencies, or can I safely remove (some of?) those?

[TheRealGramdalf]

I suppose also important, what was the motivation for moving to ags over eww? I would think that eww is preferred due to it's memory safety and lean resource footprint.

[fufexan]

• Does/will the EWW version continue to receive updates?

Probably not, as I barely have time to work on my ags config.

• Do you intend to upstream gross to nixpkgs? I wasn't able to find it/an open PR.

No, it's a hobby project and I'd say the code quality is bad compared to other projects.

• Is it possible to use this configuration in a home-manager configuration without passing your dotfiles repository as an input?

Yes, you'll need to copy the eww directory and import it in your home manager config.

Are the scripts still required, or have they been superseded by gross?

* Semi-related, do the scripts still require the other [dependencies](https://github.com/fufexan/dotfiles/blob/eww/home/services/eww/default.nix#L11-L40), or can I safely remove (some of?) those?

The scripts in there complement gross' functionality. Their dependencies are also required.

I suppose also important, what was the motivation for moving to ags over eww? I would think that eww is preferred due to it's memory safety and lean resource footprint.

Eww is pretty limited in what it can do, due to the usage of yuck. You cannot define custom functions or callbacks, nor manipulate windows as easily as in ags. Also, with all the scripts combined, eww takes up way more RAM/CPU time than ags.