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.

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.

Holy hell, thats rough. :D

True Arch: you write the image to the usb stick yourself, boot it on bare hardware, and don’t use archinstall. This is the minimum requirement BTW. If you use archinstall you can only use “btw” in lowercase. /s

Do you know about ortho/para-H₂O? It only gets weirder.

This might just push my fear of targeted ads enough to give in to my idea of a nearly soundproof box for my phone when I’m not using it. :(

They got credited for scientific research: link

I’ll just comment about one thing that keeps popping up in the discussions: grid-level storage. There is no such thing yet really that would last a full day cycle, and the 100MW or so units we are building are mostly for frequency stabilization and for buying enough time to turn on a base-load plant when the renewables drop out. I’m not arguing against storage - it is absolutely needed.

The problem is the scale, which people don’t seem to get. Largest amount of energy we can currently repeatedly store and release is with pumped hydro, and the locations where this is possible are few and far between. Once the batteries reach this level-of-capacity, then we have a possibility to use them as grid-level storage that lasts a few days instead of hours.

Send it through the earth, you can reduce it theoretically to 42.5ms

This isn’t as ridiculous as it sounds and you just need a neutrino-beam… which has a horrible bandwidth (of 0.1 bits/s) plus the ridiculous upfront cost of running two particle-accelerators for a full-duplex link. (Google it up, this exists.)

My favorite so far:

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

Now,

R E A S S E M B L E

it again.

I recently deleted my +10y (cant remember anymore how old it was) old account. I had not logged in with it since the first exodus.

In my time, I started from the old reddit, saw the changes to more modern UI twice. I “collaborated” with the pixel art canvas event. (twice?) (last was fullout among us dithering) And finally saw the full revolt against spez that ended my journey there. (plus the complete enshittification of the reddit app)

I once wrote bind_front() and move_only_function likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.

On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.