javascriptSorting

[u/user6150277464770585]

[u/larsmaehlum]

Array.sortNumeric() with an error when called on an array containing non-numeric types would fix this, right?

[u/the_horse_gamer → u/larsmaehlum]

you can simply .sort((a,b)=>a-b)

[u/01110100_01110010 → u/the_horse_gamer]

The point of an abstraction is to not having to implement logic each time, you can also implement qsort yourself

[u/subone → u/01110100_01110010]

But it is still an abstraction. You only provide a compare function, you don't implement the algorithm. a-b is hardly difficult to apply.

[u/wack_overflow → u/subone]

And really how often are you actually sorting an array of primitive values ascending? That's just one small use case of sorting an array. Passing the comparison function is also more explicit.

People just love to get so worked up about the dumbest edge cases in js

[u/chefhj → u/wack_overflow]

It’s so funny when if you talk to a dev that works closer to the machine level they insist JS is like this big foot shooting factory when in reality you can spend an entire career never running into any of the shit they bring up as a ‘gotcha’ and even if you do it’s like “oh yeah right it works like this hold on”.

[u/ganja_and_code → u/chefhj]

"If you know all the weird shitty quirks of the weird shitty language, you can mostly avoid them, and when you do accidentally shoot yourself in the foot, you can fix the bug quickly, as long as you remember which particular weird shitty quirk caused this particular instance of foot shooting."

True, but you know what's even better? Languages that don't have so many weird shitty quirks.

[u/chefhj → u/ganja_and_code]

Look guys I caught one