Ioni's shared items in Google Reader

More on Mono, Microsoft, and Novell

Roy Schestowitz — Sat, 18 Jul 2009 08:51:17 PDT

“We could refresh the look and feel of the entire desktop with Moonlight”

–Miguel de Icaza

Summary: A batch of small updates on the Mono/Moonlight situation

NOVELL’S (and Microsoft’s) plan with Moonlight is something that we have warned about ever since Moonlight was first announced. As usual, at the time, certain people dismissed this as something along the lines of "zealotry". The word “zealotry” (like “terrorism”) is increasingly being used to describe “something I don’t like” or “something I don’t agree with” (even protests or noise). The label most commonly fits a minority, so it is conventionally assumed that a majority cannot be “zealous” and strong nations cannot be supporting “terrorism” (which is, by definition, the use of force to accomplish political goals). Most critics of Microsoft are not “Microsoft haters”. On the other hand, Microsoft is a self-confessed "Linux hater", so Linux users are justifiably being defensive. But being a minority with little influence over the media, it is often GNU/Linux which gets daemonised.

Now, arriving at the actual point of this post, the community is rapidly becoming aware of Novell’s Mono-Moonlight intersection, which we covered in [1, 2, 3]. It is nothing but trouble, unless we all support Microsoft and Windows.

Banshee and F-Spot to depend on Moonlight

[...]

Planet Debian points to the news that Banshee and F-Spot is going to depend on Moonlight in the future. Moonlight is forbidden from Fedora. If this happens, Banshee and F-Spot have to be dropped from Fedora.

The FSF, which is against Mono, was very polite in its statement. As Sam Varghese puts it:

The statement conclude by saying that if Microsoft wanted to genuinely reassure free software users that it had no intention of suing them for using Mono, “it should grant the public an irrevocable patent license for all of its patents that Mono actually exercises.”

Watch the pro-Mono spinners in the comments. Here is one interesting comment from LWN:

I can only imagine the violent anti-FSF reaction and hate this will generate (or is probably already generating?) on various forums.

Anything that RMS or the FSF says is usually grounded in solid logic. Everybody would be wise to at least consider it.

As for me personally, and the businesses I am involved with, I would avoid Mono.

Which really saddens me because I like Mono. The language is better than Java, the implementation starts faster, it feels more lightweight, it supports static compilation, etc.

I have been on the receiving end of an IP-related lawsuit and it is an experience which one never forgets.

LinuxInsider quotes some more people, with statements that include:

“If you honestly think this will lead to cross-platform development, then you need your head checked,” wrote Josh in the comments on TuxRadar, for example. “Since when has Microsoft had any sincere interest in cross-platform anything?

“It looks to me like a classic Trojan horse,” Josh concluded, “and Miguel de Icaza is a tool.”

Similarly: “This Mono thing looks a bit like a Trojan horse,” agreed kt on LXer, where the topic was covered in not just one but two separate threads.

Jason has just suggested a new slogan for Mono:

New Slogan Time

Mono: Extending Redmond’s Reach into Proprietary Platforms on the backs of “Open Source” developers since 2001. Also some Linux apps in there somewhere too.

Boycott Mono and Novell. They take away the freedom of GNU/Linux users and turn Linux aficionados into clients of Microsoft. █

The Great Google Doodle Triforce Conspiracy

Michel "WebSonic" Wester — Thu, 16 Jul 2009 13:51:14 PDT

In many well-known programs there are hidden features or messages called easter eggs, being put there by the developers for you to find. Like in some applications from Google: Docs (Cliply), Picasa (bears) and Reader (ninja and the end of internet). But it seems that these ’eggs’ are not only featured in the applications from Google but also in the special Google Doodles. Several Doodles appear to have a symbol in it which looks very much like a Triforce – this could be an easter egg or an artist’s signature, and a hidden reference to the Nintendo Classic Zelda game, where the Triforce appeared. Wikipedia explains: “The Triforce is a triangular relic which features throughout the series as a nearly-omnipotent sacred item representing the essences of the Golden Goddesses. It is made up of three smaller triangles known as the Triforce of Wisdom, Triforce of Power and Triforce of Courage.”

The most recent Doodle to feature a Triforce was the Nikola Tesla logo which was placed on 9th July. You can see the little icon next to the Tesla coil.

Nikola Tesla, July ~~9th~~ 10th 2009

Earth Day 2009

Christiaan Huygens, 2009

Thanksgiving 2008

Halloween 2008
Here, the triforce might have been added later on, or removed... in another version it was not to be seen.

France October 4th, 2008

Olympic Summer Games 2008

Earth Day 2008

Can you find more Google logo doodles with the triforce in them?

[When Michel is not hanging out at Blogoscoped, he’s writing the Dutch blog WebSonic.nl.]

Update: Now Google removed the triforce from logos.

[By Michel "WebSonic" Wester | Origin: The Great Google Doodle Triforce Conspiracy | Comments]

[Advertisement] Google books on Amazon

Confirmed: Novell Puts Mono (and Moonlight) at Centre of the GNU/Linux Desktop

Roy Schestowitz — Thu, 16 Jul 2009 02:57:25 PDT

“We could refresh the look and feel of the entire desktop with Moonlight”

–Miguel de Icaza

Summary: Another new roundup of Mono news

YESTERDAY we wrote about Moonlight and Mono-based applications getting more tightly integrated. We now see it confirmed by Novell employees Miguel de Icaza and Jonathan Pobst [1 2], so our suspicions were correct from the very start. This is all part of Microsoft’s ambition to fill the Web with Silver Lie content and the desktop with .NET/WPF, which in turn imposes a patent tax on GNU/Linux and makes a poorer experience for GNU/Linux users. From ITPro news:

The first version of Silverlight was launched in April 2007, while version 2 arrived in 2008. It runs on Windows and Mac – and even Linux. The latter is developed by Novell in conjunction with Microsoft, a project known as Moonlight.

“[I]n conjunction with Microsoft,” says this article, but the Microsoft/Novell Web site calls it “Microsoft Moonlight”. It serves Microsoft’s interests.

Microsoft’s Anti-Java

In the blog post where Mini Microsoft suggests laying off 15k employees we also find this comment which reminds us why it’s good that Bing is dying. Microsoft uses Bing to smear .NET’s (and Mono’s) main competitor, Java. From the commenter:

“Regarding Bing, I believe there are untrustworthy behaviours under the hood, specifically black list result filters. Try this searching for “transferhandler.export to clipboard swing”. Google finds about 100 results all related to Java. Bing finds exactly two results. One is my comment on this subject elsewhere and the other is in French. How can it be possible without deletion of “things Java” ?”

This is not surprising because Microsoft applies the same type of treatment to all major competitors of Microsoft, GNU/Linux included. See our previous posts on the subject, e.g.:

Attacks on Stallman

