tef posted:

.sort(reversed=True)

tef posted:

i am really curious what cmp stuff people are doing because i really don't ever write them since i stopped doing java

Subjunctive posted:

so you specify that per key in the tuple?

tef posted:

i use key more than i ever used cmp. most of the python types already have comparisons, and for user types, implementing <, >, >=, <= is usually enough.

i do a lot of sorting by property, but not as much as sorting in default order, and very rarely sorting with a custom ordering

multigl posted:

i have strong opinions about sorting,

Athas posted:

Any program is just a sort with a sufficiently complicated comparison operator. This is serious stuff.

tef posted:

i am really curious what cmp stuff people are doing because i really don't ever write them since i stopped doing java

MononcQc posted:

Python programmers are known to work in memory constrained environments and never complain about speed of their programs, so that change was totally unwarranted.

Max Facetime posted:

something like

Java code:

	static void ehh(List<Point> points) {
		points.sort(Comparator.comparing(p -> p.x));
	}

Bloody posted:

the only time i have done something with a sort other than sorting numeric values or maybe strings in a default way was when i lazily used it to shuffle a list but i ultimately wound up adding a separate key to the item i was sorting that was pseudorandomly defined at instantiation (which was very important because for a given seed the random ordering had to be the same) and then sorting however c# wanted to on that key.

tef posted:

this is using a key function ???

tef posted:

again this is a key, not a comparator.

Bloody posted:

Lol yeah lemme fire up a garbage collected interpreted scripting language for a loving memory constrained environment. Let's just add in some nodejs for when we need to get close to the metal.

Cybernetic Vermin posted:

this is a weird debate since there is literally no way to defend the decision of removing the cmp= bit, proven by loving *guido* showing regret, so what can we even argue about other than randomly explaining how some things are not java to shaggar?

Brain Candy posted:

if you don't want to read page after page of nerds talking past each other over trivial bullshit, i don't know why you read yospos

MononcQc posted:

Suspicious Dish posted:

Staples Easy Button TM

MALE SHOEGAZE posted:

my girlfriend used to work at staples








i wish she had an easy button!!!!

VikingofRock posted:

Also C++ has its warts but it is a much, much, much, much, much better-designed language than javascript.

VikingofRock posted:

Honestly I think that having more ways of doing something usually makes a language richer and more expressive, and I would much rather have many ways of doing something than be forced into something clunky because the natural way isn't "pythonic" or something.


Also C++ has its warts but it is a much, much, much, much, much better-designed language than javascript.

MALE SHOEGAZE posted:

Hm, yes, the design of a language designed to be compiled using a relatively straightforward compiler, to provide low-level access to memory, to provide language constructs that map efficiently to machine instructions, and to require minimal run-time support, can be meaningfully compared to

JewKiller 3000 posted:

roflmao if you ever use python for anything

fart simpson posted:

i used to like python and then i figured out haskell is way better

fart simpson posted:

i used to like python and then i figured out haskell is way better

quote:

We should not beckon people into our field only to then ostracize them for the sin of learning PHP.

VikingofRock posted:

meh I think you can compare the overall design of two languages even if they were designed to do different things. the post I was responding to said that C++ suffers from poor design and feature bloat, and I while you can make a case for both it's pretty ridiculous to imply that c++'s design is bad on the level of js.

compuserved posted:

C is Manly, Python is for "n00bs": How False Stereotypes Turn Into Technical "Truths"