mkanki VS sql.js

It is possible languages that do no share roots. You also need to create a different environment for studying each language. I am studying Korean and Chinese st the same time. And even though they share the some words and the Characters they are essentially separate languages because Standard Mandarin was "redesigned" to be closer to English Grammer while Korean and Japanese follow "closer" to ancient Chinese. Due to the way I am studying each language, I almost never get confused. I will caveat this with I had been studying Korean for 7 to 8 months before starting Standard Mandarin so I had a foundation that was somewhat solid. I am using Mandarin Blueprint and Anki for Mandarin and for Korean LingQ, Memrise, Anki and supplementing it with Talk to Me in Korean.

If its flashcards you're looking for download Anki. The PC version has more options than mobile. Though the learning curve is a bit steep. https://apps.ankiweb.net/

I recommend this app called Anki that does flashcards and the spaced repetition for you :)

Ask your lecturer/teacher what you need to remember, then go to r/medicalschoolanki for advice on how to use Anki, don't waste your time with any other app that promises you the world and charges you money.

For vocab revision, I use Anki - I have a general vocab list and a verbs one, because Greek verbs are hell and I need all the extra help I can get!

Anki: https://apps.ankiweb.net/

Download Anki for desktop (link)

Hi HN! A friend and I were inspired by projects like https://github.com/sql-js/sql.js and the idea of querying files served over CDN with HTTP range requests. We started thinking: what would a database that was specifically designed for this type of use case look like? So we started building one, and we landed on a functional prototype that we're pretty proud of!

With our prototype, Appendable, we're able to serve and query large (GB+) datasets by hosting them on a static file host like Amazon S3 or Cloudflare R2 without running a separate server and worrying about things like tail latency, replication, and connection pooling -- all that is handled for us by the file hoster.

Additionally, one tenet that we have been following is Appendable won't touch your underlying data, so your jsonl file is preserved and we point at that data instead of consuming it into an Appendable-specific file format. This keeps your data yours and makes it easy to introspect the data: just open it up with your favorite editor aka vim.

We're curious what you think, we're excited to build this out further to get the performance even better and add features like pubsub. Everything is open source at https://github.com/kevmo314/appendable.

Kevin and Matthew

My project is powered by sql.js, I recommend checking that out if you're interested - https://github.com/sql-js/sql.js/

Maybe you can try to use some SQL database compiled as Web Assembly Modules? Like this one for example: https://github.com/sql-js/sql.js

If you want to have persistence, then I would go with a database like Dexie, as it uses IndexedDB and has transactions. If you just want something that's in memory, you could look at Sql.js or something simple like lowdb.

not necessarily. you can host an html/js/sqlite site on github pages for free. json -> sqlite3 js -> sql

Link: https://sql.js.org

Does it work with really large files? Like, >100mb or so. I was considering making something similar but with sqlite.js [1], but the problem with it is that it loads everything in memory, so I wasn't entirely sure how it will deal with larger workloads.

[1]: https://sql.js.org/#/