For the past fortnight or so (shortly after Stallman’s official statement on Mono and C#), Stallman has come under attack from many directions, usually from defenders of Mono or users of Mono (including Canonical employees). He is still not impressed by Microsoft’s “Community Promise” (CP) [1, 2, 3] and this makes him no friends. Stefano Forenza wrote about these attacks on Stallman only to be called “misguided” by Caonical’s CTO.

The first meme being directed to Richard Stallman for citing ‘eMacs virgins’ in a speech and the other one only gods knows whom.

While the latter is just is yet another generalist campaign (like the infamous “hey, even double click is patented!”) the first is a frontal attack to Richard Stallman as a person: knives coming out all of a sudden.

Even the Canonical CTO blogged about it.

While the video isn’t available yet, I have big doubts there is something even remotely offensive in such Stallman talk. It’s very easy to take feminism as an excuse, as many people (not just girls) will jump in no-matter-what without even knowing what it’s being talked about.

The new method in place seems to be that if you support Stallman and support his stance on Mono, then you’re also a chauvinist. It’s not said explicitly, but it is being implied that to be associated with Stallman is also to accept his sometimes-tactless humour/modest proposals.

Sam Varghese correctly points out that Mono’s most vocal defender inside Debian is himself quite chauvinistic. That person is Josselin Mouette.

Mouette, it may be recalled, is the developer who had posted what were considered sexist posts to the Debian project mailing list meant for important announcements for developers.

(Mono is an open source implementation of parts of Microsoft’s .NET development environment; many sections of the FOSS community fear that Mono may prove to be a patent trap down the line as .NET is totally Microsoft technology. Recent statements have done little to dispel this impression.)

I asked the Debian leader Steve McIntyre a few queries about the Mono change and he, as always, sent back straightforward replies. McIntyre, I may add, has always been open and upfront in dealing with iTWire.

But after Free Software Foundation chief Richard Stallman called the Debian move risky - he based the statement on the inference that a decision on including Mono in the Debian default install had already been taken - Debian spokesman Alexander Reichle-Schmehl decided that the project had to speak up and did so by trying to explain things through a post on his blog.

For those who have not been following the whole Mono kerkuffle (a lot has happened recently), here is an excellent summary, which concludes thusly:

Well there are issues around Mono, including patents. This means that some people, myself included now refuse to use it. Those that are pro-mono don’t seem to understand exactly why everyone isn’t shouting hosannas over their projects. Indeed one of them classified Tomboy as ‘An Exciting Program’, which stunned me. Tomboy? Exciting? I didn’t think so.

It is “exciting” for Microsoft, that’s for sure. Its APIs spread to the competitors’ platforms, which makes Microsoft more powerful. It does not bother Novell. █

“Our partnership with Microsoft continues to expand.”

–Ron Hovsepian, Novell CEO

“[The partnership with Microsoft is] going very well insofar as we originally agreed to co-operate on three distinct projects and now we’re working on nine projects and there’s a good list of 19 other projects that we plan to co-operate on.”

–Ron Hovsepian, Novell CEO

Releasing Debug Panel for GWT

Leslie Hawthorn — Wed, 15 Jul 2009 17:19:28 PDT

A few years ago, we released GWT, the Google Web Toolkit, which allows code to be written in Java using your favorite editors and then compiled into JavaScript that runs smoothly on host browsers. Today, we're releasing some additional debug tools to make troubleshooting easier. See the post on the GWT blog for more details!

By Jeff Bailey, Software Engineering Team

Tip: Recover your password via text message

The Gmail Team — Thu, 09 Jul 2009 14:00:42 PDT

Posted by Cristelle Blackford, Online Operations Strategist

Even the best of us forget our passwords from time to time. In fact, recovering passwords is one of the top reasons people visit the Gmail Help Center. To help with these situations, we recently added the ability to recover your password via text message.

To turn this on for your account, just sign in, select 'Change Password Recovery Options,' enter your cell phone number and click 'Save.'

Next time you forget your password, enter your username on the password-assistance page, and Google will text you a recovery code. No need to check another email account or even leave the page.

In general, it's a good idea to add as many password recovery options to your Google Account as possible, like a secondary email address and security question. And don't forget to keep them up-to-date.

How To: Install Windows Mobile 6.5 Right Now [How To]

John Herrman — Sat, 06 Jun 2009 11:30:00 PDT

The bad news: Windows Mobile 6.5 won't be coming out for a while, and you'll be expected to buy a whole new phone to get it. The good: You can actually install it today, on your HTC phone. Here's how.

Why should you upgrade to Windows Mobile 6.5? Disregarding the mixed coverage the OS has gotten—which tends to compare it to more modern software like iPhone OS and Android—6.5 is much, much ~~better~~ less terrible than 6.1, especially for touchscreen phones You've probably heard about the new graphical start menu and fantastic Titanium home screen; they're great, but there's a lot more to appreciate. IE has been updated; all menus are now finger-friendly; the whole system has inertial scrolling; there's been a system-wide cosmetic refresh. That's not to mention the upcoming Windows Mobile Marketplace, Microsoft take on the App Store. On top of that, at least in my experience, it's pretty snappy.

Dozens of Windows Mobile 6.5 Beta ROMs are floating around the tubes, collected, tweaked and prepared for your use by the kindly souls over at XDA Developers, from whom I've adapted this How To. Despite their unofficial-ness, they're really quite good—the fancy new interface elements are buttery smooth, and as a whole, and enough bugs have been stamped out to make 6.5 solid enough to use as your day-to-day OS.

This How To is based around my experience with a GSM HTC Touch Diamond. The process is largely the same between the few handsets that can run 6.5, but for the sake of brevity, I'm sticking to one handset, and its QWERTYed brother, the Touch Pro. For further guidance on other phones, head over to the XDA forums (CDMA Touch and Pro, Touch HD, Sony Xperia, Samsung Omnia)

Also, the necessary disclaimer: this tutorial reaches deep into your phone's software, which means there's a (slim) possibility that you'll brick your phone should anything go wrong. If you're worried, read up on the risks here. Otherwise, follow closely and you—and your phone—should be just fine.

What You'll Need:

• An HTC Touch Diamond or Touch Pro (GSM only. Folks with CDMA handsets—that's you, Sprint and Verizon—go here or here.)
• A (free) account at XDA Developers
• A Windows Mobile 6.5 ROM (Lotsa choices here: Diamond, Pro)
• A Windows PC, set up to sync with your handset
• A device flashing utility (Both)
• A bootloader (Diamond, Pro)
• A device radio (Diamond, Pro—Make sure to download from the "Original" list, not the "Repacked" one.)

Before you get started, you'll probably want to back up your contacts and personal info. I'd recommend PIM Backup, which I've used for years. Or you could try Microsoft's new, free online service called My Phone. This How To will replace all your device's software, so if you have anything worth keeping, you'll need to back it up.

Installing the bootloader:

Many of you have probably updated, or "flashed" your devices before, but this will have been with an official, signed utility from either your carrier or handset manufacturer. What we're doing today is installing unofficial software, something which your handset isn't currently set up to do. Our first order of business, then, is to install a new bootloader, called HardSPL, on the device, which will allow your handset to load software from third parties, i.e., your sweet, sweet Windows Mobile ROM. Let's go:

1. Connect your phone to your PC, and establish an ActiveSync (on XP) or Sync Center (on Vista, or Windows 7) connection to your device. You don't need to set up any sync rules—just makes sure the connection is active. You can check this by looking for a bi-directional arrow in your phone's taskbar.

2. Extract the bootloader you've downloaded, and note the location (see "What You'll Need" for links)

3. Find your extracted files, and run the executable file (usually called "ROMUpdateUtility.exe" or something like that.

4. Follow the instructions, carefully. The software performs lots of checks to make sure you don't goof this up, but make sure you a.) have at least 50% battery left in your phone b.) the correct bootloader c.) a host computer that won't shut off, go to sleep or otherwise interrupt the process. Heed! Or else there may be bricking.

5. Wait! You'll see paired progress bars on your phone and computer screen. This part of the process doesn't take that long, since you're only updating a small piece of software.

6. Restart your phone. The small text in the corner of your Windows Mobile splash screen will have changed to something unfamiliar, but don't worry about verifying your new bootloader. If you ran the utility to completion and the device restarted on its own, it's more or less a sure thing that you're upgraded.

Installing a new device radio:

This is the most esoteric part of the process, so I'll try not to get too deep into the nuts and bolts. Basically, your device has firmware that manages its various antennae, letting you connect to cellular networks, GPS, etc. Installing a fresh Radio onto your device usually won't make much of a change in how your phone works. it just lets us—or rather, your soon-to-be mobile OS, manage your phone's communication capabilities freely. Some radios can improve reception on certain networks, or even connect to entirely new mobile bands. For more info on that, I'l refer you again to XDA.

You'll probably notice that this process is seems an awfully lot like the last stage: that's because it is. Since we're "flashing" different parts of your phone's software in each step, the core utility, and general technique, is quite similar. Anyway!

7. Pair your phone with your PC, like you did in step 1.

8. Extract your downloaded radio files and note their location

9. If the radio came with its own bootloader, skip to step 12.

10. Extract your downloaded bootloader, noting location.

11. Copy the extracted radio file—it should have an .NBH extension—to the directory where you've put your bootloader.

12. Run the bootloader, as in step 3.

13. Follow the instructions, as in steps 4 and 5.

14. Let the phone restart. Nothing much will have changed, but you may need to perform some minor network setup. Don't worry too much about that now, since you're about to wipe your whole device.

Flashing the ROM, i.e. Installing Windows Mobile 6.5

This is when we get down to actually installing our new OS. This is the step that'll take the longest, and it's the biggest leap of faith, since you're replacing your device's main software. Luckily, if you've come this far, it'll be a snap. Same process, different .NBH file. Onward!

15. Pair your phone to your PC (this is the last time! promise!)

16. Extract your downloaded bootloader, again, to a different location. (Or you can use the same copy you used to flash your radio; just make sure you delete the radio file from the directory)

17. Extract your Windows Mobile 6.5 ROM, which should be an .NBH file of about 80-100MB, to the same directory that your bootloader is in.

18. Run the bootloader, and follow the instructions. Same warnings as before—don't let your PC or phone sever the connection at any point.

19. Sit and wait. This time it'll take a bit longer, but shouldn't top 15-20 minutes.

20. Your phone will reset, and you should see a fresh Windows Mobile 6.5 splash screen. It might look hacked or unprofessional—don't be alarmed! The guys who so graciously put together these ROMs, which often take a good deal of tweaking, leave their marks on the software in various ways. Anyhoo, you'll have to let your phone run through a set of initialization routines for a little while. Just follow along.

21. WinMo should automatically guess your carrier and apply the appropriate connections settings. If not, you can do it from the device's Settings page, found in the top level of the new start menu. As for the settings parameters, Google is your friend.

Conclusion:
Congratulations! You are now the proud, semi-legal owner of a Windows Mobile 6.5 smartphone! It's hard to imagine wanting to switch back, but if you do, just repeat the above process with a different ROM. There are plenty of 6.1 installs, including the official carrier versions, available from the same place you found your 6.5 download.

Resources:

• XDA Developers
• ModMyDiamond

So that's about it! Please add in your experiences in the comments-your feedback is a huge benefit to our Saturday guides. Good luck with your flashing (firmware only, please), and have a great weekend!

Google Chrome Adblocker

Martin — Tue, 02 Jun 2009 14:52:27 PDT

The first extensions for the Google Chrome browser are finally being released and available for users who want to add functionality to the web browser that everyone is calling Google Browser. There is still no build in extension manager in the web browser which makes the installation of the extensions more complicated than other web browsers.

The first extension to block advertisement has been around for a while but the installation has changed with the official release of Google Chrome 2. Adsweep can be compared to the popular Firefox add-on Adblock Plus. Google Chrome 2.x users need to download the file AdSweep.user.js from the official AdSweep website. They then need to create a directory with the name User Scripts in their user profile. Windows XP and Windows Vista users find the Google Chrome profile folder in the following default locations:

Windows XP user profile directory:

C:\Documents and Settings\\Local Settings\Application Data\Google\Chrome\User Data\Default

Windows Vista user profile directory:

C:\Users\\AppData\Local\Google\Chrome\User Data\Default

Google Chrome needs to be started with a parameter to enable userscripts. This can be best done by adding the parameter to the shortcut of the Google Browser. A right-click on the shortcut will open the shortcut properties of the browser. The parameter –enable-user-scripts needs to be added at the end of the Target field in the Shortcut tab.

The complete command to launch Google Chrome with extensions would then look like the following:

"c:\Documents and Settings\username\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --enable-user-scripts

The website of the Adsweep developers contains additional information to add the parameter to the shell command when opening websites this way.

Tags: adblocker, adsweep, google browser, google chrome, Google Chrome Adblocker, google chrome extensions

Google Docs Adds Docx And Xlsx Support

Martin — Tue, 02 Jun 2009 01:34:55 PDT

Microsoft’s decision to change the default file format in Office 2007 for some of its most popular Office programs has caused some confusion and controversy, especially shortly after introduction. Back then no one was able to open the docx, xlsx or pptx file formats if they would not have Microsoft Office installed. This changed quickly as Microsoft released the Office 2007 compatibility suite for previous installments of Microsoft Office. Users without Microsoft Office were able to work with the new formats in Open Office or use online converters to convert them to traditional Office documents.

The Google Docs team on the other hand was reserved and did not add support for these file formats until now. Today, they announced that they finally added support for both the docx (that is for Microsoft Word 2007 documents) and xlsx (Microsoft Excel 2007 spreadsheets) format in Google Docs.

Support in this case means that users can upload files with the docx and xlsx extension to Google Docs. The size limitations are 500 Kilobytes for docx documents and 1 Megabyte for xlsx spreadsheets.

The document can then be edited in Google Docs just like any other document. There is however no option to save documents to a local computer system in the docx or xlsx format yet. Google Docs will automatically convert the documents to doc or xls format.

Tags: docx, excel, google docx, microsoft-office, office excel, office word, pptx, word, xlsx

Mozilla and Google Announce HTML-Based Extensions

donotreply@osnews.com (Kroc Camen) — Thu, 28 May 2009 10:32:39 PDT

It appears that great minds think alike (or in the case of open-source software and the close-ties between Google and Mozilla, share-alike). Within a week of each other both Mozilla and Google have announced new initiatives to allow for extensions to their browsers to be written using regular HTML / JavaScript and CSS, greatly lowering the bar for developers to join in. Strap on your Mozilla Jetpack and take a peek at extensions for Chrome.

Went Walkabout. Brought back Google Wave.

A Googler — Thu, 28 May 2009 19:08:08 PDT

Back in early 2004, Google took an interest in a tiny mapping startup called Where 2 Tech, founded by my brother Jens and me. We were excited to join Google and help create what would become Google Maps. But we also started thinking about what might come next for us after maps.

As always, Jens came up with the answer: communication. He pointed out that two of the most spectacular successes in digital communication, email and instant messaging, were originally designed in the '60s to imitate analog formats — email mimicked snail mail, and IM mimicked phone calls. Since then, so many different forms of communication had been invented — blogs, wikis, collaborative documents, etc. — and computers and networks had dramatically improved. So Jens proposed a new communications model that presumed all these advances as a starting point, and I was immediately sold. (Jens insists it took him hours to convince me, but I like my version better.)

We had a blast the next couple years turning Where 2's prototype mapping site into Google Maps. But finally we decided it was time to leave the Maps team and turn Jens' new idea into a project, which we codenamed "Walkabout." We started with a set of tough questions:

Why do we have to live with divides between different types of communication — email versus chat, or conversations versus documents?
Could a single communications model span all or most of the systems in use on the web today, in one smooth continuum? How simple could we make it?
What if we tried designing a communications system that took advantage of computers' current abilities, rather than imitating non-electronic forms?

After months holed up in a conference room in the Sydney office, our five-person "startup" team emerged with a prototype. And now, after more than two years of expanding our ideas, our team, and technology, we're very eager to return and see what the world might think. Today we're giving developers an early preview of Google Wave.

A "wave" is equal parts conversation and document, where people can communicate and work together with richly formatted text, photos, videos, maps, and more.

Here's how it works: In Google Wave you create a wave and add people to it. Everyone on your wave can use richly formatted text, photos, gadgets, and even feeds from other sources on the web. They can insert a reply or edit the wave directly. It's concurrent rich-text editing, where you see on your screen nearly instantly what your fellow collaborators are typing in your wave. That means Google Wave is just as well suited for quick messages as for persistent content — it allows for both collaboration and communication. You can also use "playback" to rewind the wave and see how it evolved.

As with Android, Google Chrome, and many other Google efforts, we plan to make the code open source as a way to encourage the developer community to get involved. Google Wave is very open and extensible, and we're inviting developers to add all kinds of cool stuff before our public launch. Google Wave has three layers: the product, the platform, and the protocol:

The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave).
Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves.
The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

So, this leaves one big question we need your help answering: What else can we do with this?

If you're a developer and you'd like to roll up your sleeves and start working on Google Wave with us, you can read more on the Google Wave Developer blog about the Google Wave APIs, and check out the Google Code blog to learn more about the Google Wave Federation Protocol.

If you'd like to be notified when we launch Google Wave as a public product, you can sign up at http://wave.google.com/. We don't have a specific timeframe for public release, but we're planning to continue working on Google Wave for a number of months more as a developer preview. We're excited to see what feedback we get from our early tinkerers, and we'll undoubtedly make lots of changes to the Google Wave product, platform, and protocol as we go.

We look forward to seeing what you come up with!

Update @ 7:07PM: The video of the Google Wave keynote presentation is now available:

Posted by Lars Rasmussen, Software Engineering Manager

RMS participated in a IRC chat with BerkeleyTIP 5/17/2009

can.axis — Mon, 18 May 2009 15:34:02 PDT

"The BerkeleyTIP group got Richard Stallman to stop by and chat on IRC in #berkeleyTIP on freenode today, May 17, 2009. They pushed him to get on Ekiga, but he doesn't have it setup yet. I thought this was kind of neat to have him get on IRC and chat on an open channel. The nickname for Richard is rmsgnu..."

Advertisement
Your ad here!

Import your mail and contacts from other accounts

The Gmail Team — Wed, 13 May 2009 15:42:31 PDT

Posted by Chad Parry, Gmail Engineer

Gmail users can be a passionate bunch. Many of us have, at one time or another, encouraged or cajoled friends and family to join us @gmail.com. But switching email accounts can be pretty painful. It's like getting out of a relationship. You have so much baggage — years of emails and contacts, memories of past Christmases and Valentine's Days — so the easier your new email account can make it, the better. My wife flirted with the idea for two years before she finally took the plunge with Gmail. The reason she finally made the switch might also convince your friends that it's a good time to adopt a shiny new Gmail address.

Gmail now migrates email and contacts from other email providers, including Yahoo!, Hotmail, AOL, and many more. It's much easier to make the transition now that you can bring along all your old email and contacts. You can even have your messages forwarded from your old account for 30 days, giving you time to take Gmail for a test drive while you make up your mind.

This new feature is available in all newly-created Gmail accounts, and it is slowly being rolled out to all existing accounts. It'll take longer than the few hours or days that most Gmail features take to get out to everyone. You'll know it's on for your account when you see the Accounts and Import tab (formerly just called Accounts) under Settings. Sorry, businesses and schools using Google Apps won't see these new migration options.

Everyone can still use POP3 mail fetching and upload your contacts in a CSV file, but this new way is much simpler for basic imports. And we like it when you can access and move your data the way you want — it's been easy to auto-forward all your Gmail messages to any other service, and now it's a little easier to go the other direction too.

Tasks, now in Calendar too

The Gmail Team — Wed, 13 May 2009 10:59:55 PDT

Posted by Garry Boyer, Software Engineer

Ever since we launched Google Calendar, people in our forum have been pretty vocal about a missing piece -- an integrated task list. "To-do would be tooo-rific," "I really, really, really need to use a to-do list," and my favorite: "I'll join your team to help you get it done!" The rumble turned into a roar a few months ago when we launched Tasks in Gmail Labs. Now we've integrated Tasks into Google Calendar as well.

To get started, open Calendar and click on the "Tasks" link on the left hand side. You'll see the familiar task list you're used to using in Gmail, with some Calendar-specific additions:

Tasks that have due dates will automatically appear on your calendar. To create a task with a due date in Calendar, click on an empty space in month view or the all-day section of week view, and be sure select the "Task" option.

To attach a due date to an existing task, click the right-arrow from within the task list, and then click on the calendar icon.
You can modify a task's due date by dragging it to a different date, just as you would with a regular calendar event.
To mark a task completed from within Calendar, just click on the task's checkbox. (Isn't that satisfying, overachievers?)
To keep track of due dates before they arrive, there's a nifty new "Sort by due date" feature available in the Actions menu at the bottom of your task list. While sorting by due date, you can reschedule a task by clicking on it in your list, then pressing control and the up or down arrow key.

While working to help bring this feature to you, I used it to keep track of my own tasks. Now I can finally check off the last one in that list: "write blog post." Phew.

My Google Profile

(author unknown) — Fri, 08 May 2009 14:41:26 PDT

Check out my new Google profile.

The 2008 Founders' Letter

A Googler — Thu, 07 May 2009 12:13:06 PDT

Posted by Sergey Brin, Co-founder & President, Technology

Every year our founders take turns writing a letter that is included in our annual report. We originally published the 2008 Founders' Letter on our Investor Relations site. Since today is the annual Stockholders' Meeting at our Mountain View headquarters, we wanted to make it more widely available. We welcome you to have a read, and you can also check out the webcast of the Stockholders' Meeting, beginning at 2 p.m. PT today. – Ed.

Introduction

Since 2004, when Google began to have annual reports, Larry and I have taken turns writing an annual letter. I never imagined I would be writing one in the midst of an economic crisis unlike any we have seen in decades. As I write this, search queries are reflecting economic hardship, the major market indexes are one half of what they were less than 18 months ago, and unemployment is at record levels.

Nonetheless, I am optimistic about the future, because I believe scarcity breeds clarity: it focuses minds, forcing people to think creatively and rise to the challenge. While much smaller in scale than today's global collapse, the dot-com bust of 2000-2002 pushed Google and others in the industry to take some tough decisions — and we all emerged stronger as a result.

This new crisis punctuates the end of our first decade as a company, a decade that has brought great change to Google, the web and the Internet as a whole. As I reflect on this short time period, our accomplishments and our shortcomings, I am very excited about what the next ten years may bring.

But let me start a little farther back — in 1990, the very first web page was created at http://info.cern.ch/. By late 1992, there were only 26 websites in the world so there was not much need for a search engine. When NCSA Mosaic (the first widely used web browser) came out in 1993, every new website that was created would get posted to its "What's New" page at a rate of about one a day: http://www.dejavu.org/prep_whatsnew.htm. Just five years later, in 1998, web pages numbered in the tens of millions, and search became crucial. At this point, Google was a small research project at Stanford; later that year it became a tiny startup. The search index sat on a small number of disk drives enclosed within Lego-like blocks. Perhaps a few thousand people, mostly academics, used the service.

Fast-forward to today, the changes in scale are striking. The web itself has grown by about a factor of 10,000, as has our search index. The number of people who use Google's services every day is now in the hundreds of millions. More importantly, billions of people now have access to the Internet via computers and mobile phones. Like many other web companies, the vast majority of our services are available worldwide and free to users because they are supported by ads. So a child in an Internet cafe in a developing nation can use the same online tools as the wealthiest person in the world. I am proud of the small role Google has played in the democratization of information, but there is much more left to do.

Search

Search remains at the very core of what we do at Google, just as it has been from our earliest days. As the scale has changed dramatically over the years, the presentation and quality of our search results have also undergone many changes since 1998. In the past year alone we have made 359 changes to our web search — nearly one per day. Some are not easy to spot, such as changes in ranking based on personalization (launched broadly in 2005) but they are important in getting the most relevant search results. Others are very easy to see and improve search efficiency in a very clear way, such as spelling correction, annotations, and suggestions.

While I am proud of what has been accomplished in search over the past decade, there are important areas in which I wish we had made more progress. Perfect search requires human-level artificial intelligence, which many of us believe is still quite distant. However, I think it will soon be possible to have a search engine that "understands" more of the queries and documents than we do today. Others claim to have accomplished this, and Google's systems have more smarts behind the curtains than may be apparent from the outside, but the field as a whole is still shy of where I would have expected it to be. Part of the reason is the dramatic growth of the web — for any particular query, it is likely there are many documents on the topic using the exact same vocabulary. And as the web grows, so does the breadth and depth of the curiosity of those searching. I expect our search engine to become much "smarter" in the coming decade.

So too will the interfaces by which users look for and receive information. While many things have changed, the basic structure of Google search results today is fairly similar to how it was ten years ago. This is partly because of the benefits of simplicity; in fact, the Google homepage has become increasingly simple over the years: http://blogoscoped.com/archive/2006-04-21-n63.html. But we are starting to see more significant changes in search interfaces. Today you can search from your cell phone by just speaking into it and Google Reader can suggest interesting blogs without any query at all. It is my expectation that in the next decade our searches and results will look very different than they do today.

One of the most striking changes that has happened in the past few years is that search results are no longer just web pages. They include images, videos, books, maps, and more. From the outset, we realized that to have comprehensive search we would have to venture beyond web pages. In 2001, we launched Google Image Search and via Google Groups we made available and searchable the most comprehensive archive of Usenet postings ever assembled (800 million messages dating back to 1981).

Just this past fall we expanded Image Search to include the LIFE Magazine photo archive. This is a collection of 10 million photos, more than 95 percent of which have never been seen before, and includes historical pictures such as the Skylab space station orbiting above Earth and Neil Armstrong landing on the moon. Integrating images into search remains a challenge, primarily because we are so reliant on the surrounding text to gauge a picture's relevance. In the future, using enhanced computer vision technology, we hope to be able to understand what's depicted in the image itself.

YouTube

Video is often thought of as an entertainment medium, but it is also a very important source of high-quality information. Some queries seem like natural choices to show video results, such as for sports and travel destinations. Yet videos are also great resources for topics such as computer hardware and software (I bought my last RAID based on a video review), scientific experiments, and education such as courses on quantum mechanics.

Google Video was first launched in 2005 as a search service for television content because TV close-captioning made search possible and user-generated video had yet to take off. But it subsequently evolved to a site where individuals and corporations alike could post their own videos. Today Google Video searches many different video hosting sites, the largest of which is YouTube, which we acquired in 2006.

Every minute, 15 hours worth of video are uploaded to YouTube — the equivalent of 86,000 new full length movies every week. YouTube channels now include world leaders (the President of the United States and prime ministers of Japan, the UK and Australia), royalty (the Queen of England and Queen Rania of Jordan), religious leaders (the Pope), and those seeking free expression (when Venezuelan broadcaster El Observador was shut down by the government, it started broadcasting on YouTube).

When it began, online video was associated with small fuzzy images. Today, many of our uploads are in HD quality (720 rows and greater) and can be streamed to computers, televisions, and mobile phones with increasing fidelity (thanks to improvements in video compression). In the future, vast libraries of movie-theater-quality video (4000+ columns) will be available instantly on any device.

Books

Books are one of the greatest sources of information in the world and from the earliest days of Google we hoped to eventually incorporate them into our search corpus. Within a couple of years, Larry was experimenting with digitizing books using a jury-rigged contraption in our office. By 2003, we launched Google Print, now called Google Book Search. Today, we are able to search the full text of almost 10 million books. Moreover, in October we reached a landmark agreement with a broad class of authors and publishers, including the Authors' Guild and the Association of American Publishers. If approved by the Court, this deal will make millions of in-copyright, out-of-print books available for U.S. readers to search, preview, and buy online — something that has been simply unavailable to date. Many of these books are difficult, if not impossible, to find because they are not sold through bookstores or held on most library shelves; yet they make up the vast majority of books in existence. The agreement also provides other important public benefits, including increased access to users with disabilities, the creation of a non-profit registry to help others license these books, the creation of a corpus to promote basic research, and free access to full texts at a kiosk in every public library in the United States.

Geo

While digitizing all the world's books is an ambitious project, digitizing the world is even more challenging. Beginning with our acquisition of Keyhole (the basis of Google Earth) in October 2004, it has been our goal to provide high-quality information for geographic needs. By offering both Google Earth and Google Maps, we aim to provide a comprehensive world model encompassing all geographic information including imagery, topography, road, buildings, and annotations. Today we stitch together images from satellites, airplanes, cars, and user uploads, as well as collect important data, such as roads, from numerous different sources including governments, companies, and directly from users. After the launch of Google Map Maker in Pakistan, users mapped 25,000 kilometers of uncharted road in just two months.

Ads

We always believed that we could have an advertising system that would add value not only to our bottom line but also to the quality of our search result pages. Rather than relying on distracting flashy ads, we developed relevant, clearly marked text-based ads above and to the right of our search results. After a number of early experiments, the first self-service system known as AdWords launched in 2000 starting with 350 advertisers. While these ads yielded small amounts of money compared to banner ads at the time, as the dot-com bubble burst, this system became our life preserver. As we syndicated it to EarthLink and then AOL, it became an important source of revenue for other companies as well.

Today, AdWords has grown beyond just being a feature of Google. It is a vast ecosystem that provides valuable traffic and leads to hundreds of thousands of businesses: indeed in many ways it has helped democratize access to advertising, by creating an open marketplace where small business and start-ups can compete with well-established, well-funded companies. AdWords is also an important source of revenue for websites that create the content that we all search. Last year, AdSense (our publisher-facing program) generated more than $5 billion dollars of revenue for our many publishing partners.

Also in the last year we ventured further into other advertising formats with the acquisition of DoubleClick. This may seem at odds with the value we place on relevant text-based ads. However, we have found that richer ad formats have their place such as video ads within YouTube and dynamic ads on game websites. In fact, we also now serve video ads on television with our AdSense for TV product. Our goal is to match advertisers and publishers using the formats and mediums most appropriate to their goals and audience.

Despite the progress in our advertising systems and the growth of our base of advertisers, I believe there are significant improvements still to be made. While our ad system has powerful features, it is also complex, and can confuse many small and local advertisers whose products and services could be very useful to our users. Furthermore, the presentation formats of our advertisements are not the optimal way to peruse through large numbers of products. In the next decade, I hope we can more effectively incorporate commercial offerings from the tens of millions of businesses worldwide and present them to consumers when and where they are most useful.

Apps

Within a couple of years of our founding, a number of colleagues and I were starting to hit the limitations of our traditional email clients. Our mailboxes were too big for them to handle speedily and reliably. It was challenging or impossible to have email available and synchronized when switching between different computers and platforms. Furthermore, email access required VPN (virtual private networks) so everyone was always VPN'ing, thereby creating extra security risks. Searching mail was slow, awkward, and cumbersome.

By the end of 2001 we had a prototype of Gmail that was used internally. Like several existing services at the time, it was web-based. But unlike those services it was designed for power users with high volumes of email. While our initial focus was on internal usage, it soon became clear we had something of value for the whole world. When Gmail was launched externally, in 2004, other top webmail sites offered 2MB and 4MB mailboxes, less than the size of a single attachment I might find in a message today. Gmail offered 1 Gigabyte at launch, included full-text search, and a host of other features not previously found in webmail. Since then Gmail has continued to push the envelope of email systems, including functionality such as instant messaging, video-conferencing, and offline access (launched in Gmail Labs this past January). Today some Googlers have more than 25 gigabytes of email going back nearly 10 years that they can search through in seconds. By the time you read this, you should be able to receive emails written in French and read them in English.

The benefits of web-based services, also known as cloud computing, are clear. There is no installation. All data is stored safely in a data center (no worries if your hard drive crashes). It can be accessed anytime, anywhere there is a working web browser and Internet connection (and sometimes even if there is not one — see below).

Perhaps even more importantly, new forms of communication and collaboration become possible. I am writing this letter using Google Docs. There are several other people helping me edit it simultaneously. Moments ago I stepped away and worked on it on a laptop. Without having to hit save or manage any synchronization all the changes appeared in seconds on the desktop that I am back to using now. In fact, today I have worked on this document using three different operating systems and two different web browsers, all without any special software or complex logistics.

In addition to Gmail and Google Docs, the Google Apps suite of products now includes Spreadsheets, Calendar, Sites, and more. It is also now available to companies, universities, and other organizations. In fact, more than 1 million organizations use Google Apps today, including Genentech, the Washington D.C. city government, the University of Arizona, and Gothenburg University in Sweden.

Because tens of millions of consumers already use our products, it is easy for organizations — from businesses to non-profits — to adopt them. Very little training is required and the passionate Google users already in these organizations are usually excited to help those who need a hand. In many ways, Google Apps are even more powerful in a business or group than they are for individuals because Apps can change the way businesses operate and the speed at which they move. For example, with Google Apps Web Forms we innovated by addressing the key problem of distributed data collection, making it incredibly simple to collect survey data from within the enterprise — a critical feature for collecting internal feedback we use extensively when "dogfooding" all of our products.

There are a number of things we could improve about these web services. For example, since they have arisen from different groups and acquisitions, there is less uniformity across them than there should be. For example, they can have different sharing models and chat capabilities. We are working to shift all of our applications to a common infrastructure. I believe we will achieve this soon, creating greater uniformity and capability across all of them.

Chrome

We have found the web-based service model to have significant advantages. But it also comes with its own set of challenges, primarily related to web browsers, which can be slow, unreliable, and unable to function offline. Rather than accept these shortcomings, we have sought to remedy them in a number of ways. We have contributed code and generated revenue for several existing web browsers like Mozilla Firefox, enabling them to invest more in their software. We have also developed extensions such as Google Gears, which allows a browser to function offline.

In the past couple of years, however, we decided that we wanted to make some substantial architectural changes to how web browsers work. For example, we felt that different tabs should be segregated into separate sandboxes so that one poorly functioning website does not take down the whole browser. We also felt that for us to continue to build great web services we needed much faster Javascript performance than current browsers offered.

To address these issues we have created a new browser, called Google Chrome. It has a multiprocess model and a very fast JavaScript engine we call V8. There are many other notable features, so I invite you to try it out for yourself. Chrome is not yet available on Mac and Linux so many of us, myself included, are not able to use it on a regular basis. If all goes well, this should be addressed later this year. Of course, this is just the start, and Chrome will continue to evolve. Furthermore, other web browsers have been spurred on by Chrome in areas such as JavaScript performance, making everyone better off.

Android

We first created mobile search for Google back in 2000 and then we started to create progressively more tailored and complex mobile offerings. Today, the phone I carry in my pocket is more powerful than the desktop computer I used in 1998. It is possible that this year, more Internet-capable smartphones will ship than desktop PCs. In fact, your most "personal" computer, the one that you carry with you in your pocket, is the smartphone. Today, almost a third of all Google searches in Japan are coming from mobile devices — a leading indicator of where the rest of the world will soon be.

However, mobile software development has been challenging. There are different mobile platforms, customized differently to each device and carrier combination. Furthermore, deploying mobile applications can require separate business arrangements with individual carriers and manufacturers. While the rise of app stores from Apple, Nokia, RIM, Microsoft, and others as well as the adoption of HTML 5 on mobile platforms have helped, it is still very difficult to provide a service to the largest group of network-connected people in the world.

We acquired the startup Android in 2005 and set about the ambitious goal of creating a new mobile operating system that would allow open interoperation across carriers and manufacturers. Last year, after a lot of hard work, we released Android to the world. As it is open source, anyone is free to use it and modify it. We look forward to seeing how this open platform will spur greater innovation. Furthermore, Android allows for easy creation of applications which can be deployed on any Android device. To date, more than 1000 apps have been uploaded to the Android Market including Shop Savvy (which reads bar codes and then compares prices), our own Latitude, and Guitar Hero World Tour.

AI

The past decade has seen tremendous changes in computing power amplified by the continued growth of Google's data centers. It has enabled the growth and processing of increasingly large data sets such as the web, the world's books, and video. This in turn has allowed problems once considered to be in the fantasy realm of artificial intelligence to come closer to reality.

Google Translate supports automatic machine translation between 1640 language pairs. This is made possible by large computer clusters and vast repositories of monolingual and multilingual texts: http://www.google.com/intl/en/help/faq_translation.html. This technology also allows us to support translated search where the query gets translated to another language and the results get translated back.

While the earliest Google Voice Search ran as a crude demo in 2001, today our own speech recognition technology powers GOOG411, the voice search feature of the Google Mobile App, and Google Voice. It, too, takes advantage of large training sets and significant computing capability. Last year, PicasaWeb, our photo hosting site, released face recognition, bringing a technology that is on the cutting edge of computer science to a consumer web service.

Just a few months ago we released Google Flu Trends, a service that uses our logs data (without revealing personally identifiable information) to predict flu incidence weeks ahead of estimates by the Centers for Disease Control (CDC). It is amazing how an existing data set typically used for improving search quality can be brought to bear on a seemingly unrelated issue and can help to save lives. I believe this sort of approach can do even more — going beyond monitoring to inferring potential causes and cures of disease. This is just one example of how large data sets such as search logs coupled with powerful data mining can improve the world while safe guarding privacy.

Conclusion

Given the tremendous pace of technology, it is impossible to predict far into the future. However, I think the past decade tells us some things to expect in the next. Computers will be 100 times faster still and storage will be 100 times cheaper. Many of the problems that we call artificial intelligence today will become accepted as standard computational capabilities, including image processing, speech recognition, and natural language processing. New and amazing computational capabilities will be born that we cannot even imagine today.

While about half the people in the world are online today via computers and mobile phones, the Internet will reach billions more in the coming decade. I expect that by using simple yet powerful models of computing such as web services, everyone will be more productive. These tools enable individuals, small groups, and small businesses to accomplish tasks that only large corporations could achieve before, whether it is making and releasing a movie, marketing a product, or reporting on a war.

When I was a child, researching anything involved a long trip to the local library and good deal of luck that one of the books there would be about the subject of interest. I could not have imagined that today anyone would be able to research any topic in seconds. The dark clouds currently looming over the world economy are a hardship for us all, but by the time today's children grow up, this recession will be a footnote in history. Yet the technologies that we create between now and then will define their way of life.

Q&A: Windows 7 File Extension Hiding

(author unknown) — Fri, 29 May 2009 02:01:20 PDT

We got plenty of good comments on the previous blog post about Windows 7, including feedback from people who are actually working in the Explorer development team at Microsoft.

Many of the comments included questions on the topic, so here's a Q&A:

Q: What is this all about?
A: It's about Windows, by default, hiding file extensions such as .EXE. Virus writers exploit this by creating malicious files with double-extensions (PICTURE.JPG.EXE). Such a file would typically also use a misleading icon.

Q: How long has Windows Explorer been hiding file extensions "For known file types"?
A: Since Windows NT.

Q: Why do they do it?
A: We don't know.

Q: Is this a real risk? If user already has such a file on his hard drive, it's too late, right?
A: Not really. The file could have come from the Internet, from a file share or a removable drive and the user hasn't necessarily executed it yet.

Q: But if the file came from the Internet, Explorer will warn you that it came from an "Untrusted Zone"!
A: Only if you use Internet Explorer to browse the web and Outlook to download your e-mail attachments. There are plenty of other ways to download files from the net: 3rd party web and e-mail clients, BitTorrent and other P2P clients, chat programs etc. Also, you can't rely on such warning dialogs if the file is on a network share or an a USB drive.

Q: There is no problem. Even in your own screenshot the file is labeled by Explorer as "Application"! Thus, nobody would click on it. Even though the file is called something.txt. And it has the icon of a text file.
A: Right…

Q: Do real worms really use such filenames?
A: Oh yes. They typically spread by copying themselves with tempting filenames to random folders on removable drives or network shares, with filenames along these lines:

    E:\PRESENTATION.PPT.exe
    E:\DOCUMENT.DOC.exe
    E:\PORNVIDEO.AVI.exe
    Etc.

Many would click on these, especially if the icon of the file looks like a document icon — and when Windows hides the ".exe" part of the name.

Q: So, the solution is turn off "Hide extensions for known file types" in Explorer settings?
A: Yeah.

Q: Will that make all file extensions visible?
A: Well, no. There are executable extensions that will STILL be hidden even if you turn the option off.

Q: What?
A: For example PIF. This file type was meant to be a shortcut to old MS-DOS programs. Problem is, you can rename any modern Windows Executable to .PIF and it will happily run when double-clicked.

For example, the Scamo worm uses exactly this flaw, dropping files such as these:

    HARRY POTTER 1-6 BOOK.TXT.pif
    ANTHRAX.DOC.pif
    RINGTONES.MP3.pif
    BRITNEY SPEARS FULL ALBUM.MP3.pif
    EMINEM BLOWJOB.JPG.pif
    VISTA REVIEW.DOC.pif
    OSAMA BIN LADEN.MPG.pif
    NOSTRADAMUS.DOC.pif

Q: How do you I make PIF files visible then?
A: Via a registry key called "NeverShowExt". We'd link you to an article in the Microsoft Knowledgebase… except we couldn't find any. But here's a Web page on the topic, from GeoCities, made by some hobbyist a couple of years ago. Maybe it's the best source of information on the topic.

Q: Do you still expect Microsoft to change the behavior of Explorer in Windows 7?
A: No, not really.

Bottom line: We still fail to see why Windows insists on hiding the last extension in the filename. It's just misleading.

On 07/05/09 At 02:25 PM

Andreas Nilsson: Thunderbird visual refresh on Linux

(author unknown) — Thu, 07 May 2009 04:42:29 PDT

Been working on the appearance of Thunderbird for the last two months now and as things are starting to land in the Nightly builds, things are indeed starting to look quite nice. As always, Lapo have been of great help in the icon department.

I’ve always enjoyed Thunderbird and it’s predecessors that have been following me since I started out with web stuff when I was around 14 years old. Therefore, working on this would really scratch my own itch as I felt it always looked out of place on my Linux desktop and allow me to give back to the e-mail client that served me with so many messages over the years (and pay the rent, yay!).

Anyway, here are some shots:

Main window:

Compose:

Address book:

As you might note, the icons in the main toolbar pretty much look the same, this is mainly because they are going away as soon as the great work that’s been going on with the new toolbar layout lands.

As we’ve used GTK+ stock items wherever we can, your folders in the sidebar will of course look native. Comparison between regular GNOME, Fedora, openSUSE and Ubuntu:

Please check out a Nightly build and report any issues.

Windows 7 RC1: 10 Things You Need to Know [Windows 7 RC1]

matt buchanan — Wed, 06 May 2009 12:00:00 PDT

Windows 7's about ready to come out of the oven, and now everybody can shove their hands in the warm OS pie. And really, you should. Here's everything you need to know to dive in.

1. Where Do I Get It?
Right here! If you're at work, don't worry, you have until July to download it. From there, you'll need to burn the disc image to a DVD or copy it to a flash drive. From there, you can follow our guide to installing Windows 7 pain-free (or Lifehacker's, though I hear they smell like nerd feet). There's a guide for doing it on a Mac too.

