Comment by pessimizer
1 day ago
Actually, every point was right and the data model is terrible. I've been using it for years. The other commenter just mentioned a list of things that the software does do and basically said "isn't that good enough for you" a bunch of times. No, it's not. Anki's concepts of flashcards, and how it stores and manipulates them, are horrible.
It's hard to do many, many things in Anki that should be trivial, impossible to do many, many things that should be possible, and the things you can do involve the types of queries being run over your entire collection that causes the app to slow to a crawl after you add about a dozen decks. And in general: I can adjust far too many things that I don't even care to adjust and probably shouldn't be adjusting, and things that should be trivial to do are impossible.
It's bad. Ankidroid is a little better, but they're also stuck with the data model.
That’s because the default model is designed for the general user. If you sat down and really worked with the documentation, you would realize you shouldn’t be using decks or collections for management you should be using tags. Decks and collections are a different abstraction for different purposes.
I’m in medical school which has basically mastered Anki. The AnKing deck, used by over a million medical students, has over 35,000 cards, cross-tagged by numerous study resources that exists on a single “deck” which receives regular updates. I regularly run basically instant queries on over 40,000+ cards.
Medical school Anki has basically mastered this workflow and the original commenters complaints are completely wrong/come from a misunderstanding of Anki’s data model.
To be put simply, ignoring subdecks, filtered decks, cards vs notes, etc.: cards can only belong to one deck, but can have multiple tags. What exactly do you want to see differently in the data model?