HN user

inffcs00

22 karma

[ my public key: https://keybase.io/mrfelcio; my proof: https://keybase.io/mrfelcio/sigs/7_VnWqgUxaKtvHj9mP6PxjuOsPWwVlGvs_bw_o-dPAQ ]

Posts3
Comments8
View on HN

The problem here is that Google used the word "open" as a feature of Android and marketing term against iOS/Apple. But don't forget that a lot of parts of iOS are open source and several parts of Android are closed (Google branded apps). Does the percentage of opennes matter?

Gruber might be biased but that doesn't mean he is wrong or off-base.

It seems Apple already holds some kind of ownership over ARM. From ARM Wikipedia page:

The Company was founded in November 1990 as Advanced RISC Machines Ltd and structured as a joint venture between Acorn Computers, Apple Inc and VLSI Technology

I think you have to read the full paragraph.

"If you go back to the Pirahã language, and you look at the stories that they tell, you do find recursion. You find that ideas are built inside of other ideas, and one part of the story is subordinate to another part of the story. That's not part of the grammar per se, that's part of the way that they tell their stories. So my idea is that recursion is absolutely essential to the human brain, and it's a part of the fact that humans have larger brains than other species. In fact, one of the papers at the recursion conference was on recursion in other species, and it talked about how when deer look for food in the forest, they often use recursive strategies to map their way across the forest and back, and take little side paths that can be analyzed as recursive paths. So it's not clear, first of all that recursion is unique to humans, and it's certainly not clear that recursion is part of language as opposed to part of the brain's general processing.

He says Piraha doesn't have recursion and that he thinks recursion isn't essential to human languages (thus in contradiction with Chomsky theories), but that it's part of how the brain processes information.

I think that if you follow the "One level of abstraction per function" tip from the "Clean Code" book, and you do a proper naming of your functions this problem disappears.