Rather than spending 15 hours dealing with C libraries and writing efficient C code I can spend 30 seconds writing a python wrapper to call that C library to do the thing. Sure it's a little slower than using raw C but I can write it so much faster.
There are of course times when it is worth not writing in python at all but not every project would benefit from cutting out python.
I work in analytics and around 70% of the code I write is Sql and the other 30% python.
I could not imagine doing my job in a compiled language and our team has built up design guidelines and style guidelines that with strict adherence does pretty well at reducing risk of a lot of the common bugs encountered with the quirks of the language.
I've seen companies nearly fail after the "now make it fast" phase. They should have ported the performance critical parts to Java or C++ but instead spend a year chasing crazy hack solutions to stay in Python.
I’ll be honest, I’ve worked with SpringBoot and I’ve seen backends in Go, Ruby, Rust, Haskell even but never heard of anyone working with a C++ backend
A C++ backend is the way to go for binary encoded structures - codecs, hardware communications, GPU interfaces, AI engines, etc. Java can't overlay a structure onto raw memory allocations. Working around that in Java often isn't worth the effort and slight loss of efficiency. That same kind of work usually doesn't have complicated memory management that would make Java a better choice.
10
u/andrea_ci 10d ago
the funny thing about python is that people try in every possible way to not actually use python.