Search for a command to run...
A fond believer in learning by doing. Loves to try out new languages in the world of computing
Want to optimize your JS-code(s)? Welp, I've got you covered! https://hasty.dev 🧑💻
Want to tweet your commits? https://gitbird.dev 🐦 It's dead I think, honestly, I haven't been keeping up with the death of the blue-bird-site 🤐
No comments yet. Be the first to comment.
Which is faster? In this series I'll explore a few patterns in programming to try and figure which are faster and/or better to use - in the need for speed.
The Prequel
Micro-optimizations #3
Sorting Algorithms - Short
The Idea I've for a while have been tinkering with what I think JavaScript'ers have been missing - namely a way to make Jupyter-like notebooks! So I started building. Actually been on this since November 12th - so about a month. Lot's of stuff is goi...
The Prequel
The love, and arguebly one of my favourites, things of ES6 is the Spread-operator. This has made my work so much easier. Also, makes everything look so lovely!
Here comes the question:
Is the
Spread-operator faster or slower than using the complete object?
As you can see, using the complete object everytime seems like a better choice. Except for readability, which I do prefer over a such small optimization.
How about numbers? Imagine you're in an interview. The interviewer asks you how to parse an integer. You think to yourself:
Huh? That's a silly question.
Though, is it? Is it really a silly question? Well, I don't think it is, there are a magnitude of ways to parse an integer in JavaScript.
Imagine we have this variable
const n = "1";
How would you parse n into an integer d? You could for example do:
const d = parseInt(n);
Easy peasy! Well, if I were to be your interviewer, I'd say:
Sure, but are there any other ways?
To this, you should not hesitate, but prompt answer:
Yes! There are many ways. Do you want to see another?
Then you quickly write another way below like so:
const d = Number(n);
This would show that you do know some options, but what if you swiftly wrote below the like again, whilst talking
const d = +n;
I ofr one, would be super happy and kind of proud, that you'd know at least three options. I wouldn't have to more questions about numbers.
How about 10 options in total? Well, these might still just be some of the options, but heck. It's enough for a proper micro-benchmark.
In your journey of bettering yourself in the world of JS, you'd try such a benchmark, just to check which of those ten options is the best. Of course, this small website can't give you advice when to use which options in which situation, but it can help you along some of the way, but lowering the guess work.
I found the best options, both for readability and speed, is the parseInt(n, 10), as this actually tells the reader that it'll parse an integer n in the base 10 format.
{ Best, Mads Bram Cordes }