This exactly. I'm a software engineer and I'm itching to contribute to one of these systems, but I do not agree with some of the stuff I've seen posted by one of the developers of Lemmy. It just leaves a sour taste in my mouth about the whole thing.
C8H10N4O2
Couch gaming is key for me too. There are a lot of PC-only titles that interest me but don't compel me to sit at a computer to play. Being able to just tinker around in these games while watching TV is amazing. A great example of one of these types of games is Beam.ng Drive.
Does this only show if there is a known delay for all federated content, or is it a default warning that will always show?
One of the things I'm really enjoying about this jump to the fediverse is watching everyone try things to get a better understanding. Gives me first telephone call vibes. Lots of "does this work?" "HEY it does work!"
You're entirely correct, I was just commenting that Rust is also very memory safe in response to the first statement. As much as Rust interests me, I'm also in agreement that the problem it solves as a language isn't really a concern with modern web development.
These are garbage collected languages and come with the overhead of such a process. Rust has no GC process and instead relies on reference counters to statically track live memory.
That's interesting. What happens if a lemmy user replies to a beehaw user's comment from a lemmy instance? Does the beehaw user just never see it?
This makes sense. The only thing I put spinning disk storage in anymore are large storage arrays where part of the overall goal is to keep the disks cheap.
Wow this is neat!
How can I tell that a post is from another instance when browsing on Kbin? Just scanning the card for this thread, it isn't apparent that it's federated content.
Yeah, I'm probably going to bite the bullet and start working on Kbin too. I've avoided PHP for my entire career just by chance, so all I know are the memes and what I've read of (usually older) codebases. From what everyone says, modern PHP isn't really that bad, and from what I can tell when perusing the Kbin source, the implementation is pretty clean.