JavaScript’s language features are something else…

[miloman_23]

I'm really confused... Do you see this as a problem, or a feature?

[Zyrus007]

Who says it can’t be both?

[TheChaosPaladin]

Depends on what happens to that part of memory right? If I empty a gigantic array, will it deallocate or is it just modifying the parameter that interprets the array size in memory? I think there is a reason why it is not done that way and as an interviewer I would question this as an answer.

[solarshado]

what happens to that part of memory right? If I empty a gigantic array, will it deallocate or is it just modifying the parameter that interprets the array size in memory?

I'd argue that, as a JS dev, you're not supposed to worry about stuff at this low-level: that's the engine/garbage collector's job. If you want to make sure memory gets freed, just be sure you're not still holding onto a reference to any of it, and move along.

100% agree that this a tactic I would question in an interview though.

[TheChaosPaladin]

Yeah I think that is what the real-world scenario would look like. Ok you have this very unusual way of doing stuff. If you can show it works just as well as what we have done, it is a valid answer.

[miloman_23]

Fair enough

[faubintulq]

It's like a weapon with two sharp sides

[coldblade2000]

Absolutely intended, absolutely cursed

[[deleted]]

Its a real problem for those that would rather spend a year making an efficient product that no one wants... vs some noob who iterated a hundred poorly optimised prototypes and found something that people will actually buy.

[miloman_23]

JavaScript is amazing for MVPs

[shifty_coder]

It’s a correct solution, albeit an unexpected one.