Awesome, love to see more Java devs pushing back on the spring madness.
In Db.java, with the write/update/delete locks, that mutate both in memory and on disk, is there not a bunch of race conditions there?
In Db.java, with the write/update/delete locks, that mutate both in memory and on disk, is there not a bunch of race conditions there?
1. update x in memory
2. delete x in memory
3. update fn checks for file on disk
4. delete x from disk
5. update x on disk
Is this not possible and you end up with different state in memory and on disk.