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
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.
It's not a question of the browser, it's the addon. There are separete APIs for local and synced storage (but same interface). Both browsers use the same main api (web extension).
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
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.
Jerboa doesn't have anything to do with it, it is the app you use to access the fediverse/lemmy.
Lemmy has upvotes, downvotes and the tally of those two. Karma is a step further; on reddit, every user has a total tally (Karma) as well, where all up/downvotes of every comment and post are added together as a "score" for the user. So people post popular stuff to get upvotes and thus have a higher score (which some subreddits required to post).
Have a friend who still does this. Every so often he'll notice that something is missing from a previous reinstall and we have to take a second to bring his system back on track
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