News for hackers. Stuff that matters.
Re:A performance comparison between Java and C on the Nexus 5 by pjmlp on Tuesday April 15, 2014 @01:54AM (#7590480)
Yes, because [] was a pre-processor hack back when Objective-C was invented and the compiler was actually a translator to C.

A means of gathering the code, dump it into a series of objc_msgsnd, without doing much of real compiler work.

There are languages with Smalltalk semantics without forcing me to type @ and [] multiple times per line, a pain in non US keyboards.

Re:A performance comparison between Java and C on the Nexus 5 by antimagic on Tuesday April 15, 2014 @06:50AM (#7591166)
Seriously? And all of those {} that you type in Java-land, they're magically easy to type? Which is of course a red-herring, because neither is enough of a drama to be taken seriously. You deal with it for a day or two and then forget about it.
Re:A performance comparison between Java and C on the Nexus 5 by mikeash on Tuesday April 15, 2014 @10:30AM (#7591995)
What kind of code are you writing where you have to type @ multiple times per line?
Re:A performance comparison between Java and C on the Nexus 5 by pjmlp on Tuesday April 15, 2014 @11:56AM (#7592501)

    id map = @{ @"my key": @123};
Re:A performance comparison between Java and C on the Nexus 5 by rsynnott on Thursday April 17, 2014 @11:38AM (#7604252)
Of course, in Java, this would look like (at best, using a third party thing):

ImmutableMap.builder().put("my key", 123).build();

Which hardly seems neater (especially in a more realistic case where you have more than one entry).

Re:A performance comparison between Java and C on the Nexus 5 by pjmlp on Thursday April 17, 2014 @01:44PM (#7605064)
The point was the pain to type @ in keyboards other than US.
Re:A performance comparison between Java and C on the Nexus 5 by mikeash on Tuesday April 15, 2014 @12:48PM (#7592866)
Surely you're not doing that anywhere close to every line.