Lâu lâu Tết nhất mới có hứng viết lách, đọc được review về benchmark Carakan ( Js Engine của Opera ), lại nhân vụ Google ra mắt Google Buzz, muốn viết loanh quanh về Google.
Bài viết thể hiện quan điểm của tui, thế nên sai đúng thì đừng có ném tạ 
Easy meh!
Arrg btw Google met their resistence, their currently resistence might be around 750-800$, so buy it fast =)
It's been an exciting nine months since we launched the Google Chrome browser. Already, over 30 million people use it regularly. We designed Google Chrome for people who live on the web — searching for information, checking email, catching up on the news, shopping or just staying in touch with friends. However, the operating systems that browsers run on were designed in an era where there was no web. So today, we're announcing a new project that's a natural extension of Google Chrome — the Google Chrome Operating System. It's our attempt to re-think what operating systems should be.
Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.
Speed, simplicity and security are the key aspects of Google Chrome OS. We're designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware and security updates. It should just work.
Google Chrome OS will run on both x86 as well as ARM chips and we are working with multiple OEMs to bring a number of netbooks to market next year. The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel. For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform.
Google Chrome OS is a new project, separate from Android. Android was designed from the beginning to work across a variety of devices from phones to set-top boxes to netbooks. Google Chrome OS is being created for people who spend most of their time on the web, and is being designed to power computers ranging from small netbooks to full-size desktop systems. While there are areas where Google Chrome OS and Android overlap, we believe choice will drive innovation for the benefit of everyone, including Google.
We hear a lot from our users and their message is clear — computers need to get better. People want to get to their email instantly, without wasting time waiting for their computers to boot and browsers to start up. They want their computers to always run as fast as when they first bought them. They want their data to be accessible to them wherever they are and not have to worry about losing their computer or forgetting to back up files. Even more importantly, they don't want to spend hours configuring their computers to work with every new piece of hardware, or have to worry about constant software updates. And any time our users have a better computing experience, Google benefits as well by having happier users who are more likely to spend time on the Internet.
We have a lot of work to do, and we're definitely going to need a lot of help from the open source community to accomplish this vision. We're excited for what's to come and we hope you are too. Stay tuned for more updates in the fall and have a great summer.
Posted by Sundar Pichai, VP Product Management and Linus Upson, Engineering Director
The Google Update process was the bane for many Internet users as it seemed to come up again even if it was disabled on the computer system. The process googleupdate.exe was running all the time on the computer system trying to connect to Google to see if there were any updates for Google software available. It could even happen that the updating process was still running if no Google software programs were installed on the computer system.
It also did feel strange that Google needed a process to update their programs while other companies like Mozilla did not. Especially if the only software by Google was their web browser Google Chrome.
Google has announced changes yesterday that will please many computer users. They basically changed Google Update from running in the background permanently to a process that would check for updates periodically which basically eliminates the googleupdate.exe process in the background as it will terminate after the check for updates.
Google's Cron Tasks
Users can check the Task Scheduler in the Windows Control Panel to change the frequency of the update checks. The Google team points out that the process might be running continuously on some computer systems if problems are encountered with the task scheduler and Windows Services.
I hope that all of you will be happy reading this announcement.
Starting today, I'm going to resume my HidePost project, I'll try to fix all known problems ( excerpt bug, feed, level bug and somemore ), and maybe, some new features.
I've never used any subversion system to develop a program before, so I'm going to learn how to use it, by updating HidePost in google code ( you may find my project in google code, but I'll not support anything there, I'll only support the version that release in official Wordpress's plugin ).
At last, my resuming didn't mean that there will be a HidePost version release in next few weeks, but it'll release, someday.
A few months back, we announced some pretty big upgrades to Picasa and Picasa Web Albums for English-speaking users in the U.S. On the PC side, we rolled out a brand-new version of Picasa, with a slew of new tools like effortless web sync, movie editing, and photo-retouching capabilities. On the web, we launched "name tags," a new feature that automatically helps organize your photo collection based on who's in each of your pictures.
Today, just in time for your holiday snapshots, these changes (and more!) are available in all of the 38 languages we currently support. If you've been waiting to try the new photo-collage feature in Picasa, or been curious to see how clustering technology can automatically find similar faces across your photo collection, now's the time to download Picasa 3.1 or opt in to name tags on Picasa Web Albums.
Of course, having a truly global audience sharing and commenting on photos is one of the things that makes Picasa special. The people and places you'll spot on our Explore pageattest to this, as do the multilingual comments users receive on their most popular public albums. That's why we just launched automatic comment translation on Picasa Web Albums, which harnesses Google Translate to make sure you know that "美麗的落日" means "Beautiful sunset!"
In fact, if you look closely, you'll see that we've recently rolled out a number of other small but meaningful changes across Picasa Web Albums, in all 38 languages -- ranging from improved sharing to better video playback. Swing by the Google Photos blog to learn more about what's new.
(Or, if you speak British or American English, Dutch, French, German, Italian, Japanese, Korean, Polish, Brazilian or European Portuguese, Russian, Spanish, Simplified Chinese, Traditional Chinese, Turkish, Danish , Finnish, Norwegian, Swedish, Bulgarian, Catalan, Croatian, Czech, Greek, Hindi, Hungarian, Indonesian, Latvian, Lithuanian, Romanian, Serbian, Slovakian, Slovenian, Tagolog, Thai, Vietnamese, or Ukrainian, just visit Picasa Web Albums and see for yourself!)
via Official Google Blog: Picasa 3 (and name tags) go global.
Google vice president Marissa Mayer announced Google Chrome is coming out of beta in an interview with Michael Arrington at Le Web 08. The Google’s open source browser has a number of eager customers, including OEMs who can’t offer the browser until it is in full release. Chrome’s Windows client has been in beta since its roll out 3 months ago, and with the new move will likely spur bundling with Google Toolbar and Google Apps.
Chrome’s official release comes at a time when Google is accelerating efforts to redefine the browser around open Web standards while adding rich media and secure code extensions. Google’s open source Native Client project is just one possible future for the Chrome platform, where applications can run in a browser but incorporate native code modules. For example, this would allow developers to perform image processing on the local client without requiring round trips to the server.
In recent weeks, Google has released a number of enhancements via the Gmail Labs project. A GTalk video chat client requires a 2MB plugin that appears to incorporate proprietary Flash technology as well as other early versions of open Web standards. Another Lab offering creates a Tasks tool that can automatically add emails as items with a keyboard shortcut from within the email item. Other Labs tools include gadgets to view and create Google Calendar items and Google Documents from within the Gmail window. A Google gadget allows third party developers to add their own Labs code.
via Google To Take Chrome Out Of Beta.
Google Reader
Google has begun to push out an updated interface to Google Reader users. The new look does away with much of the color seen in previous iterations of the RSS reader, while setting up a foundation for a more streamlined and customizable navigation system.
Part of that navigational change now hinges on small widget-like enclosures, which users can collapse down to take up less space. This is quite similar to what's being done over on iGoogle, and on Gmail to some degree, which could signal the future support for third-party widgets. Considering users can spend hours using the Web app, this could add extra utility, or simply carve out a little more space for ad units.
Each enclosure has its own contextual menu which lets you tweak sorting options on a per-subscription basis. There's also a new option to hide and show the read counts, which will let you feel less guilty if you're coming back to feeds you haven't checked in long time.
Google Reader new look
The new Google Reader is a little less blue, and now features collapsible navigation on the left-hand side, opening it up to possibly handle widgets in future versions.
(Credit: CNET Networks)
Another big change is the automation of feed bundles. Since October of last year, Google has provided groupings of feeds that users can subscribe to at once. These were chosen by Google staffers, which is now a completely automated process done with an algorithm. Google has not said if these feed choices are coming from Google Reader subscription numbers in particular, or from other company properties like search, iGoogle, and the Google toolbar. Nonetheless is means bundles will be faster to update with new feeds. There is, however, not an option to "subscribe" to these bundle feeds to get new recommendations as they're added--something I'm hoping will come in a later release.
If you don't yet have the new interface, just check back later. Out of three of my Google accounts, it's only live on one. Typically Google gets out new features to everyone within about two days.
via Google Reader gets a cleaner, minimalist look | Webware - CNET.
Google has published its plan to build into Chrome what is arguably its most requested feature: the ability to accept extensions that can customize how the open-source Web browser operates.
And guess what? Google's dependence on advertising notwithstanding, one of the extension examples the company points to is the ability to block advertisements.
The Chrome extensions document, spotlighted Saturday by Google programmer Aaron Boodman, doesn't include a timeline, but it does shed light on why the project is a priority for Chromium, the open-source project behind Chrome.
"Chromium can't be everything to all people," according to the document. "User-created extensions have been proposed to solve these problems: the addition of features that have specific or limited appeal; users coming from other browsers who are used to certain extensions that they can't live without; bundling partners who would like to add features to Chromium specific to their bundle."
When Google launched Chrome three months ago, it promised a Chrome extensions framework. Extensions are a popular feature of Chrome's most likely rival, Mozilla's Firefox, and one very popular extension is AdBlock Plus.
And AdBlock makes a specific appearance on the list of extension uses that Google said it would like to support eventually:
• Bookmarking/navigation tools: Delicious Toolbar, StumbleUpon, Web-based history, new tab page clipboard accelerators.
• Content enhancements: Skype extension (clickable phone numbers), RealPlayer extension (save video), Autolink (generic microformat data--addresses, phone numbers, etc.)
• Content filtering: AdBlock, Flashblock, privacy control, parental control
• Download helpers: video helpers, download accelerators, DownThemAll, FlashGot
• Features: ForecastFox, FoxyTunes, Web Of Trust, GooglePreview, BugMeNot
Demand for extensions is real.
In an unscientific CNET News poll about why people don't use Chrome, about 19 percent pointed to the lack of an extensions feature. And on Google's issue tracking site for Chromium, a Chrome extensions feature is the top-requested item.
"Of all the Firefox plug-ins, this is the one essential one," said Firefox user Ole Eichhorn. "Chrome is faster until you factor in all the cruft that gets downloaded as ads, then it isn't faster anymore. When Chrome supports AdBlock, it will be the winner, but until it does, Firefox is the only choice."
In its document, Google described some of its goals for Chrome extensions. The extensions should silently update, just like Chrome does. They should be isolated for security reasons and only get access to resources it's entitled to use. Installation should be easy, taking only two clicks.
They should permit rich user interface options--rich enough to implement some parts of Chrome as extensions, Google said. Among the interface options should be "toolbars, sidebars, content scripts (for Greasemonkey-like functionality), and content filtering (for parental filters, malware filters, or AdBlock-like functionality)," Google said. Some interfaces will require the user to grant specific permissions, such as "access to the history database" or "access to mail.google.com," Google said.
Google will play a major role in extensions, providing a central service that can be used to issue updates and to blacklist "malicious or harmful extensions" so the browser won't use them.
"It's likely in the future we may want to provide a consumer front-end which would allow users to more easily find the most popular, highest quality and trustworthy extensions," Google also said.
Sorry if it sounds like I'm drinking the Google Kool-Aid here, but I switched from Mozilla Firefox to Google Chrome as my default browser for the very reason Google's executives said we should: speed.
Years ago, Firefox won me over chiefly with plug-ins, tabbed browsing, and some security advantages. But using Chrome removed a bit of friction from Web I hadn't realized was there. It felt like discovering I'd been driving with the parking brake on just a bit.
Here's what coaxed me away: Chrome starts way faster than Firefox. Web pages load faster when I type in an address or click a link. The Omnibox--Chrome's combination location bar and search box--often gets me where I want to go at least a keystroke faster, and I'm not terribly worried aboutsending Web navigation and search data to Google.
Individually, a few tenths of a second here or there doesn't make much difference. But it adds up fast. I spend hours a day using the Web--not just browsing, but also uploading photos, issuing instructions to my bank, editing documents online, and posting comments. As the Web gets more complex and more deeply embedded in my life, waiting for it gets more annoying.
I hadn't set out to convert to Chrome. I just wanted to see how well it worked, so I used it to run my personal e-mail while at work. Then I added in reading RSS feeds. After a few weeks, I noticed that I was manually copying Web addresses to Chrome and realized that my subconscious mind had made its decision. So last week, I set it as my default browser, despite a range of criticisms (see below).
After I told Mozilla Foundation Chairman Mitchell Baker about my experience, she sounded a bit crestfallen. "We've been increasing our focus on performance for some time. Maybe comments such as yours will increase that," she said.
Faster stripped-down Firefox
More to the point, Mozilla suggested I try a fresh installation of Firefox, one that's not burdened by those pesky extensions. I hadn't been running a large quantity, but I started with a fresh reinstallation of Firefox 3.1 beta 1.
I have to say that Firefox picked up the pace a notch. But I compared it again with Chrome on many Web sites I use daily and a variety of others, and with the exception of Flickr and My Yahoo, I still found Chrome snappier.
Of course, disabling extensions is a shame, given that it's one of Firefox's big advantages. Google has promised an extensions framework at some point, and it's the top-requested feature, with 381 people having starred it as a priority in Google's issue-tracking system for Chrome.
Reinstalling Firefox also reminded me of a feature in the forthcoming Firefox 3.1 that I was happy to leave behind: tab-switching behavior. I'm a big fan of keyboard shortcuts, and use Ctrl-Tab hundreds of times daily to switch between browser tabs. I loathe the new Firefox mechanism, which switches to your most recently used tab rather than cycling one tab to the right, and showing a miniature preview version of the Web page instead of actually switching tabs. I don't know if others' brains work differently, but the new mechanism leaves me completely lost in a sea of tabs, forcing me to use the mouse, which slows me down.
I reverted to the earlier tab-switching feature by adjusting Firefox's behavior thus: First, type "about:config" into the address bar, then move past the warning message, then type "ctrlTab" into the "Filter" box, then double-click first on browser.ctrlTab.mostRecentlyUsed and then on browser.ctrlTab.smoothScroll to set them to "false," then restart the browser.
Meanwhile, though, Chrome cycles the way I like, and in another nice move, it opens new tabs immediately to the right of the page I'm reading when I middle-click to open a page in a new tab. That conveniently groups related tasks together.
Off-color remarks
Here's what's keeping me an active Firefox user, though: Chrome's lack of support for color profiles.
Most images on the Web are encoded with a color scheme called sRGB, but there are others out there includingAdobeRGB and Microsoft's scRGB that can show a much broader range of colors. I'm a photography buff with an eensy-weensy photo business, so I prefer images to look as good as possible on the Web.
Apple's Safari was the pioneer for color management, and Firefox added color profile support with version 3.0 if users manually enable it. With version 3.1, Firefox applies color profiles for images that have been tagged with one. As a result, images on my high-gamut monitor at home look fine in Firefox, but in Chrome they're hideously garish and oversaturated. It's a showstopper for me when I'm doing anything photo-related on the Web.
I recognize my color preference is at odds with Google's performance push. Mozilla programmers found thatsupporting color profiles slowed Firefox 20 percent to 30 percent, though they reduced that number 4 percent to 5 percent with testing. Eventually, to get it lower, they went with a third way, applying color profiles only for tagged images, which caused only a 1 percent performance hit.
(Credit: Paul Ford)
But Google hasn't even gotten to the stage of evaluating performance effects. "I don't see how any sites could depend on this feature if it's missing/disabled for 90 percent of users," said Chrome Program Manager Mark Larson in a response to arequest to add color management to Chrome, referring to the fact that color management is missing in Internet Explorer and not enabled yet in mainstream Firefox. "I'm all for it, but it's definitely not a release priority."
Other gripes
Chrome has other issues that frequently annoy me. Allow me to share.
• There's no plug-in mechanism. I'm getting by, but there are some I'd like to have back.
• Bad support for RSS subscription feeds. In Firefox, a site with an RSS feed gets an icon in the address bar, and clicking it signs me up for the subscription. In Chrome, I have to hope someone manually put a link on the page, but usually I just move back over to Firefox.
• When I launch a new window, Chrome never starts it maximized, even if the last window was. This is a bit surprising, given Google's laudable emphasis on showing as much real estate as possible. I always want my browser page maximized. On a related note, I miss Firefox's maximized mode (hit F11 to try it out).
• Chrome doesn't respect changing monitor sizes well. When I move to a dual-monitor setup, Chrome stomps all over Windows' task bar.
• Selection and copy-paste issues. When I'm selecting text in Chrome, I don't like how the blue selection box spreads wider than the text box. And when text is selected but I missed a few characters, I don't like the inability to use Shift-right arrow keys to extend the selection a bit.
Those are my issues, and I'm sure other people have their own. What's keeping you from switching to Chrome? Vote in the poll above and share your thoughts below.
Comments