News for hackers. Stuff that matters.
Re:Elm 0.12.1: Fast immutable arrays by rurban on Friday May 02, 2014 @12:26PM (#7686604)
Logarithmic is not constant.

The fact that elm announces constant array access will not surprise anybody, as this is an inherent property of arrays. But then seeing that they have to use radix-trees for arrays and announcing it as constant is highly misleading. These guys should switch over to politics.

And this only holds for immutable arrays! So even without push,pop,shift,unshift they have to use trees for arrays.

Re:Elm 0.12.1: Fast immutable arrays by reitzensteinm on Friday May 02, 2014 @01:14PM (#7686915)
Fully populating a 128 bit memory pool would take enough energy to boil the oceans[1]. This requires a branching factor of 26 to address.

So the absolute worst case scenario - even if we get science fiction computing - is a small, constant number of indirections.

The whole purpose of this type of analysis is to get an intuitive approximation as input size grows. The graphs for log32(n) and 1 will be essentially indistinguishable, and most programmers have a much clearer understanding of constant time versus O( log32( n ) ).

It is not misleading, it is a simplification that is absolutely valid to make.

[1] https://blogs.oracle.com/bonwick/entry/128_bit_storage_are_y...

Re:Elm 0.12.1: Fast immutable arrays by millstone on Friday May 02, 2014 @01:55PM (#7687110)
Agree with what you wrote. However, the article is misleading when it says that because the operations are "constant time in practice," that they are "fast."
Re:Elm 0.12.1: Fast immutable arrays by reitzensteinm on Friday May 02, 2014 @02:50PM (#7687400)
Unless the article has been edited, it doesn't say that[1].

What the article calls "constant time in practice" is necessary, but not sufficient.

As you say, it's not correct to say that CTIP means that you're fast - after all, you could make a HTTP request per array access and maintain constant time.

But you can say that taking advantage of CTIP allows you to achieve speed.

In my opinion, it takes quite an uncharitable reading of the article for it to seem like they mean the former.

[1] (The closest section to your quote) "Elm now has fast immutable arrays. How can that be? Is there such a thing? Thanks to Christian Widera, the new Array library uses some very clever data structures that make common operations like get and set constant time in practice! We will get into the details later in this post, but the big takeaway is that you can have immutability and speed. "

Re:Elm 0.12.1: Fast immutable arrays by millstone on Friday May 02, 2014 @04:11PM (#7687852)
> What the article calls "constant time in practice" is necessary, but not sufficient.

So non-CTIP data structures cannot be fast! There it is again!

This line in particular jumped out at me:

One way to make these trees faster is to increase the “branching factor”.

And we are lead to conclude that the 32-ary tree is faster than the binary tree. But there's necessarily a tradeoff here: a larger branching factor results in fewer node traversals, but more copying and wasted space on insertions and deletions.

So it's not at all obvious that a higher branch factor is faster. After all, in the limit as the branch factor approaches infinity, you recover naive arrays.

Basically I'm begging for benchmarks! It would be very interesting to see the performance effects of adjusting the branch factor.

Re:Elm 0.12.1: Fast immutable arrays by JeanPierre on Friday May 02, 2014 @12:36PM (#7686669)
Constant time in practise is a notable difference from saying constant time.

I can always sort a 32-bit int array in worst case linear time using counting sort, which in theory is better than the worst case runtime of quicksort, O(n²). Is it better in practise? Of course not, the constant factor is just too high, both for time and memory.

Re:Elm 0.12.1: Fast immutable arrays by ajanuary on Friday May 02, 2014 @01:30PM (#7686990)
Much as I dislike it, not everyone uses 'array' to mean a collection with constant time indexing. Lots of people use it to mean an indexable collection.

The 'constant' vs. 'almost constant' has been covered by other comments.

Re:Elm 0.12.1: Fast immutable arrays by pohl on Friday May 02, 2014 @12:33PM (#7686648)
Given the current rate of progress, what year would you predict that web browser applications use large enough arrays where that distinction makes a practical difference, and not just an academic one?
Re:Elm 0.12.1: Fast immutable arrays by tiles on Friday May 02, 2014 @12:28PM (#7686617)
Why are Elm's arrays so much more complex than JavaScript's O(n) arrays?
Re:Elm 0.12.1: Fast immutable arrays by wheatBread on Friday May 02, 2014 @12:33PM (#7686649)
It's about mutability vs immutability. I think Zach explains the whole idea of immutable arrays really well: http://www.infoq.com/presentations/julia-vectors-maps-sets
Re:Elm 0.12.1: Fast immutable arrays by dalke on Friday May 02, 2014 @12:31PM (#7686632)
Elm's arrays are immutable. JS's are mutable.
Re:Elm 0.12.1: Fast immutable arrays by gliptic on Friday May 02, 2014 @12:41PM (#7686700)
slice/push/get/append can stand in for push/pop/shift/unshift. The immutability of the arrays is considered a feature and Javascript arrays are O(N) for the same operations.