const max = (a, b, c) => ([a, b, c].sort().pop());

if i'm writing something SOOO performance critical that i can't afford the extra One comparison that comes with a sort i'd write it as

function max(a, b, c) {
if (a > b) {
return Math.max(a, c);
}
return Math.max(b, c);
}

because at that point you're doing too many things for it to make sense as a one-liner

this is all assuming Math.max can't take a third argument, or an array argument or something. which seems to be the assumption made in the premise

@monorail oh my fucking god Math.max can take a third argument in JavaScript fuck me

@monorail when i do things like this aesc calls them "caleb solutions"

@wallhackio @monorail I like Clodsire's solution better, for what it's worth

What the Glaceon wrote just feels so wrong

IDK, I'm not a JavaScript programmer, it's probably an OK solution in terms of performance

It just feels so wrong instead of the obvious solution of using 2 ternary operators...

Follow

@vaporeon_ @monorail well modern architecture is so performant that it is okay to always prefer elegance over performance

Sign in to participate in the conversation
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.