2. Will It Run on My Computer?
Probably. It's run fantastically on netbooks for us, if that tells you anything. But here are the hard minimum specs:

• 1 GHz processor (32- or 64-bit)
• 1 GB of RAM (32-bit); 2 GB of RAM (64-bit)
• 16 GB of available disk space (32-bit); 20 GB of available disk space (64-bit)
• DirectX 9 graphics device with WDDM 1.0 or higher driver

3. Wait, Can I Upgrade My Current Windows Install?
If you're running Windows Vista, you sure can—it's designed to be easy to go from Vista to Windows 7, actually. It's a little more complicated with other types of Windows. You can upgrade your Windows 7 Beta install if you've got one, but it's not recommended, and takes a bit of skunkwork. You're out of luck with XP and any other older version of Windows, which is how it's gonna be with the retail version of Windows 7 too—though Microsoft has some tools to make it less painful, or you could take the long way around, just to say you did it.

4. Is It Safe?
It's very safe. Unlike Google, Microsoft seems to be using product cycle terms in their traditional sense, so the designation "release candidate" means it's a version that's got the potential to go final—as long as nothing majorly FUBAR is discovered—with just a few little bugs left for squishing. Besides, the Windows 7 Beta was pretty damn solid to begin with. And if you follow one of our guides to dual-booting it, then you've really got nothing to worry about.

