Programming and reading.
The main reason for Ubuntu against Debian is the packages. For Ubuntu, they’re much newer, and with PPAs (launchpad.net), you can often get more and/or newer packages built by other users. For debian, good luck, you’re stuck with old packages (which is the intent of Debian stable, but not nice as a user, that’s for server)
This would likely only hurt the end user. Many use chromium-based browsers, so you’re just driving those away.
You can detect Firefox, so you can do a superficial block in JS, but lemmy is such a simple site that you’d find it hard to find areas where there’s actual differences between the browsers, those usually only come from complex pages like video calling
Immutable distros aren’t immutable in the home folder though, they would be unusable otherwise, so that doesn’t solve OPs problem of dotfiles/personal files (I know nixOS tries to get rid of dotfiles, but in my experience that almost never works, it’s only helpful for replacing config files in /etc)
It’sintended to be used when the cookies are actually required for the app to work. For example, to preserve your login, you need a cookie, no way around. Unfortunately, as mentioned by others, it’s often abused
Usually we don’t distinguish between many2one and one2many, since it’s the same just viewed from the other entity.
There is one more class though, which is one2one. That is, the entities have a direct relationship. Sometimes this also includes the case where you have zero or one, i.e. the relation is optional on one side. This can be accomplished with an FK plus unique constraint or by merging the tables.
streaming small commits straight into the trunk
The image even calls it like that
Some things don’t have good CI/tests, so it doesn’t make sense to include the build step, especially on a small team where we trust each other. But yes, it’s not good practice, and we don’t do this on every project, but sometimes it’s necessary to adjust the flow to the specific project
With git. Every time we start work, we pull. After every commit, we push (and pull/merge/rebase) if necessary.
We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it’s “just” a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.
You can set the initial value directly in /etc/environment, did you check that? It could also be set only for your user, so it might be in ~/.profile, ~/.bashrc or ~/.bash_profile` (or the rc file for your shell if you’re not using the default bash).
Edit: I suppose you could also have added a startup script in /etc/init/ or /etc/init.d/, or in /etc/rc.local
I use it for everything, because I connected my external monitors through the eGPU. https://wiki.archlinux.org/title/PRIME has a few methods for running only selected applications via the eGPU, but I haven’t tried them. Edit: See also https://wiki.archlinux.org/title/External_GPU#Xorg for eGPU specific setups.
Can confirm, I’m using a dock (from Razor) daily without problems. Hot switching doesn’t work though, you need to restart X/your display manager to connect or disconnect the eGPU. I’d recommend the gswitch utility to configure the graphics card to be used (on X11). Haven’t tested much on Wayland, but I know that at least Gnome (Wayland only) has trouble mixing eGPU and the internal display if that is important.
If you need finer control than recursive
chmod(see other replies), you can also usefindto match precisely which files/folders you want and use the-execparameter to runchmodon those