Oh huh. Thanks for letting me know! It might be my client I use Infinity for Lemmy. I'll check my actual instance, and then see about opening an issue for Infinity if possible.
Or maybe terminal emulation needs to be brought up to speed with modern computing. New terminal specs and all that.
Nothing is better for remote computing and administration than a terminal. It's far too data data dense for anything to be competitive.
Nothing is better for quick and easy iteration of programming ideas than a quick text output in a terminal.
It doesn't need to be destroyed, it needs some iteration. It's an old technology with a lot of cruft.
JFC, some of these responses here about I 'should' do this or that. This is precisely why Reddit and most social media is cancer and people filled with 0 social and life skills.
I shouldn’t have to do anything. If you have an issue with my crying child, the onus is on you to find another space for yourself to make yourself comfortable instead of mandating what other people should/should not do.
Does that mean that parents should let their kids run around? Hell no. But this also means that you stop acting like another baby and find a way to adjust just like everyone else incl other parents."
FTFY. The problem with this argument is it's just as self-centered as the others. If your child starts crying or throwing a fit, go to the bathroom or something, soothe it, and come back. It's not that hard. If your child isn't poorly behaved, it won't cause any other problems. Don't let your child bother other people by being a nuissance. It's not on them it's not their child.
I've never faked an orgasm, but I've def been there. It's rough. They always say "Oh man men don't last long enough" but when they last longer than you...
Thanks for reminding me I have this installed. I've spent all day playing this instead of doing my work.
I'm aware, but the appimage I run (Slippi Launcher) will run other appimages, and appimage-run can't handle that, since it extracts the appimage, then runs the contents, but it won't automatically do that for other appimages that are run.
Which is why I used a Distrobox and it was awesome, worked like a charm. I used Arch previously, and I just made an Arch distrobox and it worked perfectly.
Probably omitted as "an exercise for the reader" since it's legally grey. And a difficult exercise. I cannot find it at all
BetaWiki is gonna go wild with this.
Sorry for the late reply. In the 2 weeks I've still kept using it and I learned a lot! But a lot of my musings still stand, at least in my mind, but after thinking a little longer, a lot of the thoughts I had also apply to other distros as well.
To answer what you asked in final, a good hypothetical that might answer it is something like GNOME. If the nixos channel blew up in a doomsday scenario, I'd be stuck maintaining my packages myself, right? And I use the doomsday scenario, because the problems here apply for self-made packages as well, but it's easier for me and maybe others to wrap their head around the problem I'm getting at. So with GNOME, I'd have to update every single dependency manually in my nix files. With something like Arch/Alpine I could just have those files, and they have these really neat scripts where I can just bump the version, and it'll download, set the hash up, and bump the version all for me. With Nix there are no such tools. I can't just automate the process, nor is it feasible to do this type of thing manually. As new features are added, so are new options needed to activate those features. And yes, although in this scenario, I would probably just opt to not add these options and set it up myself, when making a package for the general public this isn't the case. If GNOME adds a feature (idk why I picked GNOME I haven't used it in like 5 years) to have extensions managed by the package manager, I'd have to add an option for what extensions are needed and all that. And this is a lot of work, at least as far as I know. The extensions would also have to be packaged.
Gotcha I'll start playing around with derivations. I also just came to the realization that because of the magic of Nix, I can try these things, and if it breaks it, I can just roll back.
So I can use something like systemd.services to make my own services as well? Because I've been wondering how to do this as well.
Hi all,
I've been using NixOS for a while now (About a month now) and I've been loving it, but I've had some thoughts lately.
I understand that Nix(OS)'s claim to fame is the fact that packages are reproducible. All dependencies are versioned and all packages are rollback-able (although not sandboxed). With proper maintenance (nix-collect-garbage mostly), the problem with space is mostly mitigated.
But what if a package's dependencies are out of date? These just stay out of date with their possible security problems as well. Not just that but it's (nearly) impossible to actually do your own manual imperative editing of packages to solve a quick problem since everything is declarative.
Not just this, but Nix uses mostly its own configuration methodology, so isn't this a maintenance nightmare as config files change and options are added/removed? Home manager is a prime example of this potential problem.
Plus more technologies being introduced on top of it to solve problems that seem already solved? (Flakes mostly come to mind).
I have come to the realiziation that, unlike a traditional distro like Arch/Alpine which I used previously, if maintenance dies I cannot feasibly maintain it myself, since it's mostly "magic". The upkeep of all the configurations plus all the dependency packages, and making sure each package compiles and matches the build configuration is a nightmare. I can barely do it with my own personal projects.
Anyways that's kinda it just expressing thoughts about it. I do love Nix(OS) and plan to continue using it. It's amazing, and its capabilities are matched by few to none, and from a user perspective it is an extremely seamless and simple OS. It's mostly from a maintainer perspective that I had.