JATtho

Sure it's terrifying, but you can start a sparky plasma show in a resilient enough container and keep it going for hours and the microwave won't break. (except maybe overheat.) The microwave will be fine as long as the arcs don't reach the waveguide cover. (which would risk burning/shorting the magnetron.)

I have done the microwave grape plasma trick myself and started an arc in a microwave. The current between the two objects goes through a very narrow point, which is enough vaporize the contact point to plasma. This then can grow as the microwave continues to pump more energy into the spark.

hardmode: I did a fresh install on a HDD that is on verge of being dead. Every-time this thing boots it's a miracle. Somehow dd blanking the disk, plenty of smartctl offline disk surface scans and finally putting btrfs with data in DUP profile resurrected the HDD. I have run btrfs scrub daily or else the os install may bitrot and well.. expire. :D

Edit: Todays catch, I was too late and now I have fix 3 files:

Error summary:    read=112
  Corrected:      109
  Uncorrectable:  3
  Unverified:     0

Two new hobbies to keep me in the reality^tm^.

So this is it. The enshittification has reached slowlorris levels.

I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.

Oh, this is a good one.

No mention of KDevelop? ;__;

I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I'm been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)

The \EFI\BOOT\BOOTX64.EFI is the only file the UEFI standard says it is required automatically lookup from an EFI system partition. There can many EFI partitions but the UEFI is only required to find a single file per such a partition.

efibootmgr -u can show all bios auto created boot entries (don't touch those, the bios can/will reset them at whim) and the manually created entries that don't launch a BOOTX64.EFI named file.

I intended this an sarcastic example; I think it's worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main() doesn't exist if you try import this as an module.

Btw, ld.so is a symlink to ld-linux-x86-64.so.2 at least on my system. It is an statically linked executable. The ld.so is, in simpler words, an interpreter for the ELF format and you can run it:

ld.so --help

Entry point address: 0x1d780

Which seems to be contained in the only executable ~~section~~ segment of ld.so

LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
     0x0000000000028bb5 0x0000000000028bb5  R E    0x1000

Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text section.

I would put my code in a def main(), so that the local names don't escape into the module scope:

if __name__ == '__main__':
    def main():
        print('/s')
    main()

(I didn't see this one yet here.)

I do this, and I have a "graveyard log" file where I paste my discarded posts and replies.