There are dozens of us. Dozens!

that’s already in the cheatsheet

Nice, mypath.open() is a more semantic alternative to open(my path)

I’ve seen plenty of grad student code, abundance of OOP concepts was never an issue. Complete lack of any structure on the other hand…

Tbh if the average grad school student overused object oriented stuff they would produce vastly better code than the status quo.

man touch

yeah, discord the the true black hole of information

basically sums up the opencv experience in Python.

great lib, very mediocre Python wrapper.

types are always ignored at runtime, they’re only useful when developing

at least on my part, what they get from channel memberships (a whopping 30%) I’m sure exceeds the amount in ad revenue they lose from me

what you and I quoted comes from the article, and it’s true

a problem that is documented is obviously a feature

The takeaway is to not use forks if there are changes you want to keep private.

I don’t think you can create private forks from public repos (the fork is public upon creation). This is more like the opposite:

If there’s a private repo that is forked and the fork is made public, further changes to that original private repo become public too, despite the repo remaining private and the fork not being synced.

the article explains it

I have a ~40TB HDD array and jellyfin is super fast

I hope it is. But OP has a single drive.

thanks, i hate it

User-Agent: bender
Disallow: /my_shiny_metal_ass

wat

why would you want to nuke your installed cli apps on every boot with a tmpfs