don't know why nobody stated this but space age is basically five times larger than the base game. they've announced that even though the game is coming to switch, space age is not since it has much higher requirements.
yeah one thing we couldn't fix before losing interest was eventual consistency and authority. files would sort of flicker in and out while state was being propagated. i dread to think what kind of bandwidth use that thing would have when sharing large files.
i don't know of a single town here that has overhead power lines in populated areas. those are for long-distance transmission only.
or, okay, i know of one. but that's because there's a steel mill and a hydropower plant there, and you don't wan to bury lines that carry that around of energy.
it was nothing official, just a toy file sharing thing using the chord dht algorithm. it consisted of a single binary that you fed with a directory and the IP of an extant member, and it would sync everything on the network into that directory.
good point, ruby is a good comparison. although, ruby is very different under the hood. it's magically dynamic in a completely different way, and it also never really got the penetration on the system level that python did.
none of this is to take away from the fact that python packaging is bad. i know how to work it because i've been programming in python for 14 years, but trying to teach people makes the problem obvious. and yet.
sure, do that. and good luck with this, i did something similar for a project once and as usual its those last 5% that are going to cost you 90% of the time.
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.
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
large files (like a Linux disk image), to demonstrate consistency in transfer.
Video stream, to demonstrate performance and low latency.
multiple files shared with many peers at once, to demonstrate scalability
sharing with low bandwidth and high latency, to demonstrate possible mobile use cases.
thoughts:
the logo is very close to wireguard's.
if the data is stored on peers, that means there must always be people with free storage online for it to work? how much storage is needed? is that data in plaintext? could a bad actor push illegal content to peers without them knowing?
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.
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.
don't know why nobody stated this but space age is basically five times larger than the base game. they've announced that even though the game is coming to switch, space age is not since it has much higher requirements.
it's not a dlc, it's a proper expansion.