Come they told me, pa rum pum pum pum A new born King to see, pa rum pum pum pum Our finest gifts we bring, pa rum pum pum pum To lay before the King, pa rum pum pum pum, rum pum pum pum, rum pum pum pum,
So to honor Him, pa rum pum pum pum, When we come.
Little Bobby, pa rum pum pum pum I am a poor boy too, pa rum pum pum pum I have no gift to bring, pa rum pum pum pum That’s fit to give the King, pa rum pum pum pum, rum pum pum pum, rum pum pum pum,
Shall I play for you, pa rum pum pum pum, On my unsanitized database inputs?
Remote is something I’d only enable while using it. Once found my ubuntu (I use arch btw) with the setting on for some reason. Might be worth checking even if you never turned it on.
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:
<span style="color:#323232;">const unsorted = [1, 100000, 21, 30, 4]
</span><span style="color:#323232;">const sorted = unsorted.sort((a, b) => a - b)
</span>
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.
ah yes, a reasonable solution to that problem that any human would think of
ah yes, a reasonable problem that any human would think of – “what if someone tries to sort a list containing some integers and some arrays, and our interpreter needs to keep chugging instead of telling the programmer they fucked up?”
The princess is saved, but all you can think about is rescuing another, with an entirely different plan. Which is just as well because you have no fucking idea how to explain the one you just wrote and executed.
You have rust, you decide to rewrite the C plan but the only library that supports it uses unsafe code so you go back and rewrite it. Wait what were you working on?
C# is about right. LINQ was meant to make things easier, or at least the code easier to read. Instead, you gain this addiction to seeing how much functional logic you can fit into one line of code (or a single multi-line query) while still remaining readable.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.