Best case scenario: sunk cost fallacy
Worst case scenario: there's a lot of shit you can do when you control a closed source app store, and canonical has a history of doing sketchy shit like selling user data to Amazon
As far as I understand, they're not replacements in the same way nix profile replaces nix-env. They seem to serve a different purpose, but I don't know enough to say for certain.
$ nix shell -p python
error: unrecognised flag '-p'
Try 'nix --help' for more information.
No, it builds on top of nix. But it seems like the only real option for declarative package management.
Nix shell and nix-shell are different commands
https://discourse.nixos.org/t/nix-shell-nix-shell-and-nix-develop/25964/4
Nix run iirc only works with flakes
So does nix shell
Home-manager > nix profile
Also, nix-shell is supposed to be used for debugging, and nix shell/run/develop for using packages without installing them
Depends on what you do.
If you're just browsing, and doing casual stuff, it's not really noticeable. It's perfect for the less technically oriented because nothing changes for years.
I've been using MX for about a year now, but I definitely wouldn't have without flatpak and nix. I need packages that aren't years out of date, so they're all installed through nix home-manager.
The benefit of this combo is that while user packages might break, the system itself will be predictable for the next few years. That means no new bugs, but also that minor issues won't be solved.
Yeah, who'd hate using a package manager that increasingly slows down your boot time with every package installed, or that uses a closed source store to provide you FOSS
Maybe there's a reason canonical has to force it on their users
No, Debian doesn't take your apt install ... command and install a snap behind your back...
I dislike that it takes way too long to boot
- Use the Daemon, it starts a new client in a fraction of a second
- Improve your config and it'll start in under a second anyways
Emacs had some "premade IDE" project I recall that I tried and wasn't that enthusiastic about.
Doom Emacs, spacemacs, etc.
And there are plenty of nvim "distros" like that (lazyvim for example).
They make getting started pretty easy. I've been using Doom for years and never bothered to make a full config of my own.
WELL SURE, BUT BOIZ R SHROOM N BOIZ 'AVE TEK
Is there a better way of starting the emacs daemon?
I just use the DE/WM autostart functionality
Zergs are purely biological, this is more 40k ORK territory
MEKBOI SAIZ WAAAAAAAAAAAAAAAAAAGH!!!!!!!
AI is quite fit for the task of understanding
Sure, and parrots are amazing at spotting fallacies like cherry picking...
if there's something that I can adopt as a default goto solution without having to worry about how each system is packaged/configured.
Go is probably your best bet. Simple to use, and you can compile it so it runs everywhere
The genesis of a nixOS user
cross-posted from: https://programming.dev/post/14020506
> The product of a chat with @[email protected]
(partially solved, will update when completed) Please help with an xfce/powerup bug: black screen after suspend/hibernate
MX Linux, Xfce 4.18
Closing the laptop lid suspends the system, opening it resumes it, but the screen is black. I'm guessing it's related to powerup because suspending through the logout menu and systemctl suspend both work as expected. When it's black, switching to a different tty works, as well as C-M-Backspace to logout.
Same results with both lightdm and sddm, when replacing suspend with hibernate, and I've tried a few solutions like disabling lock on sleep.
Seems like this issue has been around for years, but had a whole bunch of different causes since every other thread has a different solution.
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon > /tmp/xf.log 2>&1
ps -ef | grep -E 'screen|lock'
xfconf-query -c xfce4-power-manager -lv
dmesg, cleared it before trying to suspend
updates:
I'm not seeing a black screen, instead it turns on the display and then turns it off.
Additionally, I tried closing and opening the lid a few times, and it woke up correctly.
I tried it in i3wm with the xfce power manager to suspend after closing the lid. It woke up correctly 10 times in a row.
Solution: start an xrandr config and the monitor turns back on.
Non-general purpose posts
This community is:
> A general purpose programming community for English speakers
Language specific posts like:
and ide specific posts like:
are not general purpose. Posts like that ruined /r/programming for me, and this community seems to be going down the same road. I'm here to read about programming concepts that can be applied to any/most languages, not patch notes for 10 different Js frameworks posted by karma farming bots. If I wanted to read posts like that, I'd have subbed to /c/javascript...
Do you agree with me that they should be removed from /c/programming, and limited only to their respective communities? Or have I missed the point of this community?