4 ms·

This is a C vs Java argument. There are people who prefer each. > when you get it right, there's nothing to second guess Given the topic is "how to corrupt yo

This is a C vs Java argument. There are people who prefer each. > when you get it right, there's nothing to second guess Given the topic is "how to corrupt your db file," does that mean they didn't get it right yet? Or that the underlying platform prevents them from getting it right?

bayindirh 4y ago
> This is a C vs Java argument. There are people who prefer each. As a person who've developed sizeable projects with both, you hit the nail on the head (and yes, Java can do amazing things in the foot gun department, believe me). However, my favorite language duo is C/C++ at the end of the day. > Given the topic is "how to corrupt your db file," does that mean they didn't get it right yet? This means you (as the developer) has a misunderstanding between you and the system. The article contains a very large swath of problems from hard to understand implementations (e.g. locks), to hardware which doesn't listen you to bugs in SQLite itself. So, in the article there are a lot of cross-platform bad practices which one's warned about. Shrinking this to "POSIX is bad!" is just wrong. This is what I'm trying to point out.