This is due to the default sorter in JavaScript sorting by the string value. The reason for that is that this won't create errors at runtime. Since JavaScript does not have types, this is the safest way of sorting.

This works:

const unsorted = [1, 100000, 21, 30, 4]
const sorted = unsorted.sort((a, b) => a - b)

[–] jmcs@discuss.tchncs.de 64 points 1 year ago (1 children)

Which is a fine decision if you have a programming language to do silly stuff on a personal geocities page, but a horrible one when you start using that language to handle serious data. Silently ignoring what's probably a bug is dangerous.

[–] seitanic@lemmy.sdf.org 25 points 1 year ago

Which is a fine decision if you have a programming language to do silly stuff on a personal geocities page

And that is, of course, what it was designed for.

JS is brilliant considering that it was created by one dude in 10 days. Nobody thought it would become nearly as important as it has become.

[–] UndefinedIsNotAFunction@programming.dev 11 points 1 year ago* (last edited 1 year ago)

Get out of here with your sensibility!

^kidding, ^js ^via ^ts ^is ^my ^life.