As I read it, that technology doesn't provide haptic feedback, it just tracks gestures.
HN user
afy
If you look at the byline, it is very interesting that this was co-written by Juan Manuel Santos (for other readers: the current president of Colombia).
Wrong thread! :)
There are parts of south america where vosotros is used, but I think what the parent was getting at is that it is not technically considered a 'tense', but rather a 'person' as in e.g. 'third person'
I think that is just to refer to the instruction set that is being emulated (8-bit AVR - see Erin Ptacek's blog post about it on sockpuppet.org), used by the microcontroller on many Arduino boards
I agree that the first number shouldn't be a rate. x per y implies a rate though like 26 kilometres per hour or 16 miles per gallon.
Agreed! The thing I found most confusing in the title though is "At the same time, Bing gained 4.2% market share."
Over what period of time? I am guessing that it is over the past year but the first part specifies a rate and not a specific time interval.
Actually, in the final Pirlo did not have the ball the most for Italy because he was closely marked by Xavi. A central defender, Barzagli got more touches than him. It would be interesting to see the graph of that match.
Also your final assertion that teams set themselves up so their best players get the ball the most seems a bit off to me. Consider FC Barcelona. Lionel Messi is arguably their best player but you would be hard pressed to find a game in which he has the ball the most since he plays high up on the pitch as an attacker.
I agree with you in that single match analysis using this technique doesn't really produce any new insights. I think this analysis would be very interesting when comparing between different games however. e.g. comparing Italy's match against England where Pirlo was effectively given free reign of the pitch to their match against Spain where he was shut down for most of the match. I would love to get my hands on some raw data from Optasports!
It is my understanding that that is what is meant by submit a patch!;)
The whole article hinges on the lines of code metric being an accurate metric for how productive a team is. But how many programmers would be happy if their bosses paid them per line of code?
I would be inclined to agree with the premise of the article, but the evidence given is flawed at best.
The problems that the article addresses are not the ones that I would have chosen.
I think the main problem that new users to Linux have is the steep learning curve. The author dismisses user friendliness with the implication that the only reason Linux is difficult to learn is because it is different.
The analogy given is vi versus a standard Windows word processor. I am not disputing that vi is a much more powerful program, but I am saying that it is much harder to learn than Microsoft Word. Using Word, without knowing the keyboard shortcuts, you can use the toolbars to do what you want and in doing so you learn the shortcuts, most of which are printed next to the menu items.
Using vi, without knowing any keyboard shortcuts, you can do exactly nothing. Arguably vi is much better off without toolbars because they take up a lot of screen real estate and would be difficult to implement from a terminal window, but that does not mean there is no such thing as user friendliness. Another problem is the problem of hardware support[1], which the author does not address at all.
Having said that, I will agree with his point that since it doesn't really matter much to (with notable exceptions) most developers what features people not already using Linux would like to see, development is centred around people already using Linux and on more gentle slopes of the learning curve.
In mathematics there is a well defined right and wrong, but in history there are often competing viewpoints of which none can be dismissed easily. I would say that to pick one as true and discard all the others is folly.