git-remote-aws VS linux

ff-only is the real git superpower.

a linear, immutable, series of commits in the only branch that is suffered to exist.

git, the good parts.

it also pairs well with a simplified remote[1].

1. https://github.com/nathants/git-remote-aws

use a network snitch[1] on desktop and mobile. The original slogan says it all: makes the invisible visible. i’d love to use a disk snitch too, but no exist yet afaik.

it’s interesting to see firefox or any other legitimate app i’m using make many unsolicited requests to weird domains. it feels good to interactively deny those connections.

make sure that cloud[2], which includes git hosts[3], are untrusted. unencrypted data should never hit remote. keys should never leave local.

consider the tradeoffs with online interactions. engaging with other humans in public on github and hackernews is likely worth. engaging in impassioned op-ed debate with bots on engagement monetization platforms like twitter or youtube is likely not.

1. https://github.com/nathants/mighty-snitch

2. https://cryptomator.org/

3. https://github.com/nathants/git-remote-aws

Those other flashy distros like mint and ubuntus are designed with rich people with very fresh machines in mind, they don't care if you have an AMDx4 or core2duo or even 32bit older machine. Even Mint and ubuntu people will tell you, if you have an old machine with little ram, use antiX. It still works very well with machines not even released yet, buy one in May 2024 and I "guaranty you" antiX will run fine. That's because kernels, even 6.1 have code for machines not yet released in the market, this is where manufacturers of new hardware send their prototypes to be tested, to kernel.org Some are even industrial machines we will never see in the market.

The memory_order_relaxed explanation on the kernel.org documentation heavily implies (never explicitly) that the direct memory load is implicit in the barrier(so by preventing it's reordering we are also forcing a LOAD from main), and that THIS specific barrier (relaxed) is what we NEED for these type of scenarios, so I am not entirely sure if a loadLoadFence() would prevent the hoisting... maybe it will prevent the reordering but not the hoisting/caching... in which case we would still have a visibility issue.

Are all versions of the kernel from kernel.org called mainline kernels or only 6.6-rc4 as shown in the picture?

Devuan is a fork of Debian GNU+Linux without systemd.

I built the dev env on Devuan GNU+Linux, a fork of Debian without systemd. It resembles my past trial on Artix Linux.

Devuan GNU+Linux is a fork of Debian without systemd and hence Snaps (Snapd). Even on it, it's easy to install Android Studio and start to develop Android mobile apps.

kernel.org