I desperately want a RiF clone for interacting with Lemmy. If RiF does actually shut down at the end of the month, I really hope talklittle open-sources it.
I’ve been a RiF diehard for about a decade, but I’ll definitely give Sync for Lemmy a try when it’s available.
What I’m really interested in is this. If this gets completed, theoretically any existing third-party reddit app could update the API URL it hits and their app would pretty much “just work” with Lemmy, they’d just need to add an option for the user to input their home instance’s URL and their credentials. It was started by @derivator
The one thing that takes a bit to get used to is the borrow checker. Advice there is don’t fight it. Trust the compiler to tell you your code is wrong. Once you understand the ownership/borrowing rules, it’s honestly just a joy to code in. Static typing protects you from the inevitable mess that every large python project becomes, and the borrow checker gives you the comfort and safety you’ve come to expect from memory safe languages without the overhead of a garbage collector.
I desperately want a RiF clone for interacting with Lemmy. If RiF does actually shut down at the end of the month, I really hope talklittle open-sources it.
@tool @sirvesa if its any reassurance, Sync is coming to Lemmy
I’ve been a RiF diehard for about a decade, but I’ll definitely give Sync for Lemmy a try when it’s available.
What I’m really interested in is this. If this gets completed, theoretically any existing third-party reddit app could update the API URL it hits and their app would pretty much “just work” with Lemmy, they’d just need to add an option for the user to input their home instance’s URL and their credentials. It was started by @derivator
@tool @derivator that could be awesome, any way to bring over the apps that made reddit great
Still working on this, help is welcome :)
Unfortunately I don’t know shit about Rust. I use Python/PowerShell/Bash/some C#/etc daily for my job, but I haven’t touched Rust at all.
What would you say the learning curve would be based on the languages I’ve worked in?
The one thing that takes a bit to get used to is the borrow checker. Advice there is don’t fight it. Trust the compiler to tell you your code is wrong. Once you understand the ownership/borrowing rules, it’s honestly just a joy to code in. Static typing protects you from the inevitable mess that every large python project becomes, and the borrow checker gives you the comfort and safety you’ve come to expect from memory safe languages without the overhead of a garbage collector.
Ok. I’ll give it a try some time this weekend, thanks for the tip. Hopefully I can contribute in the future.