“Robinson”!?!

I’m sorry but you’re going to have to hand in your passport.

Why would they want you to have a working program? How does that help sell you more stuff?

…Am I not allowed to use “y’all”, north of the 49th parallel? Do we have to bring back “thou” so “you” can be plural again? Or is this part of the Quebecois plot to force everyone to parler en français donc nous pouvons utiliser “vous”? C’est bien, anyway, j’suppose.

I mean, you don’t have to buy the new one. I guess as long as they’re not forcing you to upgrade while your current phone is still fine, it shouldn’t have too much impact on e-waste and stuff for them to refresh the parts list and specs for new buyers.

…No. It seems like a bad time to be a plant. Too many wildfires, weird things are kinda happening to atmospheric composition, plus invasive species everywhere— Ugh, pine beetles crawling all up in my skin, hogweed taking my nutrients? No thank you. Maybe later— Definitely want the autotrophy eventually, but taking like a 95% hit to metabolic rate and being unable to go indoors obviously wouldn’t be acceptable either…

Seriously though, the comment you replied to also mentioned a few products by name, so I thought I’d reflect that hey, Bluetooth hasn’t been quite as bad as I’d expected it would be, even if most headsets are either overpriced or garbage.

Other than the 3.5mm still being universal basically everywhere except for phones, it’s also universal in a purist physical sense.

Any old piece of scrap copper wire connected to a 3.5mm jack, wrapped vaguely into a coil, and placed next to something magnetic, should form a working speaker compatible with the 3.5mm jack. It won’t sound hi-fi, but it will work, because unlike Bluetooth or USB-C where you have to read hundreds of pages of standards and do a bunch of engineering just to figure out how to understand the signal, the signal in the 3.5mm jack basically is the sound.

This has direct practical implications as well: The transparent simplicity vs opaque complexity is why wired headphones can be so cheap and yet so reliable, or as hi-fi as your DAC and the speaker cone will allow, whereas Bluetooth devices are comparatively expensive, a mess to connect, fragile, bandwidth-limited, and environmentally and ethically dubious.

Bluetooth, and even USB-C, is basically black magic— Which wouldn’t be so bad, except that it’s also glitchy black magic. And this remains true regardless of device availability, because it’s determined by the physics of the technology itself is implemented.

I’ve been using the same (comparatively) cheap Sony WIC100 in-ear Bluetooth headset every day for several (over four?) years now. It’s lasted longer than basically any of the cheap wired earbuds I kept replacing before ever did, and still has all-day battery life too. I haven’t been particularly careful with it; Generally, I’ve just crumpled it up and stuffed it in my pocket with my keys, and probably semi-regularly snagged and yanked it on stuff pretty hard. Losing it is not really a concern; It’s all one flexible piece, and it’s basically the same profile or even slightly bulkier and heavier than wired earbuds when coiled up (but still more convenient when worn, because it doesn’t run the length of the torso). Plus they can just dangle safely from my neck when I need to hear stuff around me, which neither wired headphones nor “true wireless” headphones can do.

I agree with all your points in principle, and I still pay attention to the headphone jack when evaluating phones. But the corporations that make our consumer electronics have decided this is the trend they’re going with. Ultimately, you can either adapt, stop using the technology, or make your own with Raspi and SLA or whatever.

Let us not forget that S7 and S7 Edge had headphone jack and were waterproof.

Not user-disassemblable, much less Lego-style modular, though. Easy to make something “waterproof” when you can just seal it shut with “gooey black adhesive”.

I personally think the headphone jack is a wonderful truly universal and effectively completely open standard that’s very good at what it does, and which furthermore is doubly useful as a generic power and analog signal delivery mechanism, while mandating its supposed successors like Bluetooth and USB-C needlessly and massively inflates the technical and material cost of just playing a dang sound file. You could get serviceable wired headphones that last forever for like $5 if you were lucky; Nowadays, you pay at least ten times that for fragile lithium batteries and circuitry that will break in a couple years, and I really don’t like this trend of taking away capabilities for less robust alternatives while portraying it as innovating.

But I also actually use my Bluetooth headphones way more than my wired ones, and I appreciate the potential engineering and market challenges in what Fairphone is trying to do here.

ABC.xyz?

malware

Actually, yeah, that basically fits.

Don’t say that, @FlyingSquid. You’re beautiful, and when us primates are doing ruining ourselves, you will inherit the earth and fly over mountains and forests as well.

Who is this “God” Person Anyway?

Lmao, I’ve had literally 40-70GB of highly active application swap on an SSD for the last couple months now because I opened stuff and then didn’t close it.

That said, I chose and installed that drive years ago specifically for this use case (though originally for less intensive/more reasonable cases), and I’m aware of the stupidity of letting it be used like this now.

