zlacker

>>thomas+(OP)
I'm happy to see others in the space, but I wish Anki competitors would implement a decent 'import from Anki' feature. Otherwise, I think most existing users of SRS are unlikely to switch (because we use Anki and have thousands of cards there already).

The data format of Anki is a bit complicated but at least it's SQLite. I've seen a ton of shared decks and resources on ankiweb, but it's true you can't easily put them on GitHub.

>>yellow+Am
I think that many devs missed the fact that Anki went through major rewrite and all of its business logic/its brain/api are now contained in few rust crates. They're a pleasure to work with and it's very easy to write alternative frontends (just finished one). You don't have to import anything because you can just use the same db, and cards as Anki.

>>tvshtr+7W
This feels as if it deserves a write up, did not know that they migrated from Python to a primarily Rust backend. Would love to know the why/what from the team.

(Anecdotally, Anki has seen a huge quality increase in the past couple of years.)

>>pityJu+xJ1
The Rust backend code is shared between all platforms (Desktop, Android, iOS and Web). This wasn't feasible with the Python code.

From an Android (AnkiDroid) perspective, it's allowed us to remove most of our code which was manually ported from the Python backend, with guaranteed 1:1 compatibility with upstream.

We've moved from being years behind upstream to being able to release in tandem with the Desktop app.

We also migrated to common screens written in Svelte, to reduce the maintenance burden of UI changes for screens with high churn (Deck Options being the primary example).