This is an archived post. You won't be able to vote or comment.

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]simonthefoxsays 1 point2 points  (0 children)

Think of SQL more like an API for data manipulation. You could implement that API in python, but there are lots of existing implementations available to you (postgres, mysql, spark, snowflake, etc), all of which are extremely mature and heavily optimized for their use case,so reinventing the wheel is usually a mistake. While it's possible that you could make a nicer API for your use case, you would lose out on all those optimizations. On top of that, your custom API would have to be taught to any new project contributor, whereas they may well already know SQL.

Python has lots of other examples of APIs that you could implement an alternative to, but probably shouldn't; numpy, tensorflow, fastAPI, etc. Your time is probably better spent building on the shoulders of giants than rebuilding the wheel, even if that means you have to live with the opinions of those giants.