Usually rated “Gold” or “Platinum” on AppDB:

https://appdb.winehq.org/objectManager.php?sClass=application&iId=12274

Platinum: “Applications which install and run flawlessly on an out-of-the-box Wine installation”
Gold: “Applications that work flawlessly with some special configuration”

Click on a version. Apparently it works perfectly, but you need to winetricks corefont, vcrun6, speechsdk, and sapi for the initial install.

…That’s a salt, though, right?

If you’re counting non-NaCl salts as answers, then basically any “mineral” our body needs would probably be delivered at least partly in salt form. Just reading off some multivitamins here:

• Calcium Carbonate
• Chromium Chloride
• Cupric Sulfate
• Potassium Iodide
• Ferrous Fumarate
• Magnesium Oxide
• Manganese Sulfate
• Sodium Molybdate
• Sodium Selenate
• Zinc Oxide

(I haven’t fully checked all of these are salts­— But I mean, a lot of of them are blatantly chemical analogues of stuff that definitely is salt (E.G. “Potassium Iodide” vs. “Sodium Chloride”), plus they’re metals bonded to ionic groups so they’re definitely not alloys or covalent molecules or ceramics.)

This is probably because in order for our body to absorb stuff, it basically has be water-soluble, which means salts work quite well.

When eating real food (plants, animals, and fungi), I assume a lot of this won’t be in salt form, but rather it will mostly be bound up in proteins and DNA and such. For example, iron should be primarily in hemoglobin instead of ferrous fumarate. But some of it, for example the potassium, will definitely be technically in the form of dissolved salts/minerals in the fluids inside the food.

You can of course also rearrange the compounds around. For example, this can of Windsor-brand “salt free salt substitute” I have here further lists:

• Potassium Chloride
• Calcium Silicate
• Magnesium Carbonate

You’ll note that these are some of the same components as in the list above, just a different combination. I’m pretty sure any ionic mineral that includes at least one ion that our body needs technically counts as “food”, as long as the other half isn’t poisonous— They should be basically the same when they dissolve in the water in our stomachs anyway.

Meats can also be preserved by adding nitrates and nitrites to it, though technically I guess that’s more of a likely-carcinogenic additive than part of the “food”.

Fun fact: Your body sorta knows when it’s low on minerals, and will want to start eating dirt and rocks in order to make up for it! Over 100 different types of primate do it too. So in that case, you could probably argue that plain rocks and soil literally are food, in that they provide vital nutrients the body needs and that your brain is smart enough to know that. …These days it’s apparently considered a mental disorder, but I swear it made much more sense back when the likeliest thing you were going to eat was some mud, rather than lead-contaminated radioactive refrigerants or whatever it is we’ve surrounded ourselves with.

Enjoy, also, this lovely video from a chemistry Youtuber and his friends taste-testing which alkaline-chloride salt tastes the best!

I am not a doctor. Don’t go around eating rocks unless you’re a bird or some other type of dinosaur.

The concept of a “master copy” has been around and in widespread use for around a century. It has nothing to do with either software nor social (in)justice. It’s just the thing you photocopy so you don’t end up making photocopies of photocopies. IMO It should make sense to anyone who, you know, has seen and used paper within their lifespan.

Some terminology, like “master and slave” for IO between devices, did always used to make me really uncomfortable whenever I heard it. But the branch name for software was probably fine.

Git is really inefficient for large binary files because of the decentralization. SVN for media and Git for text-based files makes sense. Otherwise— I only used SVN briefly, and then fortunately only for media— But yeah, Git is probably better and more useful overall.

Wait, what? When did this even happen (in general)?

Ah, screw this. I’ll probably keep “master” in anything that currently has it, and the next time I start something I’ll just go back to calling it “trunk” even though I was too young at that point to actually call it trunk, but it makes the most sense for the organization flow.

Disk space is an issue… I’ve seen the OS take as much as 100 GB. But in a world of 2TB SSDs for $100, is that a big deal?

Yes? Storage used for the OS is space not used for projects, entertainment, docs, redundancy, snapshots, avoiding fragmentation (EXT4), etc. Money spent on SSDs is money not spent on going out, food, meeting people, basic needs, other hardware, etc.

I don’t see why NixOS would be any worse for the lifetime of a disk than other distros.

Untested, but I’d assume high space use combined with high update frequency, plus occasional builds-from-source and multiple simultaneous package versions, means more disk writes.

Biased, maybe, because manual GC means you see disk use tick up more than in other package managers, and also because I personally repeatedly rebuilt a custom gigabyte-sized Derivation dozens/hundreds of times. But I think it’s a reasonable point of caution.

