I'm seriously considering dropping sqlite3 entirely.

[antonreshetov]

I've reached the point where I'm seriously considering dropping sqlite3 entirely.

When I implemented the database layer in v4, I gave in to the general suggestion to switch from a simple JSON-based structure to sqlite3. In theory, it sounded like a good move — more scalable, reliable, etc. But in practice, it's been nothing but headaches: native module build issues, OS-specific errors, and random incompatibilities across environments.

For an app like massCode, a lightweight JSON-based store might actually make more sense — easier to maintain, portable, and no native dependencies.

I'm still thinking...

[Airr]

Honestly, I've had issues with v4 and it's sqlite3 db. Inconsistent across platforms (macOS, Windows, Linux). I've stayed on v3 because of that.

If going back to JSON is simpler, and 'just works', then I say go for it....

[hachther]

I try to upgrade to v4 but it didn't works because of SQLite issue. I was oblige to fallback on v3.

[bw-79]

I had do downgrade to v3 again, because random scripts are missing. The console is full of 422 errors (unprocessable entity).

[pa-0]

I loved the JSON approach. Not only does it make it easy to version control the database in git, but I am able to access the snippets from other programs and scripts using well-established, easy to use JSON libraries. That said, whatever makes maintaining the program easier and more enjoyable to you should trump anyone else's opinions, period.