All of your hardware should work just fine, especially if it worked alright on Vista, since we're talking mostly the same OS guts here, and Microsoft bent over backward to make stuff backward compatible with Vista. It's possible you'll need to grab drivers for your hardware or gadget straight from the manufacturer—or in the case of graphics cards from Nvidia or ATI, you'll want to for the best possible performance—but you should be able to just plug and play.

Still, back your stuff up! That's just common sense.

5. How Long Can I Keep It?
Depends on what you mean by that! It goes completely poof on June 1, 2010. But on March 1, it becomes basically unusable—it starts automatically shutting down every two hours like a dbag.

6. How Is RC1 Better Than the Beta?
Lots of stuff, actually. Just for starters, Aero Peek is better, and works with Alt+Tab now when you're flipping through programs. Windows Key shortcuts are more logical, so pressing Windows Key + [number key] switches between apps pinned to the taskbar, rather than just launching 'em. And things just feel smoother—more fade transition effects sprinkled throughout, for instance, and there seems to be a bit more snap to everything, like a carrot. If you like carrots.

7. What's This I Hear About XP Mode?It's true, Windows 7's secret new feature is XP Mode. It's a virtual Windows XP machine—complete with a fully licensed copy of Windows XP SP 3 installed on the virtual machine—that you can download which runs seamlessly in Windows 7, so you can do crazy things like run IE6 side-by-side with IE8. It's meant for businesses who need compatibility for mission critical XP-only apps.

