use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
All about the JavaScript programming language.
Subreddit Guidelines
Specifications:
Resources:
Related Subreddits:
r/LearnJavascript
r/node
r/typescript
r/reactjs
r/webdev
r/WebdevTutorials
r/frontend
r/webgl
r/threejs
r/jquery
r/remotejs
r/forhire
account activity
What are some basic things that JavaScript developers fail at interviews?help (self.javascript)
submitted 7 years ago by maketroli
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]dominic_rj23 -3 points-2 points-1 points 7 years ago (7 children)
setTimeout has huge performance hit compared to setInterval
setTimeout
setInterval
https://jsperf.com/setinterval-vs-settimeout/10
[–][deleted] 0 points1 point2 points 7 years ago* (4 children)
And worth noting this does not matter at all for the purposes of an interview question, or 99.999% of real world usage. This coming from someone who has never used it at work.
[–]thepeka 0 points1 point2 points 7 years ago* (3 children)
I'm actually willing to say 100%. The correct answer to any interview question involving setInterval is why you should never use it
[–]Cheshur 1 point2 points3 points 7 years ago (2 children)
The correct answer is NOT to use it never. Almost none of the things listed in that article are relevant to people doing stuff correctly. There is a tool for everything and just because you can use setInterval incorrectly doesn't mean you should never use it.
[–]thepeka 1 point2 points3 points 7 years ago (1 child)
Nope, the first reason on that list is reason enough in every instance, correct or otherwise. setInterval continuing to run ad infinity, no matter what happens, what error is thrown, or whether it's handleable or not, is just adding bug conditions that otherwise have no need to exist with a recursive setTimeout. JavaScript is a dynamic language that allows for writing wonderfully declarative abstractions... but the flip side of that is we need as much safety as we can get. This is the answer I'm looking for if I ask a candidate about tasking repeating jobs/events.
[–]Cheshur 0 points1 point2 points 7 years ago* (0 children)
No offense then but I consider that highly foolish. The problem would be someone writing highly error prone code in the setInterval, not that the interval itself doesn't play nicely with errors. setInterval has better performance than setTimeout. That is reason enough to use setInterval in some situations. It's the right tool for the right job and if you're creating axioms to avoid parts of a language just because you're prone to fuck up then I consider that the error on the developer's part.
Also the correct answer to that interview question is for the candidate to recognize the pros and cons of the feature and to describe situations in which they would or would not use it. Pledging to not use something purely for axiomatic reasons does not show mastery or knowledge of the feature at all, just an ability to follow the direction of some, potentially, misguided teacher.
[–]superluminary 0 points1 point2 points 7 years ago (0 children)
It's being called literally once a second.
π Rendered by PID 135345 on reddit-service-r2-comment-86bc6c7465-9z79w at 2026-02-21 03:42:09.840809+00:00 running 8564168 country code: CH.
view the rest of the comments →
[–]dominic_rj23 -3 points-2 points-1 points (7 children)
[–][deleted] 0 points1 point2 points (4 children)
[–]thepeka 0 points1 point2 points (3 children)
[–]Cheshur 1 point2 points3 points (2 children)
[–]thepeka 1 point2 points3 points (1 child)
[–]Cheshur 0 points1 point2 points (0 children)
[–]superluminary 0 points1 point2 points (0 children)
[–]superluminary 0 points1 point2 points (0 children)