i can chime in with some actual experience!

my current problems with KDE are

• the greeter only accepts my password on the secondary monitor
• the compositor shuts down whenever something uses the GPU even though the setting is off
• my primary desktop randomly shunts itself to the right, plopping on top of the desktop on the secondary display and leaving a big black void on half my primary until plasmashell is restarted
• my panels keep collapsing their content down to the width of a single pixel until i resize them
• Wayland just crashloops and is completely unusable (no, i don’t have an nvidia card)
• i still can’t get the acrylic transparency to work :(

and what’s fun about this is, the issues are so intermittent and random that i never know what i’m going to get on a given day!

no that’s literally the description of the other axis…

as i understand it, the money goes to the foundation, and it’s the corporation that develops the browser. so it’s probably not strictly forbidden, but it does imply that the money is not for browser development.

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.

it’s when you dodge all the shots

the Chilluminati podcast episode on him talks about how he had a really squeaky voice. like, imagine if mickey mouse could karate chop you.

also, he is still alive.

in the health sector specifically, IT is a mess because you can’t stop people from working or there will be deaths. one thing you should take away from this is that their jobs are important and it is crucial that they can do them. it is your job to support them; anything that stops them doing their job or makes it take longer, even once, is dangerous. improving infra for its own sake is not a good idea because it comes at the risk of peoples lives. the details don’t matter in the face of that.

if this stresses you out, you can absolutely change jobs. i did.

if you think you can work within those parameters, and you think you can find ways to improve the system in-place while mitigating the risks, then you will be highly respected.

hypothesis: the last reply is usually left there to stop hundreds of people replying that exact same thing below.

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.

mozilla takes donations, but they don’t fund Firefox development with that money. that’s usually what people have against it.

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.

tariffs

my dude, just seeing the text is too much effort.

me, watching a friend play a game (that i play) for the first time

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.