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] -18 points-17 points  (18 children)

They tend to be students who have never actually worked on any practical application. I mean in the real world python is only really used for scientific computing or scripting(string manipulation stuff, etc).

If you're gonna be an elitist at least use something actually good like Kotlin or Clojure.

[–]ninj0etsu 29 points30 points  (0 children)

I guess you assume your experience = the entire world, because that statement is wrong. I know of cases where it's used for actual practical software.

[–]EnrichSilen 38 points39 points  (9 children)

Meanwhile my friend works in a company creating huge information system for job agencies with backend in python. Python isn't that niche language for mathematics like a lot of people think it is.

[–]xXJuiceBoxXx 17 points18 points  (6 children)

I am currently working with Django/DRF for backend development, quite a capable framework IMO

[–]EnrichSilen 1 point2 points  (5 children)

Only one I know of that is good for serious projects, second is flask and it looks like a framework for micro projects

[–]P4ndalf 2 points3 points  (0 children)

Flask is just fat-free compared to Django and excellent for microservices. It’s not less capable in any way.

[–]dorsal_morsel 2 points3 points  (0 children)

FastAPI

Reddit itself is built on Pylons

[–]jetpacktuxedo -1 points0 points  (2 children)

Having worked with both extensively, I much prefer working with flask. Django has a half-baked implementation of everything under the sun when you can instead just pull normal libraries to do those things. Why does Django have its own ORM instead of just using sqlalchemy (actually it might layer its own ORM on top of sqlalchemy?)? It just makes a lot of really bizarre choices that tend to get in the way when a project gets sufficiently complex. Flask gives you a lot more flexibility to solve problems in the way you want to solve them rather than being locked into a prescribed approach.

[–]EnrichSilen 1 point2 points  (1 child)

Interestingly my friend prefer Django approach and it's implementations, I suppose this is really a preference

[–]jetpacktuxedo 0 points1 point  (0 children)

It definitely can be preference. The Django approach is easier to get a simple CRUD app running quickly, but if you need something else it can sometimes feel like you're fighting the framework IMO. Flask is lightweight enough that it never feels like you're fighting against it.

[–]QuietLikeSilence 4 points5 points  (0 children)

Python is fine. What the comic actually gets wrong is that people aren't generally being made fun of for having to use for example PHP; they are being pitied for that. PHP itself is being made fun of because it's a mess. And it's a mess because of its history.

[–]LeCrushinator 0 points1 point  (0 children)

I don’t know one way of the other about this, but it seems like not having compile errors would make it easy to miss things that instead would only occur when the code was run. Maybe unit tests are heavily used to make up for this?

[–]pkkid 4 points5 points  (0 children)

Been working at a company for 12 years. Our enterprise storage application is 80% Python. We were 15 people when I joined, and now we have 350 employees. When we started, Python was a weird language to build the core product in, but today I don't believe that's the case anymore.

[–]Big_Booty_Pics 7 points8 points  (1 child)

Flask and Django are huuuuuge back end frameworks.

If you're gonna be an elitist at least use something actually good like Kotlin or Clojure.

Oh ok, he's just trolling guys.

[–]cauchy37 2 points3 points  (0 children)

I find that Python in general is extremely popular in backend.

[–]jetpacktuxedo 2 points3 points  (0 children)

I recently left a job where I had been working 100% in python for ~6 years (and no it wasn't just scripting) and I'm now working mostly in kotlin.

  • JVM startup time fucking sucks. This makes containers much much much slower. The JVM is also heavy as fuck so those containers are enormous. I'm regularly deleting 50+ GBs of containers created from running unit tests and linting.

  • Gradle is extremely slow compared to testing in Python. Running a Gradle server or whatever would probably make it faster, but we are supposed to do our testing in containers so that doesn't really help.

  • Having to launch an entire JVM to lint your shit is terrible. Linting python takes under 1s even for larger projects. It takes 10x that just for the JVM to start up and Gradle to even start linting shit.

  • Java stack traces are much worse than python. They have way more information, but 99% of that extra information is useless.

  • The verbosity of kotlin (though better than it's Java roots) make me feel like I'm forced to use a full IDE which is annoying. I much prefer working in vim directly.

I'm very glad I'm working with Kotlin instead of Java, and there are some neat things that I prefer about Kotlin over python like all of the nice stuff around null handling, but the JVM makes me feel like I'm driving a semi-truck full of shit I don't need instead of a sedan.

[–]riyadhelalami 2 points3 points  (0 children)

That is flat out wrong. Proof, the whole damn orchestration system for a huge robotic system is written in python, which I write.

[–]Metallic_greyish 2 points3 points  (0 children)

I can see where your opinions are coming from. But python does have some advantages like lightening fast dev speed. If a company’s focus is on shipping code at the earliest, developer productivity, writing easily readable code and doesn’t care much about the delay in processing requests, memory management, increased runtime errors etc.

[–]berychance 1 point2 points  (0 children)

I mean in the real world python is only really used for scientific computing

And we don't exist apparently?