What is the difference between Lemmy and kbin?
I'm not sure I completely understand the differences. Are they seperate or somehow connected?
Also I've read you can view kbin instances on Lemmy somehow. How does that work if they're two different things?
I'm using Liftoff is it somehow possible to view kbin instances on there?
You're viewing a single thread.
After reading these comments since I also wanted to know the differences, I have determined I am still "technologically challenged". I basically understood the punctuation.
You know you are old when you think there should be something like a "Technology and Federation for Dummies"!!
What part are you having trouble understanding?
Lemmy and Kbin basically just use the same protocol for exchanging information.
Both are similar in that they interpret and present that information in a way that looks similar to Reddit which is why you can see a community on Lemmy as a magazine on kbin and vice versa. In addition Kbin also can interpret it in a way that resembles twitter.
They both started with the protocol but the way they store, serve, and present the information from the protocol is different. For example, I think Kbin stores the information that shows who upvoted what, but I don't think Lemmy does.
The part about PHP and Rust, the differences of which is the better code?/foundation?
Most of my confusion lies with which instance is the better option as a whole. Is PHP not as reliable as Rust even thought Rust is new? I can not read code so I have no idea what any of that means.
Apologies for my ineptness. I would like to understand better.
A car can run on petrol, LPG, diesel, electricity or hydrogen. The result is still the same - a thing that moves when you push on the go pedal.
For almost everyone, it makes no practical difference which fuel makes the website work.
I disagree with that analogy. There's a very noticable difference between how the cars goes (and sounds) among those fuel types. They may all get you to your destination, but the experience is moderately different.
And maybe that actually makes it a good analogy. I'm not really sure.
I like that!! Thank you!
Ahhh. Well what's better overall is gonna be fairly subjective. Php in itself was made for serving web pages with dynamic content. It came first so there's a lot of resources to learn it, more established libraries, and there are more people who know how to code with it. Ernest having experience with PHP is likely a big contributor in his choice to use it
Rust is more efficient in terms of performance because it's purpose was to replace C, a language that is "close to hardware" (not really but for the purpose of this explanation just assume it). Meaning a coder can deal with things manually that PHP normally does for them. This is a double edged sword because manually doing things allows you to find efficiency in things that something like PHP would miss, but it also gives a lot more opportunities to mess something up.
So in terms of performance I would say
Perfectly Written Rust > PHP > Badly written Rust.
The subjective part comes from how well you think the Rust is coded in Lemmy. So just choose which one you like more.
Thank you!!
People should really mention the protocol used more often.
These services can work together because they support the 'ActivityPub' protocol. Any service that supports ActivityPub can communicate with any other service that does.
This is why we have protocols.
Lemmy stores who upvoted what but does not make it easily available to everyone like kbin does - you can set up a Lemmy instance to grab upvoted and read them from the DB if you are so inclined, or you could just look at kbin to see the same info
Let's say the fediverse is texting, Lemmy is Android, and kbin is iOS. They can text each other, despite being made by different companies.
Thank you. Putting explanations in layman's terms is very helpful!! I have received a few replies to help "dumb it down"!!!