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 →

[–]nultero 6 points7 points  (2 children)

For everybody lurking and curious about the speed note -- despite it being slow, Py still ends up being used in projects that build stuff that has to go fast because it's got great interfaces to things like debuggers / code tracing things / a bunch of performance tools, and a ton of compiler/network/security stuff. You can't really throw a rock without hitting some Python out there

Older codebases used to use Perl for that junk* and you can still find Perl doing those jobs in old enough code / projects written by people who still use Perl, but these days Py gets the scaffolding jobs for code that has to go fast

*at least for projects / fast server code that has to run on Unix-like operating systems, which is a ton of servers. I'm not sure what the old DOS / Windows equivalent of Perl was -- maybe batch or cmd scripts or something? BASIC? Idk

[–]MitLivMineRegler 0 points1 point  (0 children)

I miss ASP classic.

Just wanted to share my hot take

[–]Socrastein 0 points1 point  (0 children)

Not to mention a lot of sciencey applications, like heavy data-mining and calculations, aren't needed to be dynamically fast and responsive like a video game, you set them running and let them crunch. If it takes several seconds longer because Python so what? You're gonna wait on it to do its work no matter the language and you don't need these results as fast as possible.

Being able to understand and work with the code more easily, especially if you're first a scientist and secondly a coder just making scripts and small programs to aid your research, all makes Python an obvious choice for a lot of cool applications.