If they robbed a bank physically they'd have to have visited the U.S. and it's clear what country they committed a crime in. It is not as clear-cut when they have never been to the U.S.
N900 is interesting in that it is both a tablet PC (or whatever term fits best) and a phone. One less device to carry.
I do not know re. if the UI experience has changed. I can see how N-series tablets can appeal to hackers who like to modify the software that is running on their device. From this POV having a full-fledged Linux on a mobile device is a plus. But N710/N800 was indeed less slick in terms of the user experience than Apple's devices.
If Nokia has innovated in the mobile communication area, why would it be wrong for them to use their intellectual property rights.
A separate question is if intellectual property is a good idea at all. But that is beyond the question at hand.
Patent trolls are just a bad idea, but in this case Nokia may have created a foundation that the Apple is building upon. Companies pay for licensing technology all the time. USB, Firewire, Bluetooth, ...
One could also use SVN and GIT together. That might solve a part of the problem with not submitting fixes because of being in the middle of other set of changes. Develop using GIT locally and submit to SVN repository when ready.
What is experience of HN readers with using a combination of centralised and distributed VCS together? Have you used it and in what situations, if any, is it useful?
There is no big harm in giving something a name. Giving a name also helps if you find a need to reuse it later. Plus a name can give a hint to what this code is for.
but there are some countries/regions still missing from the "Regions" drop-down list which, being a required field, might prevent people from these countries filling out the form.
"... anything that allows arbitrary devices to pretend to be an iPhone and sync jeopardizes email account information--which can be synced to the iPhone--and is a security flaw."
Since we are talking about USB ids here, pretending to be an iPhone would open a "security flaw" only when they have physical access to the computer iPhone's being synced with.
In which case a person already can do whatever they like with it. E.g., just copy your entire hard drive.
Agree, it is too verbose. If I am using vim, I won't be looking for cookbook entry explaining simple tasks. There is probably be audience who'd benefit from the book, but does not appeal to me.
The strength of RDF is in seamless data integration.
Think flexible data mashups (where you don't need to code to the interface of a particular service because they all use same linked data principles).
I have seen people build a simple application and then increase its value by automatically pulling in information from other large source of linked data such as DBPedia and GeoNames.
Fully agree that we need simple and understandable demos that show the value of linked data (assuming for a moment that linked data have business value :).