Why Python rather than something like Rust instead? The phrase "lightweight" is thrown around, but the [requirements.txt](https://github.com/Kinto/kinto/blob/m

Why Python rather than something like Rust instead? The phrase "lightweight" is thrown around, but the [requirements.txt](https://github.com/Kinto/kinto/blob/master/requirements.txt https://github.com/Kinto/kinto/blob/master/requirements.txt) is anything but lightweight and that's before you consider carrying around python itself. It seems like compiled version would be more efficient and much smaller. EDIT: Their FAQ seems to make this question even more interesting > Why did you chose to use Python rather than X? > We love Python because it’s a concise & expressive language with powerful data structures & easy to learn, so it was an obvious choice for the development team. > In addition, the Operations team at Mozilla is comfortable with deploying and managing Python applications in production. > However, Python is just an implementation detail per se. Kinto is defined by an HTTP protocol that could be implemented in any language. If your end-user is hitting a HTTP API, then Python being "easy to learn" is a non-goal. Rust (or even JS + Node) is just as "expressive". This really makes it sound like their team is inexperienced with DB design (not very confidence inspiring). I find it equally mystifying that operations would dictate python rather than whatever language the team thought would be best.