Why Python rather than something like Rust instead?<p>The phrase &quot;lightweight&quot; is thrown around, but the [requirements.txt](<a href="https:&#x2F;&#x2F;github.com&#x2F;Kinto&#x2F;kinto&#x2F;blob&#x2F;master&#x2F;requirements.txt" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Kinto&#x2F;kinto&#x2F;blob&#x2F;master&#x2F;requirements.txt</a>) is anything but lightweight and that&#x27;s before you consider carrying around python itself.<p>It seems like compiled version would be more efficient and much smaller.<p>EDIT:<p>Their FAQ seems to make this question even more interesting<p>&gt; Why did you chose to use Python rather than X?<p>&gt; We love Python because it’s a concise &amp; expressive language with powerful data structures &amp; easy to learn, so it was an obvious choice for the development team.<p>&gt; In addition, the Operations team at Mozilla is comfortable with deploying and managing Python applications in production.<p>&gt; However, Python is just an implementation detail per se. Kinto is defined by an HTTP protocol that could be implemented in any language.<p>If your end-user is hitting a HTTP API, then Python being &quot;easy to learn&quot; is a non-goal. Rust (or even JS + Node) is just as &quot;expressive&quot;. 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.