I'm not the author but I'll attempt to clear up the confusion based on what I've read.
Total.js's specific usage of "embedded" in this case means it includes 3000 lines[1] of pure Javascript that embeds the entire db engine source code into the project.
As for SQLite... as far as I can tell with Googling, there is no port of SQLite's C code to pure Javascript code that's maintained with popular support. (I found an old 2014 project[2][3] but it doesn't appear to be up-to-date.) Yes, there is a Javascript API[4] to SQLite but that's different from the SQLite engine itself being converted to 100% Javascript.
That's the nuance of "embedded" in Total.js' context. Yes, SQLite is an embedded db but nosql.js is even "more embedded" than that.
That said, whether Total.js embedded js db engine is as high performance and error-free compared to SQLite is unknown.
Genuine question, why does SQLite get so much hate? Is it because it's SQL, or it's embedded, or what? I've used it for a lot of projects where I have to move the server around a lot and it's super convenient
SQLite gets a lot of love when it's used for the right job.
It's not a replacement for a full-blown RDBMS. If you need a database for a multi-user application, you'll probably be better served by something like PostgreSQL. For single-user applications, however, it's quite fantastic.
Huh? Not sure what you mean but it's not intended as a "server database". It is however used a lot in production as an embedded DB in applications. E.g. I've seen SQLite in lots of Android apps.
