3 ms·
Your point being? It's been serving sqlite.org just fine for all this time. You seem to be making some pretty big assumptions about security here without actual
by Cthulhu_ 5y ago
Your point being? It's been serving sqlite.org just fine for all this time. You seem to be making some pretty big assumptions about security here without actually explaining what your specific concerns are.
- foxes 5y agoI think the original comment is partially a joke. Maybe there isn't specifically anything wrong with this, but there is the fact that it is written in C. Historically there is a good precedent of this being an issue. C does not guarantee correctness to the same level as more modern languages. If it was written in Haskell or Rust for example you could be more sure about correctness. I believe for something like this, correctness is fairly important. Not to mention you probably wont even lose speed. As for if the code is understandable, it is a 2600 lines of terse-ish C [0]. Do you really think about the entire blob at the same time? [0] https://sqlite.org/althttpd/file?name=althttpd.c https://sqlite.org/althttpd/file?name=althttpd.c
- kahlonel 5y agoPeople need to stop assuming that memory safety == functional safety. They are two very different things. Rust ensures memory safety, but it won't stop you from making logical mistakes. You can't be "sure about correctness" unless proven mathematically.
- foxes 5y agoI agree, but it is an extra level above c. Same with using a more advanced type system, more easily encoding problem constraints in that type system.