>and yet
it just werks for its intents and purposes.

>>109278516
Literally no usecase
It's pure shill + major security risk
It has terrible syntax and abysmal performance, the dependencies are fragile, badly written, mostly untrustworthy and riddled with supply chain breaches.
No sane human being would use this thing in production.

It is for all intents and purposes, a no-coder slop script at best.
The only reason the infrastructure of our company works within reason is because I gate keep every idiot trying to implement anything in this piece of shit scripting language.
It's either native only with approved dependencies or bash/ powershell.

Python should be forbidden at every level.
Instead, GitHub is being flooded by subpar ((developers))) shitting out absolute garbage and call it "a tool"
Sure it's a tool made of chineesium which breaks after a minor version jump and is bottom line unusable for anything but proof of concept.

>>109278582
skill issue

>>109278506
It works and causes Pust users to seethe uncontrollably due to being written in a superior compiled language, C.
>>109278582
>terrible syntax
Modern programming languages borrow clean syntax from it though, see: Go
>abysmal performance
well duh it's using big integers and high precision floats, good luck doing anything serious with your locked precision numbers
>untrustworthy and riddled with supply chain breaches
Just use the standard library Chuddie

Everything else that you mentioned is just a warped opinion of yours specifically. Powershell/bash shilling at the end is laughable. You seem to be all wrapped up in performance jerking, but recommend fucking one-line-at-a-time interpreted fucking bash and retard syntax PS. Fuck man.

>>109278506
why should you use python when Go exists? Go is just faster and has better concurrency.

is there a point to high level langs in prod when llms can make low level langs accessible to morons?

File: python-vs-go.png (216 KB, 1536x1033)

216 KB PNG

>>109279543
Python still superior for lots of scripts. Dynamic types and no compile step is an advantage in many situations. People love dismissing short scripts meanwhile they spend hours clicking stuff in GUIs instead.

picrel takes like 30 seconds to run in Python. No idea how fast it would run in Go but probably identical given that neither script was written to be parallel anyway and 99% of the time is going to be spent in ffmpeg. It's a throwaway script. I literally do not care that [outname] isn't robust if it gets an unhandled file extension. There will never be an input exception because I have 100% of the input data that the script will ever process. I don't need it to be generalized because every time I do this kind of bulk operation, there's almost always something slightly different. Like maybe I want all the output into a new directory or maybe I want to do more automatic renaming, or use a different bitrate or frequency.

Indeed
Lisp or Lua is far better

>>109278964
Reddit post

>>109278506
I don't really know what i should imagine.

Is it like invisible implicit type conversion galore with invisible blackbox operator overloading?

>>109278582
>which breaks after a minor version jump
Are you still talking about Python?

>>109278506
> imagine
I can't
I don't like it so I don't use it
Just don't use python, it's a bad language
My likes: Rust, Julia, Matlab

>>109278506
Cry more

>>109281438
utility scripts that save time for a one off task are completely fine. it's when people shove it into guis and make abomination applications out of it. the hate for python comes from the later but for what you are talking about it's completely fine. if only the world understood it works best as a scripting lang only and nothing more

>>109278506
Suck harder, OP.

>>109284100
(You) suck

>>109278516
>>109278964
>still twerking
not an argument

>>109283894
No, it's strongly typed.

>>109278506
sadly, I don't have to imagine