Really, don't get too hung up on it—it's only for the Enterprise, Professional and Ultimate versions of Windows 7, not the Home Premium version you'll probably be running one day. (The release candidate is Ultimate, so you can toy around with it after downloading it here.) You also need a processor with either Intel Virtualization Technology or AMD-V and 2GB of RAM. And you can't really do anything intense like gaming inside of it. Oh, and fair warning, it's also probably one of the release candidate's glitchiest features. Image via Wikipedia.

8. Holy Crap, Microsoft Is Tripping on Acid!Yes.

9. What's Still Glitchy?
Uh, the aforementioned Windows XP Mode, for one. Some of our Steam games are still acting a little bit weird, notably with audio. Coming out of sleep can be wonky for OpenGL with UAC turned on. Occasional taskbar weirdness if you play around with the positioning. But all in all, fairly minor stuff, so far.

10. Why Should I Go Through All This Trouble?
Simply put, Windows 7 has been awesome. Whatever bad things you felt toward Vista—hate, fear, rage, apathy, bi-curiosity—Windows 7 probably solves your issue. The UI's evolved more than it has in years, you don't need to download a bunch of stupid codecs, it makes plugging in gadgets kind of fun, it's more secure and generally, life's just a lot better for anyone on a PC. While Microsoft says a pre-release shouldn't be your main OS, we're pretty sure it will be, almost instantly.

