redjard

It’s nice but a little janky. For me for example I have to hit ctrl+C twice after closing a session where I started a kde program.

I still use X forwarding.
It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.

It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.

Do they work with split apps yet?

I could do a script if I knew what I was gonna do ahead of time, or would write one later if I was gonna do it more often.

A variable in the shell is fine, but I still have to skip over it to change the first command, it still breaks up the flow a bit more than not having that "$file" in there at all.
Also if I interrupt the work (or in this case have to let it run for a while), or if I wanna share this with others for whatever reason, I don’t have to hunt for the variable definition, and don’t run any risk of fetching the wrong one if I changed it. Getting by without variables makes the command self-contained.

And it still maintains the flow of left to right, it’s simply easier to take the tiny well-known packet of cat file and from that point pipe the information ever rightwards, than to see a tail, then read the options, and only then see the far more important start of where the information comes from, to the continue on with the next processing step.
Any procedural language is always as left to right as possible.

If you really want to avoid the cat, I have yet another different option for you:
< /dev/nvme0n1 strings | grep -n "text I remember"
< /dev/nvme0n1 tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
< /dev/nvme0n1 tail -c -123456789012 | head -c 3000 > filerec

This ofc you can again extend with ${infile} and ${recfile} if the context makes it appropriate.

It makes the command easier to edit here. Put the various forms across my use next to each other and it becomes apparent:

cat /dev/nvme0n1 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

compare that to

strings /dev/nvme0n1 | grep -n "text I remember"
tail /dev/nvme0n1 -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
tail /dev/nvme0n1 -c -123456789012 | head -c 3000 > filerec

where I have to weave the long and visually distracting partition name between the active parts of the command.
The cat here is a result of experiencing what happens when not using it.

Worse, some commands take input file arguments in weird ways or only allow them after the options, so when taking that into account the generic style people use becomes

strings /dev/nvme0n1 | grep -n "text I remember"
tail -c -100000000000 /dev/nvme0n1 | head -c 50000000000 | strings | grep -n "text I remember"
tail -c -123456789012 /dev/nvme0n1 | head -c 3000 > filerec

This is what I’d expect to run across in the wild, and also for example what ai spits out when asked how to do this. You’ll take my stylistic cats over my dead body

Oh right I misunderstood.
I didn’t do that because I was planning to switch out strings in that line. First inserting the tail and head before it to hone in on the position, then removing it entirely to not delete “non-string” parts of my file like empty newlines.

cat /dev/nvme0n1 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"
cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

This would be the loose chain of commands I went through, editing one into the next. It’s nice keeping the “constants” like the drive device that are hard to type static. That way mentally for me the command starts only after the first pipe.

I don’t like to use < in combination with pipes, I find it harder to read. One is left to right the other right to left, and < is also just plain weird in its specifics.
cat is a stylistic choice avoiding needless notational complexity

Last time I deleted a plaintext file I just grepped for it.
cat /dev/nvme0n1 | strings | grep -n "text I remember"

Had to hone in on the location with head -c and tail -c after I found it, then simply did a cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec and trimmed the last filesystem garbage from the ends manually.

Efi spec states it must be safe to delete all variables. It’s only motherboards not adhering to the spec that are affected, effectively faulty hardware.
If you do this on a mb from that era chances are nothing will happen, and if something does happen chances are it is recoverable. You’d have to have some truly bad luck on your choice of mb to have it be permanently bricked by that.

Oh my I must have recited it wrong from memory, my bad

Yep, exact copy of the first 35 lines from the 100,000 Digits of Pi website, the spaces are still in

Sugar beet seeds are produced via wind pollination in dedicated very compact setups. They plant strips of male and female plants with controlled distances.
As far as I can tell no pollinators are involved anywhere in the sugar beet industry.

Then just say the world has ended and remove the burger.

Oh you want the code not rendered into html!
Drops the code in javascript when it is received from the backend.

genkernel is basically deprecated. You can use distkernel and supply your own config or config mods.

Export the apk via adb and then install it from the file on future devices?

Yeah, on some fundamental level.
Most linux distros would be very moddable repairable off-the-shelf cars. LFS would be your diy project with various guides. And gentoo would be a parts garage with their own guides and precompiled kits of components, so you can either follow those sets and build a more off-the-shelf car or diverge at any point for any section and run wild. But also you can still use the machine shop of the store and they offer to custom build some consumables for you and keep shipping them.

You could use njal.la, who charge a flat 15$ without deceptive schemes and actually protect your privacy properly too.
To be fair namecheap legally can’t do what njalla does since namecheap is a primary registrar and njalla secondary.

In terms of activism I’d think both getting the cheapest option and donating 8$ a year to the eff or a similar group directly, or taking a njalla domain and donating 3$, would be cheaper than namecheap and also more effective at defending internet freedom.

In the underlying system there is no difference. A renewal is just a transfer/registration leaving the data unchanged.
All cost the same and add 1 year of lifetime to the domain.
Any other pricing is invented by that specific registrar and doesn’t reflect actual costs.

What a ripoff, .com has always been about 10$. The renewal being somehow more expensive than a new registration, while in actuality there is no difference in the process, really makes it obvious they charge what they think people will fall for.

$7.85 per year in 2012. $8.39 in 2021, $8.97 in 2022, and $9.59 in 2023, $10.26 in 2024, increases always in september.

Transfers, registrations, and renewals all cost the same and all charge the domain by 1 year. You can charge at any time for I think up to 10 years. Any registrar not passing that system on is being deceptive.

They aren’t even roping in people with prices below cost, they charge you a reasonable fee for the first year and then somehow bank on people not switching. Maybe they make the process really painful?

Either way why would anyone use them?