foo(bar, baz) you might write something like [foo multiplyMatrix:bar withTransposeOfMatrix:baz]. That example doesn't seem like much, but when you're dealing with thousands of lines of code, that kind of overall readability helps a lot.Instead of foo(bar, baz) you might write something like [foo multiplyMatrix:bar withTransposeOfMatrix:baz]. That example doesn't seem like much, but when you're dealing with thousands of lines of code, that kind of overall readability helps a lot.Well I'm not sure what
foo does, but assuming it operates on baz*bazT, that could be expressed in C# as foo(baz*baz.T) what with operator overloading and all. .T would be a property that takes the transpose of baz (more likely it might be baz.transpose() to be fair). array=[]
array.reduce(sum_of_squares);
def sum_of_square(a,b):
return a+pow(b, 2)
In C at least, this would be even less expressive, because you'd have to create a function pointer first. That would be like typedef ( (double) summer(double a, double b)); or something (my C is rusty). array=[] array.reduce(lambda a,b: a+pow(b,2));There's no defining a function solely for this purpose (which can lead to annoying namespacing issues, and is ugly since it's only used once), there's no looking around to figure out what it's called or anything like that. It's just right there.
I think forcing developers to learn good memory management habits (by, for example, culling crashy apps that don't manage memory properly) has resulted in better, faster iPhone applications and a better experience.I believe it is generally agreed that garbage collection is a Good Thing in terms of application stability, developer productivity, and so on. Good memory management habits in a GCed language can become bad habits, and really , good memory management habits are a set of skills that only apply to situations where one must manage memory. Now, in the iPhone case, excluding GC for performance reasons was Apple's call, and since I don't have a GCed iphone to test it on, I'm going to trust that their reasoning was sound.
Web guys, how's that IE6 treating you?This is what will prevent the adoption of HTML5 more than anything. Even with Microsoft pushing IE7 and IE8 (which is an entirely okay browser) for years now, IE6 usage has stabilized somewhere around 30% (IIRC). When IE8 came out, it was depressing to watch IE7 usage go down in proportion to the increase in IE8 usage, while IE6 usage stayed constant. (There is a graph of this somewhere, but I can never find it when I need it.)
posted by effugas at 7:00 PM on October 5 [+] [!]
Motherfucker WILL NOT DIE.
posted by Artw at 7:14 PM on October 5 [+] [!]
« Older Insects, spiders and other arthropods... | War Dances: “I wanted to call ... Newer »
This thread has been archived and is closed to new comments
posted by Chocolate Pickle at 12:39 PM on October 5, 2009 [5 favorites]