Flashing Your BIOS From The Linux Desktop

(author unknown) — Mon, 04 May 2009 08:06:21 PDT

Linux hardware support has improved a great deal over the past few years, but there are still a few troubled spots. With computer motherboards, for instance, the core functionality is generally there and most consumer motherboards will "just work" with the latest desktop Linux distributions out there. Where users though can run into problems are with the ancillary features. Motherboard manufacturers usually bundle proprietary software with their products that allow monitoring of hardware sensors, flashing of the motherboard BIOS, and overclocking all from within the Windows operating system. With the exception of LM_Sensors providing some sensors support, this is a grey area for Linux. Fortunately, however, the folks working on the CoreBoot project have developed a program that will near universally allow you to flash your motherboard's BIOS from within the Linux desktop.

New in Labs: Google Search right in Gmail

The Gmail Team — Thu, 30 Apr 2009 17:01:27 PDT

Posted by Adam de Boor, Software Engineer

I used to have a problem. People would ask me questions, over chat or email, and I'd have to leave Gmail to search Google for an answer. Then I'd have to select the answer, copy it, go back to Gmail and paste the answer into the chat window or my reply. Sometimes I'd get distracted and forget to go back to Gmail, and I'd have to go through it all again when I remembered what I'd been doing.

With the new Google Search experiment in Gmail Labs, my problem is solved. When you turn this feature on from the Labs tab under Settings, you'll see a new search box on the left side of your inbox, like this:

Type your search in, and a window (like a chat window, but a bit bigger) appears at the bottom of your screen with the first few search results.

You can click on a search result and it'll open up in another window (or another tab) so you can make sure it's what you're looking for. Once you're sure it's a result you need, moving your mouse over the result back in Gmail reveals a pull-down menu that lets you do stuff with the search result.

What's in the menu depends on what you're doing in Gmail:

If you're reading a message, you can start a reply to the message with the search result as the first thing in your reply.
If you're writing a message, you can paste the result, or just the URL into your message.
If you're chatting with someone, you can send the result via chat.
You can also always compose a new message to send the search result.

If you have keyboard shortcuts turned on, typing g and then / will take you to the search box when you're not composing, and Ctrl + g will do it when you're composing (that's ⌘ + g for Mac users).

Like all things in Gmail Labs, we're going to be tinkering with it, so let us know what you think.

Oh, and one other thing: with all the stuff we've been adding to Gmail Labs lately, the left side of your account might be getting crowded. A lot of the people who've been playing with this new feature have found it useful to turn on "Navbar drag and drop" in Labs so they can move the web search box up to the top where it's easy to get to.