3 ms·
At this point you're arguing against a lot of things I've never said. Obviously an alternative to SQLite will have to be compelling enough to motivate its use i
by pcwalton 11y ago
At this point you're arguing against a lot of things I've never said. Obviously an alternative to SQLite will have to be compelling enough to motivate its use in ways that likely exceed just memory safety concerns. That is true of any proposed replacement for any piece of software. The point is simply that, if you want to write a SQLite alternative, Rust is a reasonable language to write it in.
- coldtea 11y ago>At this point you're arguing against a lot of things I've never said. Yeah, didn't say you said those. But since I started this subthread, I'm merely expanding and explaining further the thigs I said initially. >The point is simply that, if you want to write a SQLite alternative, Rust is a reasonable language to write it in. Oh, on that I agree. I was mainly questioning the need to rewrite in the first place (and especially for this particular software, being an embedded db et al), not whether Rust as a language is a good choice to do so. That said, the less mature ecosystem/toolchain etc, is still an issue for some projects that would still benefit from Rust -- e.g. for somebody used to work with VS C++, etc.