4 ms·
> SQLite the project cannot switch languages, sadly. I'm sensible to the issues of tradeoffs (e.g. platform support which is a completely fair issue) and manpo
by masklinn 5y ago
> SQLite the project cannot switch languages, sadly.
I'm sensible to the issues of tradeoffs (e.g. platform support which is a completely fair issue) and manpower requirements and whatnot, but I don't see why it can not switch language. Converting libraries "inside out" has been done. Adding Rust support inside sqlite's build system and migrating modules is technically feasible (again, not opining on whether it would be worth it).
- Jtsummers 5y agoAdding Rust support would reduce (presently) the number of architectures and platforms that SQLite can target. That would greatly reduce its utility for a lot of customers. Once Rust supports the same variety of architectures that C presently supports this will become a non-issue, but that's unlikely to happen in the near term.
- masklinn 5y ago> Adding Rust support would reduce (presently) the number of architectures and platforms that SQLite can target. I mentioned that but i don't think that's the subject as it does not warrant such a drastic assertion that sqlite can not switch language.
- Jtsummers 5y agoOk, yes. SQLite can switch languages if the objective is to cutoff a large number of customers. Until Rust is well-supported on the variety of architectures that C is supported on, then that will be the result.
- justin66 5y ago> Until Rust is well-supported on the variety of architectures that C is supported on There's no particular reason to think that this will ever happen. SQLite runs on a lot of crazy stuff that Rust won't want to bother with.
- ecnahc515 5y agoFor rustc with llvm maybe, but there's projects to build a GCC backend for rustc, as well as projects to build a Rust frontend for GCC, both of which could solve this.
- nine_k 5y agoIt cannot "switch" languages in a way like "we stop development in C and switch to development in XYZ only; C-based code will only get security updates". If can switch the officially endorsed "primary" implementation, but only after an alternative implementation has been around for a long time and was battle-tested, all the while the original C implementation continued to exist and develop.
- masklinn 5y ago> It cannot "switch" languages in a way like "we stop development in C and switch to development in XYZ only; C-based code will only get security updates". At a purely technical level (ignoring issues of platform support and all) it pretty much can do that, actually: integrate XYZ into the build system, build new features in XYZ, start converting old features to XYZ, end up with an sqlite in XYZ.