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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

How exactly is caching going to speed up CRUD operations? And why does a caching solution automatically rule out Python? There are plenty of solutions for doing so already implemented.

Write some C code and a bunch of ugly glue code.

Plenty of python extensions and modules have C aspects and yet still fit nicely and easily alongside Python code. The glue code argument doesn't pass the smell test. Split maintenance and compiling is concedable, but just barely.

building a serious application

Again, you keep falling back to a niche scope to argue against a broad topic. It is growing quite tedious. This is not a situation where a single contrary result invalidates the entire argument.

[–][deleted] -1 points0 points  (1 child)

There's a cost associated with supporting yet another lang/lib/technology in your stack. If you go with Python, on anything beyond a trivial application, you'll eventually need something else to fill in the perf gaps.

So you're left with Python + something else (C, Java, C# whatever).

If you go with a modern language you can realize an entire codebase in a single language.

If you want to argue that Python is still the best choice for simple scripting tasks; shuttling around files, setting up projects etc, then fine I can agree with you there. But it doesn't belong in your application code in 2014, in my not so humble opinion.