silent_water [she/her]

oh interesting. I wasn’t aware of that. thanks!

scaling sort thing? do you have a link describing what you mean?

youtubers/streamers have a parasocial thing going with their audience that makes the idea of donating a smaller mental step for their audience (senpai might notice me if I donate type brainworms). FOSS projects historically have really struggled with funding, unless they’re able to secure funding from an org/corporation.

a gift economy is also an exchange of goods but it’s decidedly not capitalism - no one earns any profit and there’s no flow converting money into capital and capital back into money.

vegan archbishop also sounds pretty cool but then people are gonna assume you’re catholic

nix overall is a much better solution to this problem.

no joke it’s how I learned linux, bootstrapping a gentoo install from the toolchain on up, with a printed manual. it’s surprisingly effective, if time-consuming (took me about 2 weeks to get to a booted system, though most of that was compilation time - took ages back then).

learn Haskell, write better code

it’s probably not code golfed and the type signatures probably weren’t elided. because otherwise I’d expect it to be above javascript.

I don’t want Google to have my info. the ads are secondary.

literally every other distribution can solve this problem but Ubuntu can’t?

I think one of the issues with nixos learning materials is that they eschew talking about how to write your own packages. but to really understand anything, you have to get your head around writing and modifying packages. in nix, a package is just a build step that can do I/O during particular phases and produces an output to the nix store, so they’re an essential building block for anything that isn’t utterly trivial.

the other major stumbling block is working out how modules (the things that let you write config for the system) can actually be composed. adding a new module to imports gives you new config params you can set so you can organize your system config in terms of modules and packages to make things work the way you like.

Nix Pills are the canonical learning material for packages. I don’t know of any good learning material for modules - I learned by working on nixpkgs and another involved project that made extensive use of modules.

lastly, nix config files are written in the nix language and it’s a bit idiosyncratic. it almost looks and feels like Haskell but it’s slightly different in important ways. there’s no way around learning it if you have multiple systems and want to share config between them.

frustration, usually, hoping against hope that the answer is relevant.

I use stackoverflow for minutes at a time and it almost never has answers to the questions I need answers to. if it has an answer, it’s usually “you can’t do that”. reference docs are 100% of the time more helpful. so no, I don’t think so.

the owners of SO make far more than the benefit provided to any single dev. if that were not true, they wouldn’t be in business.

nitrokey – they’re open source and mostly support the new FIDO standards at this point.

heartbreaking, the worst person you know made a great point

yep stuck on Xorg forever gang

dear god if I could just run xmonad and dmenu on windows or mac I’d hate employers that tried to force me to use one or the other so much less.

when you say “something is not properly supported” what do you mean? like nvidia/amd haven’t released graphics drivers yet for linux? or some peripheral isn’t recognized?

basically, by buying new hardware just after it launches, you’re effectively one of the very first people to boot that hardware with linux. you can usually make it work but most hardware manufacturers don’t work with the linux devs to make sure support is in place. so devs have to get ahold of the hardware retail and then fix whatever is broken. the exception to this is AMD and Intel - both companies have people working on linux so they will merge support for new hardware into the kernel before that new hardware is even announced to the public. so if you stick to cpus and video cards from those two manufacturers, you’ll make your linux life easier.

even then, though, the support might exist in the latest version of the kernel, but the last Ubuntu or Mint release is still several versions behind. so you’re effectively forced to use a distro that releases updates much faster (ie rolling release), or be willing to make modifications to the system post-install to get it to work.

tl;dr: you’ve got a constellation of requirements that can’t all be met at the same time. either give it 3 to 6 months after release of new hardware or be willing to learn how to make it work. expecting software to work with hardware it hasn’t yet been designed to work with is always going to be a recipe for failure.