I’ve only hit binary cache missed for packages I created, or where I changed build options.

Broken packages are, if anything, less of a problem [than] with Debian. Debian has lots of packages that are…not broken, but incomplete, requiring lots of manual config or whatever.

Maybe this is a NixPkgs vs NixOS thing. Also, using Nix mostly to supplement packages I hadn’t already installed through my distro probably meant I hit more fringe areas. But I’ve even encountered cache misses and failed builds for some pretty big Python libraries on certain commits.

Debian-based out-of-the-box functionality for stuff is indeed also Not Great, IIRC— Stable, but yeah, sometimes maybe a bit “incomplete”. Actually, Arch-based has worked well IME.

And on the flip side: you can change package build options! Neat!

But oh man…you should’ve seen how trivial it was to switch from PulseAudio to PipeWire (including Jack support etc), leaving no trace that Pulse was ever installed… Or switching from X to Wayland, on a system that I’ve been doing rolling updates on since 2017, all with a clear conscience… It’s beautiful.

Yeah. I personally don’t care about that stuff unless it directly impacts something I’m working on.

And that’s why I say Nix is a great tool for package management, but not something I’d personally want to use as an OS base. When you’re already elbow-deep in the plumbing anyway, Nix makes it way easier to swap components out. But when you just want to install and use an application, editing Nix configs feels like more work, and it’s so much easier to just pacman/yum/apt-get install firefox or whatever and get on with your day.

Plus, some specific red flags surrounding stability and interoperability:

1. ALSA is apparently hardcoded to just straight-up not work with a Nix root. Not sure how NixOS handles it, but in my specific use case, I had to symlinkJoin{paths=[alsa-lib alsa-plugins]} so they could find each other. Pretty sure it took a lot of strace -f -e trace=file and nix-locate for me to figure this one out, just to get sound working.

2. QtWebEngine/Chromium has to be run through some kind of sed -e "whatever.so" to “Patch library paths in Chromium sources” in order to even run, because it’s also hardcoded to just not work with a Nix root. IIRC, this one I figured out by just straight-up grepping on the compiled binaries after seeing the errors in strace or whereever. Seems a bit ridiculous, using a RegEx to patch a web browser when installing it so it can even run.

3. Binaries aren’t safe either, because they probably need patchelf to be able to run on Nix.

4. Flakes are apparently hosted as user repositories on a Microsoft-owned website, and can just randomly disappear sometimes.

5. Qt generally takes a ton of extra steps to be able to run on Nix. And have you actually ever opened the wrapper the Nix hooks generate to see what it’s actually doing? For one of my applications just now, you get a 43kb Bash script with apparently 581 assignments to just a handful of QT and XDG-related environment variables.

6. OpenGL doesn’t look safe either. Nix handles the drivers its own way, so to get OpenGL for Nix packages to work on other systems, you have to jump through some hoops. I assume the same amount of work in the opposite direction would be needed to use EG proprietary or statically compiled graphics applications on NixOS too.

7. Running precompiled binaries on Nix looks… Involved, as well. Sure, there’s tools to automate it. But that only hides the complexity, and adding an opaque dependency sorta defeats the entire purpose of configurability and composability IMO.

I’m sure most of these problems are “solved”, in the sense that NixOS implements workarounds that are the default when you install the affected derivations, and there are wrappers written for most other cases. But all of that adds maintenance, fragility, and complexity. It remarkably works well enough for userspace, but stuff like this still feels a bit house-of-cards-y for the basic OS and desktop. It’s not Nix’s fault, but so much of the work that goes into Nix seems to be just to force software that was never designed for it to run on it. Ultimately, the Linux FHS has momentum and adoption. Nix’s technical design might be compelling, but so are interoperability, stability, and simplicity.

The NixOS enthusiasts are doing a lot of technically interesting work, but I personally find the results of that work most useful outside the NixOS ecosystem. And I do think Nix as a package manager is really great. Ever since I’ve installed it, I’ve basically incorporated it as a major component or tool in every sizable software project I’ve since started. But I just personally wouldn’t want to base an entire OS on it.

I’m saying that’s a way I might personally consider going if I were to set up a new computer. Rock solid base that you can still get normal packages and binaries to run on without much hassle if needed, plus Nix with more up-to-date packages that you can customize however you find most useful.

Personally I have a mix of rolling/regular repos, AUR, Nix, Flatpak, and static binaries. They all have their uses, TBH.

Nix is great. But I don’t think I’d want to use it for a desktop OS base.

(Disk space/cycle life potential, binary cache misses, broken packages, and complete incompatibility with everything else. User error, TBH, but also stuff that’s not really a problem with other systems. Well worth it as a package manager, though.)