bumblebee-status VS nixpkgs

bumblebee-status (github)for bar, hugely modular and uses Python for modules. Nice assortment of included modules, and it's easy to create new ones.

Hmm i think i found a fix for this issue. So the thing is the status bar i use bumblebee-status needs font-awesome. And initially, this was my font configuarion: font pango:FontAwesome, JetBrainsMono Nerd Font 11 and the issue was that, if I was using FontAwesome as well, then the fonts weren't rendered correctly (as shown in the picture) however when I removed it, it worked just fine. And I noticed that two different fonts can be used, one for the bar and one for i3wm itself. Hence I tried that out. So for i3wm's font I had font pango: JetBrainsMono Nerd Font 11 and in the "bar" section I did this:

https://github.com/tobi-wan-kenobi/bumblebee-status << been using this. Works fine for quick and easy setup and go.

I switched to bumblebee-status a few years ago and find it to pretty extensible. Python modules, including lm-sensors support. I have blocks on my bar for radiator push fans rpm, radiator pull fans rpm, both pumps rpm, water in and water out temperatures... as well as a bunch of other stuff like CPU VRM current, package temps, load/usage, etc.

https://i3wm.org/docs/userguide.html#client_colors This is the official page for it. It explains it pretty well. Some people also use https://github.com/tobi-wan-kenobi/bumblebee-status for more color options and themes! Though you might have to point the thing to a custom config file.

Today, in what is still completely unbelievable to me, my small, humble project bumblebee-status reached 1k stars on github. Thank you so much to everyone who uses it or contributes to it, you are awesome! (459 PRs and over 400 opened issues mean that most of the work on this project is anyhow done by the community)

I just patched statuscolors to my dwm build with the aim of bringing colors to my statusbar (I use dwmblocks). I want to achieve something aesthetically similar to bumblebee-status, with each statusbar block appearing in a different color. As explained in the patch documentation, I defined an array of colors in my dwm config, something like this:

bumblebee-status, got some nice themes and info on how to write you own; easy to install too. Check this: https://github.com/tobi-wan-kenobi/bumblebee-status

How about Bumblebee-status or Polybar?" That's a question of preference. Both are excellent.

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...