Partly this:
and partly because /prog/ was filled with stupid homosexuals and now it is dead. They now roam IQfy mindlessly hating everyone's contribution because they can no longer ``expert programmer'' themselves into ecstasy.
Butt mostly the first one.
Because half of IQfy is jobless neets that unironically use Gentoo + some niche window manager and using "hard" software is the only thing that gives them any semblance of value in their life. Python is the antitheses of this as it allows some beginner to spin up a webserver in 30 mins (if that) and have a working website which is something that takes IQfyentoo man days to do in their precious C.
both true.
most of IQfy doesn't understand the concept of knowing multiple languages with different usecases. they think software engineering is just writing C code that does something as fast as possible and interpreted scripting languages/garbage collectors/dynamic typing are BLOAT in any and all contexts.
Because half of IQfy is jobless neets that unironically use Gentoo + some niche window manager and using "hard" software is the only thing that gives them any semblance of value in their life. Python is the antitheses of this as it allows some beginner to spin up a webserver in 30 mins (if that) and have a working website which is something that takes IQfyentoo man days to do in their precious C.
>and have a working website which is something that takes IQfyentoo man days to do in their precious C.
This is a good example of this:
because it's popular. IQfy is a contrarian board
and a little of this:
Partly this:
and partly because /prog/ was filled with stupid homosexuals and now it is dead. They now roam IQfy mindlessly hating everyone's contribution because they can no longer ``expert programmer'' themselves into ecstasy.
Butt mostly the first one.
i think the language is ok. i just hate everything else about it. >dependency tree resolves targets in the most naive way possible >5+ different ways to declare deps because language designers punted on it >managed clients that also run python end up bleeding deps between your source and their environment >gets used for ML, data eng, replacing bash, CLIs, etc... meaning your project will inevitably hit dependency conflicts as it ages >GIL is definitively anti-unix >async given 0 consideration
you joke, but i've seen too many python programs that basically act as extremely shitty schedulers / supervisors of OS processes to work around this terrible design decision. i'd argue it's the only complete parallel programming pattern in the language.
It isn't, threading/async is the only correct way, that's because if you aren't I/O bound you're moronic for using Python.
2 weeks ago
Anonymous
right, so you acknowledge that threading/async is not a complete solution on python. works perfectly on node, go, c++, java... probably almost any other language.
it's a moot point honestly. most of the dumbasses writing python aren't about to try parallelizing their code (and then they do, we end up with another instance of
you joke, but i've seen too many python programs that basically act as extremely shitty schedulers / supervisors of OS processes to work around this terrible design decision. i'd argue it's the only complete parallel programming pattern in the language.
).
2 weeks ago
Anonymous
I acknowledge that Python is slow and meant for shuffling I/O and not for doing the job of FORTRAN
2 weeks ago
Anonymous
100% agreement on not replacing FORTRAN. it can feed a C/FORTRAN backend but it shouldn't be solving anything itself.
Agreed, and I don't know how it became so popular in that context. Although...I fricking hate Java because all the frameworks seem to be over engineered "academic OOP." .NET can also be that way sometimes.
>knowing multiple languages
they're all the same shit, you'll learn the rest of them in couple of days.
your perception of this field is warped
Yes and no. Once you've picked up one it's much easier to pickup another one. What takes time is learning the fine details, the style and the design patterns which are common in that language. Also being familiar with the common libraries and frameworks so you're not constantly looking shit up.
But yeah, if you're a good SE in C/C++, C#, Java, etc then Python is easy to pickup.
It's mostly filled with idiots who defend it to be honest.
It's absolutely trash. It's design is trash from the ground of and much of the weird behavior is clearly simply a product of how the interpreted was programmed and Guido not even considering what would happen if someone closed over loop variables and the 2to3 transition was a disaster anyone with experience could see coming but we it again with Wayland: >Someone comes with some new technology >WHY ARE PEOPLE NOT SWITCHING? THIS NEW THING IS BETTER. I DON'T GET IT! YOU SHOULD ALL SWITCH
The mentality of people who program for fun rather than for money who don't realize that even if your new thing should be better, switching costs people time and effort and thus money and they effectively have to pay a price to switch so it should be worth it.
Someone has to be paid to rewrite python2 code into python3 so it has to be worth the money. Python3 needs to be so much better that it's worth the cost of switching and it isn't.
Blame H1B for that. The program shouldn't exist, and nobody bothers obeying the relatively lax rules it lays down because gov doesn't bother enforcing them ever.
because its easy to use badly, and using it well requires you to spend a significant amount of time using it badly until you learn what guido intended you to do
You annotate all the function parameters and return types as well. And what you do is run mypy --strict to check everything and tell you what's wrong or missing. It catches a lot of stuff
Python is my favorite scripting language but I guess I don't represent /g's opinions.
Indeed, Ruby's syntax is very nice, I think the best after Python. It's a sad and unfair world where pieces of shit like PHP and JS are more popular than Ruby.
I don't hate it, but it's dense to read. Although I like Java and JavaScript, so I am biased. I find that when reading Python you think you understand what you read, but you need to go back and read it again.
because it's popular. IQfy is a contrarian board
Partly this:
and partly because /prog/ was filled with stupid homosexuals and now it is dead. They now roam IQfy mindlessly hating everyone's contribution because they can no longer ``expert programmer'' themselves into ecstasy.
Butt mostly the first one.
both true.
most of IQfy doesn't understand the concept of knowing multiple languages with different usecases. they think software engineering is just writing C code that does something as fast as possible and interpreted scripting languages/garbage collectors/dynamic typing are BLOAT in any and all contexts.
Except that interpreted gc dt is being used in places where it is BLOAT and shouldn’t be used.
>knowing multiple languages
they're all the same shit, you'll learn the rest of them in couple of days.
your perception of this field is warped
that's rich coming from baby duck that couldn't get past his first fizzbuzz
You've missed the point entirely and are the most obvious nocoder NEET I've ever seen. Get a job, hippy.
Because half of IQfy is jobless neets that unironically use Gentoo + some niche window manager and using "hard" software is the only thing that gives them any semblance of value in their life. Python is the antitheses of this as it allows some beginner to spin up a webserver in 30 mins (if that) and have a working website which is something that takes IQfyentoo man days to do in their precious C.
>and have a working website which is something that takes IQfyentoo man days to do in their precious C.
This is a good example of this:
and a little of this:
>system whose core is Python is used by people who hate Python
bot thread
is there even python jobs that arent related to data science or something that isnt your average shit?
t. unemployed euro
because it works. Unlike fa/g/s.
i think the language is ok. i just hate everything else about it.
>dependency tree resolves targets in the most naive way possible
>5+ different ways to declare deps because language designers punted on it
>managed clients that also run python end up bleeding deps between your source and their environment
>gets used for ML, data eng, replacing bash, CLIs, etc... meaning your project will inevitably hit dependency conflicts as it ages
>GIL is definitively anti-unix
>async given 0 consideration
>GIL is anti-unix
just do it the unix way by using multiprocessing to spawn 99999999 processes to solve one problem bro
you joke, but i've seen too many python programs that basically act as extremely shitty schedulers / supervisors of OS processes to work around this terrible design decision. i'd argue it's the only complete parallel programming pattern in the language.
It isn't, threading/async is the only correct way, that's because if you aren't I/O bound you're moronic for using Python.
right, so you acknowledge that threading/async is not a complete solution on python. works perfectly on node, go, c++, java... probably almost any other language.
it's a moot point honestly. most of the dumbasses writing python aren't about to try parallelizing their code (and then they do, we end up with another instance of
).
I acknowledge that Python is slow and meant for shuffling I/O and not for doing the job of FORTRAN
100% agreement on not replacing FORTRAN. it can feed a C/FORTRAN backend but it shouldn't be solving anything itself.
tree resolves targets in the most naive way possible
elaborate
Every time i have to use softwar writen in this shit i get breakages.
It somehow manages to be slow by today’s standards.
It's not that easier than Java, C# or Go. But 10x times slower.
Agreed, and I don't know how it became so popular in that context. Although...I fricking hate Java because all the frameworks seem to be over engineered "academic OOP." .NET can also be that way sometimes.
Yes and no. Once you've picked up one it's much easier to pickup another one. What takes time is learning the fine details, the style and the design patterns which are common in that language. Also being familiar with the common libraries and frameworks so you're not constantly looking shit up.
But yeah, if you're a good SE in C/C++, C#, Java, etc then Python is easy to pickup.
It's mostly filled with idiots who defend it to be honest.
It's absolutely trash. It's design is trash from the ground of and much of the weird behavior is clearly simply a product of how the interpreted was programmed and Guido not even considering what would happen if someone closed over loop variables and the 2to3 transition was a disaster anyone with experience could see coming but we it again with Wayland:
>Someone comes with some new technology
>WHY ARE PEOPLE NOT SWITCHING? THIS NEW THING IS BETTER. I DON'T GET IT! YOU SHOULD ALL SWITCH
The mentality of people who program for fun rather than for money who don't realize that even if your new thing should be better, switching costs people time and effort and thus money and they effectively have to pay a price to switch so it should be worth it.
Someone has to be paid to rewrite python2 code into python3 so it has to be worth the money. Python3 needs to be so much better that it's worth the cost of switching and it isn't.
Too easy and lets Pajeets into the craft.
Blame H1B for that. The program shouldn't exist, and nobody bothers obeying the relatively lax rules it lays down because gov doesn't bother enforcing them ever.
slow af, only useful for small scripts
because its easy to use badly, and using it well requires you to spend a significant amount of time using it badly until you learn what guido intended you to do
every other language is infinitely easier to use badly
I'm enjoying python very much
And it's actually heavily typed if you bother to use annotations
number_ten: int = 10
this is only visual stuff and isnt enforced in runtime though
You annotate all the function parameters and return types as well. And what you do is run mypy --strict to check everything and tell you what's wrong or missing. It catches a lot of stuff
mypy is a good idea until you include a library and understand why nobody uses this
Most libraries I have to # type ignore
and that's the problem, I need full type checking, otherwise it's worthless
Also in that int example you likely don't have to annotate it since it can infer it's an int
I like python
No you don't.
Dumb&slow
Like zoomers
Thats why its IN
I will never get over the fact that Python and PHP won somehow and beautiful based Ruby lost the race
t. still working in Ruby for a living
Python is my favorite scripting language but I guess I don't represent /g's opinions.
Indeed, Ruby's syntax is very nice, I think the best after Python. It's a sad and unfair world where pieces of shit like PHP and JS are more popular than Ruby.
just write an epic JEET compiler for Ruby and make Ruby on Rails computitive with Node.js
I don't hate it, but it's dense to read. Although I like Java and JavaScript, so I am biased. I find that when reading Python you think you understand what you read, but you need to go back and read it again.
its too slow for any direct computation (unless you play around with Cython)
It’s the only language I use.
Currently using it with ML algorithm writing a paper about melanoma outcomes depending on treatment.
horrible language to read.
you have no idea what functions are returning unless you read through the whole thing.