i’ve seen something like this before, where the kernel holds the file handle open for the process so that it thinks the file is still there. i think it’s related to how the program closes the file but i don’t remember the details. restarting qbittorent will most likely fix it.
my dude, just seeing the text is too much effort.
your reaction makes me more confident that this may turn into something interesting :)
i take it then that files must have some ownership information associated with them, to distinguish the author from a relay node? or is that just a private key.
i’m interested in the dynamic linking, what mechanism is used to stop situations like left-pad or the pypi incident where a file is removed replaced with a malicious alternative?
i mean, that is the difference between interpreted and compiled.
if the container doesn’t work though, that means it is broken and should be fixed. the point of them is literally to be plug-n-play. that would be like distributing a go binary with a segfault in main.
if I’m reading this right, it’s a bit like ipfs+dht. is this a content-addressable system?
anyway, you should probably have demos of
thoughts:
also, please convert the whitepaper to a format that is actually readable. rtf? really?
that’s posturing if anything. if you’re an experienced developer it takes fully 10 minutes with either system. and if you’re not interested in modifying it, just use a container image.
the only case where i would agree with you is when i have to modify LD_LIBRARY_PATH to get things to run…
such a strange interpretation. i’ve been working in go for over 10 years now, and i love it. but the notion that you can “just find the same program but built in a different language” doesn’t make sense at all.
like, if you’re annoyed with pandoc being written in haskell and clogging up your system dependencies, you can’t just “find another pandoc”. there’s nothing like it. same thing with curl, or xonsh, or thingsboard.
such a weird take.
it’s not though. op has issues installing programs built in python. suggesting they rebuild those programs in go is 100% an apples to meatballs comparison, and way off topic.
this is not about offense! nobody is offended. but if you ask me for help with an apple pie and i tell you to make meatballs… it’s a confusing lack of relevance.
everyone focuses on the tooling, not many are focusing on the reason: python is extremely dynamic. like, magic dynamic you can modify a module halfway through an import, you can replace class attributes and automatically propagate to instances, you can decompile the bytecode while it’s running.
combine this with the fact that it’s installed by default and used basically everywhere and you get an environment that needs to be carefully managed for the sake of the system.
js has this packaging system down pat, but it has the advantage that it got mainstream in a sandboxed isolated environment before it started leaking out into the system. python was in there from the beginning, and every change breaks someone’s workflow.
the closest language to look at for packaging is probably lua, which has similar issues. however since lua is usually not a standalone application platform it’s not a big deal there.
it’s also not at all relevant. go is great, but this is about python.
shit of feceus. it was right there, man…
it’s a standout of its genre, definitely. i thoroughly enjoyed my time with it. i have no nostalgia for the apple ][ style it emulates but it really serves the art direction brilliantly.
i had a discussion with a friend about the obra dinn a few weeks ago. i told him how i enjoyed the “hidden in plain sight” fact that the letter you get with the pocket watch is signed “Henry Evans” and he basically lit up. turns out he had been stuck on the two ladies that were passengers, and he connected in real-time what must have happened to them just because i mentioned the name. i love that it’s the sort of game that gives you epiphanies.
interesting perspective, because while i completed subnautica i got tired of pacific drive. mainly because subnautica is open and static. you can make your way around a problem area meaning you get by with less time scavenging, while pacific drive is relentless and random, and will absolutely fuck you up if you don’t have the right ingredients. it sells itself on its driving aesthetic, but you spend so little time actually in the car that it seems pointless. it’s all just digging through trash and crafting.
the x is for crossover, i think
at least it’s not on top of js!
mozilla takes donations, but they don’t fund Firefox development with that money. that’s usually what people have against it.