Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

There is nothing silly in using new Array or new Object. Using {} for new Object or [] for new Array is just a notation. It is certainly not #1 in the list.
– Florian F
Commented Nov 22, 2014 at 12:05
1

I certainly wouldn't go through great effort to lambast the evils of using the Object and Array constructors over the literal expressions. In 8 years of sometimes frightfully stupid code bases I've never seen someone overwrite the Array or Object constructors and the performance benefit is negligible barring scenarios involving instantiation of massive amounts of arrays. But it's fewer keystrokes and you don't have to explain anything to the because-doug-crockford-said-so types on the team. Point #2 is more important but it's at least a little bit silly not to do it the easy way.
– Erik Reppen
Commented Nov 22, 2014 at 18:01

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »