This page was slow because it wasn't cached since people seldomly visit this page. Which other pages are slow for you?

Obj-C & Swift are the hardest to implement because they require OSX. We could use GNUstep, but its kind of a mess from what we understand. Our plan was to run a separate code execution cluster using hosted Mac Mini's and we have the test framework implemention done to make it work with our schema, we just need to finish the infrastructure which we don't have the development resources to do right now.

You can print anything you want to STDOUT.

I agree.

The description could use some examples.

Nice beginner kata.

Thanks. It should be fixed now.

I updated the test cases to use the new describe and it features. Hopefully this puts the fun back into the kata. I didn't want to be super specific with the test case errors. If I did people would just do the minimal amount needed to pass the tests, where I was hoping that by being more vague it would force you to have to create a more thorough set of test cases.

Nice kata. I think a harder version that builds off of this one would be great. Where you are given a block of text (or array of words) and you need to find all anagram groups within the text.

Preloaded section:

Array.prototype.sort = function(){throw 'Sort is disabled';}

Man you must love your oxford commas.

They are using git flavored markdown. Use three back ticks (```) to start and end a code block. After the first set of back ticks you can specify the language.

I updated the kata to also support processing non-hash items using the identify method. This will break all of the existing solutions unfortunately, but it makes the class purpose more practical and I think it probably helps clarify some of these issues. With normal class instances comparing (==) two instances with identical attribute values will return false since they don't point to the same reference.

I think I'm going to stop using the word reference, especially since in ruby its a bit confusing since the following would work:

a = {id: 1}
b = {id: 1}

a == b # in ruby this would be true, in many other languages (ie JavaScript) it would be false since they don't point to the same memory reference

When I say "reference" I meant that the typical way of determining if two items are the same (they point to the same reference). For example:

a = {id: 1}
b = {id: 1, name: 'example'}

# without identity being called they would be compared like so:
a == b # false

# with identity(:id) called they would be compared like so:
a[:id] == b[:id] # true