Google Chrome v15 Released
chrome.blogspot.com
chrome.blogspot.com
Google Chrome was released about 37 months ago. 15 versions were released since then, so Google averaged about 15/37 versions per month, the "Chrome constant." Lynx was released in 1992, around 228 months ago. 228(15/37)=v92. So, were Lynx to have used an approximately similar version enumeration to Chrome, it would currently be at around version 92.
Similarly:
Opera: 178 * (CC) = v72
Konqueror: 180 * (CC) = v72
Firefox: 83 * (CC) = v33
Internet Explorer: 194 * (CC) = v78
Safari: 105 * (CC) = v42
Lynx: 228 * (CC) = v92
What is also good is that the first few comments aren't "why is Chrome bumping the major version number so soon?" like we used to see with every Chrome and Firefox release. Maybe the internet is starting to move past that ;)
But, take into account that Chrome sees much more intensive development than all these projects. Progress is a more fitting measure than time.
1. Think of a secret number between one and ten (or higher if you are a patient person!)
2. Trigger the dialog.
3. Count up to your secret number.
4. Click OK on the dialog.
5. Count up until the page disappears.
6. And that's your secret number!
Basically Chrome freezes after a confirm dialog for the same amount of time that you take to click the OK button. Most people assume it is just the following page is taking a while to load. I'd be interested in how widespread it is - it's affected every instance of Chrome I've come across, on Windows and Linux.
Oh, and please star the issue here if it affect you. http://code.google.com/p/chromium/issues/detail?id=98275
Any setting discovered yet to turn this off?
- Two fingers for scrolling
- Three fingers for in-app navigation
- Four fingers for window management (Exposé, show desktop)
Really easy to understand. Lion made "multitouch gestures" a major advertising point, but honestly... they were better in Snow Leopard. I've reverted with BetterTouchTool, as I could not even do the new "show desktop" gesture.
Chrome is far too touchy about it, though. As soon as you hit the edge, you go back a page. Safari seems to take the velocity and acceleration into account in smarter ways.
I was glad it was no longer sensitive, but I was still wondering why they didn't just implement Safari's page-reveal as you slide back. Then I tried using the Github website, which implements its own transitions using the History API, which worked splendidly on Chrome but was rather broken in Safari.
The best compromise would be to see what sites implement the history API and switch, but I'm satisfied with working side-scrolling for now.
I use apps to integrate them into Gnome Shell. I can press super+"gm"+enter to open up Gmail, or "cal" for the calendar, etc.
There's no reason that you couldn't use this for bookmarks, but I guess Chrome apps allow for larger icons...
Despite my usage, I'd agree that it's essentially just an ideological push by Google to convince consumers that the internet is a viable computing platform in its own right. This computing platform - would you believe it - consists largely of Google's own apps (but it doesn't have to).