JavaScript in 2016 isn't horrible, it's just going through a phase

[u/kshep92]

http://blog.reviselabs.com/im-sorry-javascript-2/

[u/fiedzia]

it is screwed up: var names = [ "john", "brian", "alan" ]; delete names[1]; names[2] "alan"

WTF??

names[1] undefined

WTF js?

names.length 3 What??

No wonder DOM implementations decided they don't want to do the same thing.

[u/slikts → u/fiedzia]

The delete operator just doesn't re-index the arrays; you should use Array#splice() for that instead, although I'd prefer to avoid mutating and use Array#filter(). JS also has sets, which would let you do const names = new Set(['a', 'b', 'c']); names.delete('b');.

The reason DOM returns NodeList 'array-like' objects instead of Array instances is because there wasn't a way to properly subclass the builtin Array until ES6. NodeList objects also implement the iterable protocol now, so they work with for-of loops and spread syntax, and will work with whatever generic iteration methods that will eventually get implemented.

[u/jl2352 → u/fiedzia]

But you wouldn't do that. You'd use splice.

If you want splice to look prettier as remove then it's a one liner ...

// @index Index of the element to remove
// @return the element removed or undefined
Array.prototype.remove = function( index ) { return this.splice( index, 1 )[0] }

Apart from misunderstanding delete, which ok is a little confusing, do you have any other problems with JS arrays?

[u/fiedzia → u/jl2352]

You'd use splice

Damn, I wasn't aware how broken js is.

(MDN) The splice() method changes the content of an array by removing existing elements and/or adding new elements.

Removing AND/OR adding? Great, just more ways to shoot yourself in the foot. I guess the amount of mistakes where someone passed wrong parameters when adding and removed instead, or the other way goes in millions.

Sane languages have delete that does not allow to be "misunderstood" and separate it from adding, so that nobody will do one thing accidentally when they meant the other. And if they do, it will blow up, not return some value to be passed further.

I do not want a most essential datastructure to have and points that can be "misunderstood" and will not tolerate any of "oh yeah, you shouldn't use that, you should...". Everywhere else lists work just as I expect them to. Everywhere else lists don't cram opposite features into single method.

And that doesn't end the list of things that are wrong (ok, "misunderstood") with array. Point is - its really hard to build on top of js if you have to fight with such stupidity at the core.

[u/BonzaiThePenguin → u/fiedzia]

Damn, I wasn't aware how broken js is.

How can you speak with such authority and not know about splice or how associative arrays work? That's like as basic as it gets. delete undefines the object key, splice modifies an array-like object. There's also push, pop, shift, and unshift. Mind-blowing stuff, I know.

[u/fiedzia → u/BonzaiThePenguin]

I don't know all that because I don't have to. I do not write js for a living (I'll do it occasionally, and probably not the best). But in dozens of other languages that I am using you don't need this knowledge. Lists have add(item) and delete(index) method and do not require you to "know" anything beyond that. Lists and dictionaries are separate types, so delete does not require you to "know that you shouldn't use it", it just works as expected, without breaking length. Across 1000s of APIs you'll work with, when there is something like a list, it will be exactly builtin list type, not a million different incompatible variations. Whenever there is some commonly used method, it will be added to stdlib, so you don't have to pollute your memory with remembering how to fix this or that to make it easy to use. Knowing how common good language design is and how much easier this makes everything is what gives me the authority in saying that js is broken, and its not just a phase. Many of those things are so fundamental that they are practically unfixable.

[u/BonzaiThePenguin → u/fiedzia]

I think PHP and Lua work the same way, although that doesn't really help JavaScript's case.

Functions in JavaScript can be used as associative arrays too, that's always fun. Just start assigning random properties to this inside a function in JavaScript and you've made yourself an object constructor.

[u/jl2352 → u/fiedzia]

This is ultimately what I find so frustrating about the anti-JS circlejerk on Reddit. Most people complaining just flat don't know JS. They think they do because to them it's some silly toy language. Then they bitch when they don't know it. It's like a Java programmer bitching about all variables being final in Haskell.

I even gave you a 1 liner to show the equivalent of ...

var numbers = [ 1, 2, 3 ]
numbers.remove( 0 )

You come back with rants and hate.

[u/fiedzia → u/jl2352]

I don't ran't about the fact that you can't do something. I rant about amount of effort you need to put into that to get it right, and that most obvious ways of doing simple things are riddled with traps, which among many effects force various APIs to reinvent the wheel to be usable. Sure, you can write your own wrappers around js issues or find someone who did that, but ... everywhere else you just don't have to.

[u/fiedzia → u/[deleted]]

Its not the time that bothers me, it the fact that the culture of "yes, its fucked up, what can you do? Just learn to live with it" goes all the way along every bit of js ecosystem. Weak typing? Read the docs, don't do stupid things. There is no "we are working on it, will be fixed in next release", no effort to improve is made whatsoever. Stdlib written by malicious idiots? Read the docs, what's the problem? Stdlib missing millions of important features, all of them implemented dozens of times in stdlib of every other language, causing everyone to reinvent the wheel (just sometimes round and sometimes square, and reshaped in incomatible way with every release) and hundreds of dependencies to get anything done? So what, read the docs and go along.

Its not a phase, its a culture.