Exactly

To quote the post more specifically:

Even as our species destroys its only home, we assume that the solutions to climate change must lie in technology, without stopping to examine the role that this very attitude has played in the crisis.

This is so deeply ingrained in our social consciousness that, when there is a new impressive technology, we assume that it must be here to solve one of our big problems. As the AI hype quickens the pace of our ecological devastation, we’re so dazzled by the technology that there is actual debate in supposedly serious publications as to whether AI is going to save us from climate change, despite all evidence pointing to the contrary.

Yep, it’s definitely better to have as a default

It is with zfs, but I not with regular mount I think (at least not by default). It might depend on the filesystem though.

You can also do the following to prevent unwanted writes when something is not mounted at /mnt/thatdrive:

# make sure it is not mounted, fails if not mounted which is fine
umount /mnt/thatdrive

# make sure the mountpoint exists
mkdir -p /mnt/thatdrive

# make the directory immutable, which disallows writing to it (i.e. creating files inside it)
chattr +i /mnt/thatdrive

# test write to unmounted dir (should fail)
touch /mnt/thatdrive/myfile

# remount the drive (assumes it’s already listed in fstab)
mount /mnt/thatdrive

# test write to mounted dir (should succeed)
touch /mnt/thatdrive/myfile

# cleanup
rm /mnt/thatdrive/myfile

From man 1 chattr:

A file with the ‘i’ attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file, most of the file’s metadata can not be modified, and the file can not be opened in write mode.
Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

I do this to prevent exactly the situation you’ve encountered. Hope this helps!

Then you might like this tech blog: https://theluddite.org/#!post/ai-hype

If you don’t want spellchecking, then no. You can just change the keyboard layout.

If you do want spellchecking then yes, you will need to install some kind of language pack.

I’m not sure how libreoffice does it, but Firefox has different language packs for translating the UI and for spellchecking.

Are the extra dialects taking up too much space for you?

You’re welcome!

I’m sorry that I don’t have any advice for a specific laptop, but it seems others are helping with that already.

More memory and cores will help you with compiling and running your code.

Have you even read my comment?

It’s probably best to limit yourself to a used laptop.

Reading and writing code is nothing more than reading and writing text, and for that you don’t need a fancy gpu or screen.

What I would recommend you look for in a laptop is

• an SSD instead of an HDD
• more cpu cores (at least 4 cores)
• more memory (RAM) (at least 8GB, preferably 16GB+)

More memory and cores will help you with compiling and running your code.

And make sure you take regular backups! You never know when your disk will fail.

Also make sure to check linux compatibility before you buy. Laptops used to be a pain (10+ years ago), and it’s gotten a lot better, but it’s not always perfect. Just search for “[brand] [model] linux” or try to find the model on the archlinux wiki.

How did you install nixos? The labels for disks and partitions are usually set during creation.

If the KDE-spin installer did not need to reformat the disks (i.e. the partition sizes and formats didn’t change) it probably didn’t touch the partition labels.

You can change the label if it bothers you, just make sure fstab doesn’t use the old label :)

Happy hopping!

because bash isn’t always in /usr/bin/bash.

On macOS the version on /usr/bin/bash is very old (bash 3 I think?), so many users install a newer version with homebrew which ends up in PATH, which /usr/bin/env looks at.

Protip: I start every bash script with the following two lines:

#!/usr/bin/env bash
set -euo pipefail

set -e makes the script exit if any command (that’s not part of things like if-statements) exits with a non-zero exit code

set -u makes the script exit when it tries to use undefined variables

set -o pipefail will make the exit code of the pipeline have the rightmost non-zero exit status of the pipeline, instead of always the rightmost command.

You can also set up a wireguard VPN to run VNC over, that might be easier instead of using SSH tunnels.

Python development shouldn’t be that hard I think. You can just drop a shell.nix that imports your pyproject.toml and then you can run nix develop and have all your dependencies installed seamlessly with poetry2nix.

I’m using neovim so I can’t really help you with vscode, sorry.

Have you tried Erasing your darlings with NixOS?

There’s several pages on the arch wiki that should help:

Security - Screen lockers

Session Lock, specifically the xorg/wayland triggers and units sections

This sounds like a very specific question, what problem are you really trying to solve?

Logout before suspend/hibernate, or something else?

To expand a little on @Laser ‘s point 2:

In bash (and other programming languages) # is used at the start of the line to notate comments.

When writing percentages, you write the symbol after the number, e.g. 50%

That’s how I keep them apart, lol

Theres a section in the bash manual with these and a whole bunch of more expansion tricks.

One I find useful is

echo "${myvar@A}"

Check it out yourself: https://fedidb.org/software/lemmy