I've recently used angular (angularjs.org) and I found that it felt strange, so it took a steep learning curve, but though steep it was rather short, and at the top was bliss!
1,113 karma · joined March 23, 2008
Then you're quoting incorrectly. (Notice how I quoted only a section of your original, in my reply here.) Proper correspondence includes trimming the quoted section. Not simply leaving the whole thing there.
Because you're wrong. It is a comparison matrix, and not a product page. http://www.google.com/phone lists many different android phones, by many different manufacturers, and offers comparisons.
The Nexus S product page is http://www.google.com/nexus
But that's not true. My android phone has a 'share' button in the gallery, from which I can choose a variety of destinations, including Picasa and Facebook (and any other app that registers itself as a picture sharing endpoint).
http://googlewebmastercentral.blogspot.com/2009/02/specify-y...
Or even simpler, if you're going to go reconfiguring apache, just set up your virtual hosts right, so that only the name you want to use is actually used.
"I'll bet that if you pick any random number from 1 to 20, I can guess it. If I miss, I give you a dollar. If I get it right, you give me ten."
Over 100 trials, you would lose $1 92 times, but gain $10 18 times: net gain of $88. It works almost all the way down to getting $5 per correct guess.
Intuition would tell the guesser that they've got a nineteen-to-one chance of gaining a dollar. You know (in theory) they've got only slightly better than a one-in-five chance of winning.
In the case of HTC phones with Sense, they have to add a lot of engineering work between "Android version is available" and "that version has Sense added". They need to make sure all the hardware drivers still work, update them for updated kernels, etc.
If the phone is a "Google Experience Device" then it's very close to the original source, and should get updates sooner than the rest.
When the N1 came out, however, people were for some reason surprised about this. There's lots of news about it: http://www.google.com/search?q=t-mobile+%22nexus+one%22+%22n...
Wow, really? Six in a row? I've participated in hundreds of transactions through eBay (over the years) and I can only think of three that I was ever dissatisfied didn't meet the description, or that the description didn't reveal things I considered important (and bad). Two of them were transactions under $10, including shipping.
Can I ask what sort of things you were buying, and what sort of costs were involved (one, you said was $30)?
Whoops, you got me. I of course meant "in the working tree" when I said local. It's just easy to be close, but not quite, right with the terminology.
The term you're looking for is "network effect". http://en.wikipedia.org/wiki/Network_effect
Well, really: "git checkout foo" means:
1) Switch the branch, if foo is a branch.
2) Destroy all local modifications, if foo is a file.
These are two drastically different actions, and they're given the same name. The "rm" command has one name, and does one thing: remove files. It isn't also, sometimes, used to gain access to otherwise inaccessible files. I think, ultimately, the names are the worst part of git for me.
There's checkout, which is ambiguous. I'm used to using "svn revert" in the past, but I have to use "git checkout" to do that ... at least for individual files. If I want to do them all, "git reset" is, usually, what I'm looking for in this case. The "git revert" command also exists, but does something different (apply past commits in reverse). Git has three different commands for the "put the files back the way they used to be" concept (at least, are there more I don't know about yet?).
Then there's "the in between thing". From the man pages:
If you're doing "git add" then it "updates the index using the current content found in the working tree" and "the content staged for the next commit". If you're doing "git reset" then you have to ask for "--mixed" or "--hard" in order to "resets the index". If you're doing "git diff" then you have to ask for "--cached" to get the "changes you staged for the next commit". Then there's "git ls-files" which talks about "the file listing in the directory cache index" and "--cached Show cached files" and "--stage Show staged contents object name". Wait, "--cached" and "--staged" are different options?
So what is it? Is it "the index" or "the stage" or "the cache"? Do I have to pass "--hard" or "--cached" or "--index"? Whoops, I made that last one up! But wouldn't it be nice if it had one name, and that's always the name I used to refer to it? I know there's something between "files I edit on disk" and "files in the repository" but the documentation does anything but make it clear what that something is even called.
The title of the post on HN is "Google scraper may have to be permanently retired, thanks to a change at Google". Big difference.
I have definitely done occasionally awesome things, like amending commits with small noticed typos before pushing, stashing is totally awesome, cheap branches are mostly convenient. But there's _so many_ layers, and nothing (that I've yet discovered) that lays it out in a manner that makes it easy to understand.
I've a lot of past experience with Subversion. I used SVK for a while, so I could get local dev branches and commits without pushing to the central repository. But git continually confuses me. Plenty of it is un-learning other VCSs (no, to get rid of that mistaken change, I don't revert the file, I checkout the file. revert is a command but it does wholly other things.) Not to mention the many names for things. Local, staged, cached, indexed?
Yowza.
The address bar is not always shown. It scrolls away as you leave thet op of the document.
Your comment "At the bookmark view, tapping on the address bar" doesn't seem to make a lot of sense. If I ignore the bookmarks part, for me on Nexus One, tapping the address bar definitely does bring up the soft keyboard.
Overall, I'm very excited about the progress this shows. I'm sure getting it to work at all was the hard part. Hooking up a few keypresses to do the actions you expect is surely coming, and soon.
I think you mean: evolution doesn't always mean _adding things_. Taking away something that causes a net loss is evolution. Much like, say, the tail in certain higher primates. Or the ability to install and run absolutely anything (including malware, trojans, and viruses).
(Whether a thing causes a net gain or loss is its own entire argument, of course.)
Laziness, of course, is a problem also.
Why? Can you explain the rational reason why a retail store would want to keep someone from paying full price for their items?
Specifically: What happens when Content ID identifies a match?
If Content ID identifies a match between a user upload and material in the reference library, it applies the usage policy designated by the content owner. The usage policy tells the system what to do with the video.
So, I'd highly suspect that just now the content owner set the policy. I can't believe that the filter is multiple years out of date, and just now catching up. They wouldn't all be flagged at once, if the processing was that slow.
And I am intentionally not clicking the link because ... it's not a link. I have a greasemonkey script that automatically turns plain text URLs into clickable links. But the text in your post is not a URL. It's a domain and a path, but with no scheme it is not a URL.
Are any of these 'broken' besides not being quite as pretty? Is any content or feature invisible, unreadable, or unavailable?
a:visited + .sneakydiv { /* ... */ }
Take a look at the photo vs. the debugger snapshot of the "3G" text. The uprights in the G are 3 pixels wide, and display as one of either:
BB G RR G BB G RR G BB G RR G
Thus the point of the article: A "pixel" is either "BB G" or "RR G". There are 800x480 of these. But neither of them is "a pixel" (RBG) like we're used to talking about, it's less than that. There's one (small) green and one (bigger) red OR blue in each pixel.
I had a Nokia N810, with an 800x480 LCD of approximately this size. It was gorgeous. I was expecting something similar, but got this, with my N1. The screen is, easily, the most disappointing part of the N1 in my opinion. The enhanced contrast of the AMOLED doesn't come close to making up for the jagginess of the uneven pixels. Vertical, and especially diagonal, lines just look horrible.
They're all simply better than the metaphor. Obviously a physical magnifying glass held over a piece of paper cannot create or remove information, only scale it.
"Zooming in" in software, however, involves a complete replacement. And at every level, the most(/best) set of information is displayed. When zoomed out at, i.e., Miami, the word "Miami" displayed at a readable size covers up nearby towns. When zoomed in a bit, there's more small towns that can be displayed (collectively covering up Miami).
Moreover: this is probably even the right/best thing to do. At a wide zoom, you probably want the big cities as landmarks. Slightly tighter in, one is more likely to be familiar with the area, and want to know the smaller details. Tight enough again, Miami is the only thing left in view, so it is labeled.
This is not broken, or bad in any way.