There’s a great reason for him not to: he can create a paid Lemmy client based on the code. Dude made way too much money on that piece of software to just give it away.
Definitely. I think once he picks himself up after the initial shock of it all, he’d probably give it a go if demand calls for it. He was very passionate about Apollo, I don’t think it’s going to die here and now, nor do I think he wants it to die.
Tapbots went through the same thing with Tweetbot -> Ivory.
It’s just really hard to give up labour of love projects, especially ones that you’ve invested the last decade into.
Eh, it depends. Sometimes a lot of the API is integrated with the components and adapting a new API means tearing apart the entire codebase.
For example, Lemmy-UI has an open PR to replace the websockets API with the HTTP one and it’s a huge change. And that’s just switching a type of API for the same backend – not switching the entire backend!
There’s a great reason for him not to: he can create a paid Lemmy client based on the code. Dude made way too much money on that piece of software to just give it away.
I love Mlem so far but if Apollo came back converted to Lemmy, i would at least try out both.
Definitely. I think once he picks himself up after the initial shock of it all, he’d probably give it a go if demand calls for it. He was very passionate about Apollo, I don’t think it’s going to die here and now, nor do I think he wants it to die.
Tapbots went through the same thing with Tweetbot -> Ivory. It’s just really hard to give up labour of love projects, especially ones that you’ve invested the last decade into.
It seems like a no-brainer to me. He’s already don the hard UI work, adapting to a new API is pretty trivial by comparison.
Eh, it depends. Sometimes a lot of the API is integrated with the components and adapting a new API means tearing apart the entire codebase.
For example, Lemmy-UI has an open PR to replace the websockets API with the HTTP one and it’s a huge change. And that’s just switching a type of API for the same backend – not switching the entire backend!