Watch this battle unfold. The virtualization wars are just getting started.

On one side we have Microsoft, which announced changes in its licensing structures this week. The change reflects an understanding that the customer wants full access to its virtualization platform and not be charged a tax for that right to access it on a PC, no matter if it is at work or in their home.

And in true fashion, Microsoft is on the attack, Citrix at its side, in a full on fight with VMware for the virtualization market.

Sponsor

On the VMware side, we see a company ready to move into Microsoft's customer base by offering more than virtualization as witnessed with its recent acquisition of Zimbra. VMWare is gearing up to tap into the Microsoft Exchange market by combining its virtualization technology with the Zimbra email platform.

Historically, Microsoft has charged for separate licenses to access Windows operating systems in a virtual desktop infrastructure (VDI) environment. Until now, there would be separate licensing fees for people to access their virtual desktops from secondary devices like home personal computers.

The licensing issue in all of this gets complicated pretty fast. According to Simon Bramfitt:

VMWare, in smart retort, praises Microsoft for the move and bowing to "intense customer pressure."

Raj Mallempati, director, product marketing, calls it an opening for VMWare View. You know it's competitive when you see this kind of rhetoric:

By loosening up the restrictive desktop virtualization license policy (VECD), Microsoft has finally bowed to intensive customer pressure. This validates the acceleration in demand in the desktop virtualization industry that VMware helped start and continues to lead. Microsoft's move here is extremely positive for the industry.

But what is Citrix part in all of this?

At the beginning of the year, VMWare offered the opportunity to exchange Citrix XenApp licenses for VMWare View. In response, Microsoft and Citrix announced a partnership this week aimed right at VMWare with some pretty attractive licensing deals.

The promotion intends to undercut VMWare by reaching into its customer base with offers to trade in as many as 500 licenses in exchange for a Microsoft integration offered with Citrix.

To kick it off, the two companies plan a 100-city tour.

But what this really represents is Microsoft providing some flexibility in its virtualization licensing agreements. That move alone will help open up the market.

And VMWare? The company has 80 percent of the virtualization market. Any move on its customer base should be expected. VMware's vision for Zimbra is another matter. That's a battle it is taking right back to Microsoft - square on its home turf.

Continue reading Palm: this is your survival guide

Palm: this is your survival guide originally appeared on Engadget on Fri, 19 Mar 2010 17:04:00 EST. Please see our terms for use of feeds.

Engadget's Joshua Topolsky pens a lengthy article on what has gone so terribly wrong at Palm over the last year. His solutions aren't perfect, but it's worth reading. —Ed.

Oh Palm. Just a little over a year ago your future seemed so bright, so renewed. You walked away from CES 2009 reborn, held aloft by a completely innovative new mobile operating system, a striking piece of hardware, and a feeling amongst the press and investors that you were back in the game and playing to win. Now, less than a year and a half later, you've nearly returned to the dark and desperate place you'd found yourself in at the end of 2008; a rapidly declining mindshare, the bottom falling out of your stock, and bad dips in phone sales.

Continue reading at Engadget >

Join the conversation about this story »

(Version Française ici).

About five years ago, I wrote a detailed report on how one could have the choice between GNU / Linux and other operating systems in Argentina. that was most surprising for French people, that have always had the greatest difficulties in getting such a choice, despite the remarkable efforts made by the Working Group Detaxe and Racketiciels. It was even possible at that time in Argentina to compare on the website of major retail chains (Fravega, Garbarino, the equivalent of Darty or Boulanger in France) the price for the same machine with another operating system or with a Debian-based, customised Argentinian GNU / Linux, developed by an SME named Pixart (not to be confused with the studio Pixar!).

But starting from 2 years ago, I have seen that it has become impossible to find any longer a single machine with GNU / Linux in retail: worse, we saw some very dubious agreements negotiated under the high patronage of the founder of the multinational software company that monopolises the operating systems market.

One may well ask why: this is not without reminding us of the situation here in France, where after SFR placed on the market more thatn 250000 Netbooks all equipped with GNU / Linux about two years ago, we can not find now a single netbook without Windows (yes, I write the name in full letters now, because I am particularly upset: I wanted to buy one for personal use this Christmas, but despite my efforts, I have not found a single model with a GNU / Linux preinstalled in France).

The few remaining fans of software monopolies like to say that this sudden vanishement proves that the other operating system is superior to GNU / Linux.

Well, I happen to have in my hands right now a copy of the appeal filed against Microsoft by the little Argentine SMEs Pixart, and it is very helpful in understanding what really happened there ... and very likely what is happening here too.

Microsoft does not usually sit back when it loses market share, and I already noticed back then that Redmond had put in place a strategy to counter the spread of GNU / Linux in emerging markets. In Argentina, already in 2005 they had managed to convince the government to spend taxpayer money on an operation codenamed 'Mi PC', which through a microcredit whose interests were paid by the state, encouraged the public to buy machines that are sold with Windows SE (Starter Edition, they say), better known today as Windows FTP (For The Poor). This edition sports ludicrous limitations like the following: only recognises 256 Mb of RAM (with XP, It's a little short), 80 GB hard disk (ditto), screen resolution was limited to 800x600, no local network, and you cannot open windows for more than 3 applications at once (oh well, if there is something that poor people have in abundance is time, therefore they will only run 3 tasks in parallel, and no more).

This version was sold cheaper than the standard Windows editions , with the aim to compete with GNU / Linux machines, but at that time this move made me laugh quite a bit because the early machines with Windows FTP still costed at least 500 pesos more than the equivalent GNU / Linux systems, which had no such ridiculous limitations: one really had to be poor in spirit to purchase them!

What I did not know in 2006 is that the Windows For The Poor was just a first step in the strategy: The second step was to artificially lower the final price of computers running Windows, and financially strangling Pixart, which could not charge anymore its service for pre-installation of custom GNU / Linux on machines manufactured in Argentina.

In reading the appeal filed by Pixart, we learn that Microsoft would have started in 2008 to give back large amounts of money to the whole distribution chain to convince them to buy exclusively Windows, and these sums have been disguised in various forms.

For example, I heard that Microsoft would have payed hundreds of thousands of dollars a year to some distributors, officially for the Microsoft logo to appear on the leaflet advertising the chain. Well, this kind of operation is called 'rear margin' here, and generally corresponds to an abuse of dominant position from retailers who charge abusive fees to small suppliers for purported advertising campaigns that hide forced rebates. But in our case, I have a hard time thinking that a small retail chain in Latin America has a dominant position when facing a multinational that generates profits of billions of dollars a year.

But why, you will say , is Microsoft complicatin its life like this? Was'nt it easier to simply lower the cost of licensing Windows to, say, $ 5, rather than continue to charge $ 100 initially, to repay $ 95 to distributors right after?

Well, no! Because, if we lower the cost of the officially licensed Windows FTP to $ 5, then it must be sold $ 5 everywhere, and we can no longer pretend to charge $ 200 to large customers (such as ministries in Argentina) for the full version .

It is much more interesting to pretend that the cost is 50 or 100 dollars, and find a way to give back 45 or 95 dollars under the table: on one side the illusion is maintained that the price is high and constant, on the other, one can happily strangle competition, by lowering prices only on the competitive segment (the rebate is conditioned, of course, to stopping any sale of the rival product).

This wonderful monopolistic invention has one flaw, though: it brutally violates the rules of competition, which are codified, for better or worse, in almost all countries, including Argentina. To function properly, it must be carried out in the greatest secrecy, and stay safe from prying eyes.

But it may well be that this discretion is not going to las much longer: using the laws on competition in Argentina, Pixart filed appeal, describing what it thinks is the strategy followed by Microsoft, and asking the judge to compel Microsoft, and distributors to provide all evidence of purchases, grants, rebates, in short, an account of all financial transaction, even by means of intermediaries, between Microsoft and distributors.

Pixart also suggests that the judge checks whether Microsoft properly pays tariffs for imports of these licenses: it is well known that Microsoft

As a full time systems administrator, I can tell you without equivocation that IT is hard. There are lots of little problems that occur. Operating systems are fragile. Automation is great, but requires constant vigilance. So I approach things like the ClearBOX with much skepticism. An all-in-one IT solution sounds too good to be true, and it very likely is. I’m sure it offers some great features, and in the right environment it can be a good purchase. But there is no holy grail to unified IT services, because every environment is different, and the only constant is change.

The hardware specs on the ClearBOX look adequate enough for most small businesses with simple IT needs:

• System Restore (In Development)
• Bypass 2 LED Indicator
• Bypass 1 LED Indicator
• G2 Bypass Segment 1 with 2 1Gb Ethernet Ports
• G2 Bypass Segment 2 with 2 1Gb Ethernet Ports
• 2 1Gb Ethernet Ports
• Dual USB 2.0 Ports
• RJ45 System Console connector
• Hard Drive Active LED
• Power LED
• Reset Button
• 128×32 Graphic LCD Module
• 4 button LCD Module Control
• 200W Full-range ATX
• On/Off Switch
• Intelligent Cooling System
• VGA Port – Intel 82G41 Chipset
• One PCI-E x8 Expansion Slot Rear

The ClearBOX comes with ClearOS, “a powerful network and server gateway designed for small organizations and distributed environments.” It’s open source, so I’m guessing it’s a Linux distribution of some sort, but it’s not clear to me whether they’ve rolled their own distro from the ground up, or if they’re springboarding off an existing distribution.

The ClearBOX and ClearOS look like a neat offering, but I’ve seen way too many of these all-in-one “IT in a box” systems come and go through the years to have any expectations that this one will last.

The first car equipped with Google’s Android mobile operating system will hit the streets this April 23. It’s called the Roewe 350, and it will launch at the Beijing Auto Show.

Roewe vehicles are luxury cars made by Chinese car company SAIC (Shanghai Automotive Industry Corporation) using technology purchased from British company MG Rover, which has been owned by both BMW and Ford in the past.

The 2.1 version of Google Android — the same that Google used in the Nexus One and Motorola Droid — is installed on the vehicle’s GPS computer. You can use the computer for directions and traffic reports just as you can with many other GPS devices. But it’s not all vanilla; you can also surf the web and engage in some form of Internet chatting. There’s no telling yet which chat service you’ll be using, but hopefully you won’t be doing it while you’re driving!

We haven’t heard whether or not you’ll be able to install apps from the Android Market yet. We also don’t know how the device connects to the Internet. The car will cost between 70,000 and 130,000 yuan, or about $10,250 – $19,000.

[via The Next Web]
[img credit: autohome.com.cn]

Tags: android, android 2.1, car, Google Android, gps, roewe 350

read more

Google’s obsession with speed is well-documented. One of the primary design principles behind its search engine is to return results as fast as possible and strip away anything extra. But its need for speed goes well beyond search. All of Google’s apps are optimized for speed (well, except Gmail lately, but they promise to fix that). The Chrome browser is extremely fast, and the upcoming Chrome OS is also expected to make Web browsing and other computing tasks zippier.

It almost doesn’t matter if Google’s Chrome browser and OS gain significant market share or not, as long as they push other browsers and operating systems to keep up in the speed race. Google’s need for speed boils down to one very simple thing: money. It realized long ago that every millisecond improvement in pageload times on its search engine resulted in more searches, and thus more search ads served and clicked on. The opposite is also true. Google once did a study showing that delays of 100 to 400 millisecond in showing search results translated into up to 0.6 percent searches. Multiply that across the billions of searches done on Google and it starts to add up to real money, perhaps tens of millions of dollars per quarter.

Google can keep trying to make search faster because that is under its control. But what about the rest of the Web? The faster pages load, the more Web pages people will visit overall (this is why broadband adoption is the single biggest driver of Internet traffic and e-commerce). And it stands to reason that the more Web pages you visit, the more searches you will perform in any given day. Because searches are driven by the other things you do on the Web. You go look for information, surf around, and then go back to search when you want to find something new (at least Google hopes you do). By helping to speed up the Web, Google can speed up that information loop so that instead of waiting for Web pages to load you can get what you need and start another search instead.

No wonder Google tries to do everything it can to make the Web faster. For instance, it is supporting emerging standards such as HTML5 and SPDY, and sharing its best practices and speed-monitoring tools with developers. It is also baking the PuSH protocol into Google Reader and other apps. In doing so, Google is helping to deliver news feeds faster (PuSH, aka Pubsubhubbub, was created by two Google engineers, of course, and released as an open-source project). The list goes on and on.

It is all about trying to get people to achieve a “flow state” where they are just clicking from one link to the next and it all happens instantaneously. In order for humans not to notice electronic delays, new information needs to appear in a matter of milliseconds. Get the whole Web humming like that and we may never leave our monitors.

Photo credit: Flickr/ Ana Patricia Almelda

Palm shares plunged in late trading Thursday after the company posted yet another dismal quarter and warned that revenue for the current one will fall far short of Wall Street expectations. The company will have to take substantial charges to help its carrier partners eat through excess inventory, and whatever luster once existed for its flagship Pre is long gone. The question now is, who’s going to pick up Palm?

Palm’s last-ditch gamble on webOS has been a disaster. The operating system — which debuted last summer on the Pre — has received solid reviews, but an utter lack of effective marketing from Sprint — and more recently, Verizon Wireless — shackled handset sales. And an upcoming partnership with AT&T — which looked to be Palm’s last chance at redemption — is reportedly fizzling already after the carrier delayed the launch of webOS handsets, slashed its order and cut its marketing budget.

So what are Palm’s options? CEO Jon Rubinstein is projecting a “stay the course” attitude, saying better training of Verizon Wireless sales staffers will begin to pay off — a questionable theory given the flat-line demand for the Pre Plus and Pixi Plus so far. Producing a tablet would be an interesting strategy, as James over at jkOnTheRun suggested yesterday. But the market for tablets is still very uncertain, and there’s little reason to believe Palm can move a different kind of hardware when it can’t sell phones. So a suitor will likely sweep in and pick up Palm, snatching up webOS — the company’s most valuable asset — and a sizable patent portfolio. Here’s a quick rundown of the most likely (or most highly speculated) candidates for acquiring Palm — including their odds of doing so:

• Google : The most intriguing play on the board, Google might be compelled by Palm’s patent portfolio, as Gizmodo noted yesterday. What’s more, Google and Palm both operate Linux-based mobile operating systems, which would make it easy for Google to cherry-pick the best features from webOS and add them to Android. Google could easily afford Palm, and as a bonus would keep it from falling into the hands of a competitor. Odds: 7-1
• Dell : The Texas computer vendor joined the smartphone space a few months ago, launching handsets in Brazil and China, and will soon launch an Android-based device through AT&T. But its late entry means Dell will have a hard time differentiating its hardware, and coming to market with its own mobile operating system, app store and developer community could be a great way to stand out from the crowd. Odds: 7-1
• Hewlett-Packard: HP’s tiny smartphone business is dissolving in the superphone era. Picking up what amounts to a turnkey mobile OS would be a huge — if costly — move to attract attention and breathe life into its mobile business. Odds: 11-1.
• Nokia : Nokia has long been mentioned as a potential buyer for Palm, but successfully marrying the two has become an increasingly difficult proposition. Nokia already claims the world’s most popular smartphone OS in Symbian, and its Maemo — um, sorry, I mean MeeGo – operating system appears to be its long-term strategy. What’s more, Ovi has gained impressive traction in recent months. Adding another platform to the mix would only serve to distract Nokia just as it finally appears to be regaining its focus. Odds: 25-1
• Motorola : Another hardware maker that might be compelled by the idea of owning its own OS, Motorola’s $8 billion in cash ensures plenty of capital to pocket Palm. Yet despite what Om suggested earlier this year, taking on a mobile operating system would likely be more than Motorola could handle, given its difficulty in regaining its once-dominant market share in smartphones. Marriages of two weak players from different spaces rarely end up happy. Odds: 30-1
• Microsoft : Palm and Microsoft seemed like a great fit just a few months ago. But that was before the gang from Redmond went public with its plans to scrap Windows Mobile in favor of Windows Phone, an impressive, consumer-targeted platform set to debut late this year. Windows Phone may fail gloriously, but there’s no reason to bring another OS into the fold — and webOS is largely considered to be Palm’s most valuable asset. Odds: 35-1
• Cisco : An acquisition of Palm would enable Cisco to immediately expand beyond infrastructure into the mobile consumer market. Such a move wouldn’t exactly be unprecedented for Cisco, which last year bought the maker of Flip Video camcorders for $590 million, but maintaining a mobile operating system is a far more sophisticated endeavor than simply churning out camcorders. Odds: 40-1.

This is only a partial list, of course, and new potential suitors are sure to emerge as Palm begins to circle the drain. The clock is ticking, and there’s almost no hope Palm can reverse course at this point. So someone in the mobile space might be able to do very well by picking up a dying company at a cut-rate price.

Related content from GigOM Pro (sub req’d):

Could Games Redeem Windows Mobile and Palm’s webOS?

Image courtesy Flickr user nathangibbs.

With chip makers continuing to increase the number of cores they include on each new generation of their processors, perhaps it's time to rethink the basic architecture of today's operating systems, suggested Dave Probert, a kernel architect within the Windows core operating systems division at Microsoft.

Microsoft revealed a few more details about Windows 7 Service Pack 1 yesterday, confirming it would involve a small-fry update to the operating system....

Case Study: WhatsUp keeps Legoland turnstyles ringing

The NYT on Wednesday wrote:

Google and Intel have teamed with Sony to develop a platform called Google TV to bring the Web into the living room through a new generation of televisions and set-top boxes. (...)

The partners envision technology that will make it as easy for TV users to navigate Web applications, like the Twitter social network and the Picasa photo site, as it is to change the channel.

Some existing televisions and set-top boxes offer access to Web content, but the choice of sites is limited. Google intends to open its TV platform, which is based on its Android operating system for smartphones, to software developers.

[Thanks DPic!]

[By Philipp Lenssen | Origin: Google TV? | Comments]

On Monday I had the opportunity to present the MIX 2010 Day 1 Keynote in Las Vegas (you can watch a video of it here).  In the keynote I announced the release of the Silverlight 4 Release Candidate (we’ll ship the final release of it next month) and the VS 2010 RC tools for Silverlight 4.  I also had the chance to talk for the first time about how Silverlight and XNA can now be used to build Windows Phone 7 applications.

During my talk I did two quick Windows Phone 7 coding demos using Silverlight – a quick “Hello World” application and a “Twitter” data-snacking application.  Both applications were easy to build and only took a few minutes to create on stage.  Below are the steps you can follow yourself to build them on your own machines as well.

[Note: In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu]

First make sure you’ve installed the Windows Phone Developer Tools CTP – this includes the Visual Studio 2010 Express for Windows Phone development tool (which will be free forever and is the only thing you need to develop and build Windows Phone 7 applications) as well as an add-on to the VS 2010 RC that enables phone development within the full VS 2010 as well.

After you’ve downloaded and installed the Windows Phone Developer Tools CTP, launch the Visual Studio 2010 Express for Windows Phone that it installs or launch the VS 2010 RC (if you have it already installed), and then choose “File”->”New Project.”  Here, you’ll find the usual list of project template types along with a new category: “Silverlight for Windows Phone”. The first CTP offers two application project templates. The first is the “Windows Phone Application” template - this is what we’ll use for this example. The second is the “Windows Phone List Application” template - which provides the basic layout for a master‑details phone application:

After creating a new project, you’ll get a view of the design surface and markup. Notice that the design surface shows the phone UI, letting you easily see how your application will look while you develop. For those familiar with Visual Studio, you’ll also find the familiar ToolBox, Solution Explorer and Properties pane.

For our HelloWorld application, we’ll start out by adding a TextBox and a Button from the Toolbox. Notice that you get the same design experience as you do for Silverlight on the web or desktop. You can easily resize, position and align your controls on the design surface. Changing properties is easy with the Properties pane. We’ll change the name of the TextBox that we added to username and change the page title text to “Hello world.”

We’ll then write some code by double‑clicking on the button and create an event handler in the code-behind file (MainPage.xaml.cs).

We’ll start out by changing the title text of the application. The project template included this title as a TextBlock with the name textBlockListTitle (note that the current name incorrectly includes the word “list”; that will be fixed for the final release.)  As we write code against it we get intellisense showing the members available.  Below we’ll set the Text property of the title TextBlock to “Hello “ + the Text property of the TextBox username:

We now have all the code necessary for a Hello World application.  We have two choices when it comes to deploying and running the application. We can either deploy to an actual device itself or use the built‑in phone emulator:

Because the phone emulator is actually the phone operating system running in a virtual machine, we’ll get the same experience developing in the emulator as on the device. For this sample, we’ll just press F5 to start the application with debugging using the emulator.  Once the phone operating system loads, the emulator will run the new “Hello world” application exactly as it would on the device:

Notice that we can change several settings of the emulator experience with the emulator toolbar – which is a floating toolbar on the top right.  This includes the ability to re-size/zoom the emulator and two rotate buttons.  Zoom lets us zoom into even the smallest detail of the application:

The orientation buttons allow us easily see what the application looks like in landscape mode (orientation change support is just built into the default template):

Note that the emulator can be reused across F5 debug sessions - that means that we don’t have to start the emulator for every deployment. We’ve added a dialog that will help you from accidentally shutting down the emulator if you want to reuse it.  Launching an application on an already running emulator should only take ~3 seconds to deploy and run.

Within our Hello World application we’ll click the “username” textbox to give it focus.  This will cause the software input panel (SIP) to open up automatically.  We can either type a message or – since we are using the emulator – just type in text.  Note that the emulator works with Windows 7 multi-touch so, if you have a touchscreen, you can see how interaction will feel on a device just by pressing the screen.

We’ll enter “MIX 10” in the textbox and then click the button – this will cause the title to update to be “Hello MIX 10”:

We provide the same Visual Studio experience when developing for the phone as other .NET applications. This means that we can set a breakpoint within the button event handler, press the button again and have it break within the debugger:

Rather than just stop with “Hello World” let’s keep going and evolve it to be a basic Twitter client application.

We’ll return to the design surface and add a ListBox, using the snaplines within the designer to fit it to the device screen and make the best use of phone screen real estate.  We’ll also rename the Button “Lookup”:

We’ll then return to the Button event handler in Main.xaml.cs, and remove the original “Hello World” line of code and take advantage of the WebClient networking class to asynchronously download a Twitter feed. This takes three lines of code in total: (1) declaring and creating the WebClient, (2) attaching an event handler and then (3) calling the asynchronous DownloadStringAsync method.

In the DownloadStringAsync call, we’ll pass a Twitter Uri plus a query string which pulls the text from the “username” TextBox. This feed will pull down the respective user’s most frequent posts in an XML format. When the call completes, the DownloadStringCompleted event is fired and our generated event handler twitter_DownloadStringCompleted will be called:

The result returned from the Twitter call will come back in an XML based format.  To parse this we’ll use LINQ to XML. LINQ to XML lets us create simple queries for accessing data in an xml feed. To use this library, we’ll first need to add a reference to the assembly (right click on the References folder in the solution explorer and choose “Add Reference):

We’ll then add a “using System.Xml.Linq” namespace reference at the top of the code-behind file at the top of Main.xaml.cs file:

We’ll then add a simple helper class called TwitterItem to our project. TwitterItem has three string members – UserName, Message and ImageSource:

We’ll then implement the twitter_DownloadStringCompleted event handler and use LINQ to XML to parse the returned XML string from Twitter.  What the query is doing is pulling out the three key pieces of information for each Twitter post from the username we passed as the query string. These are the ImageSource for their profile image, the Message of their tweet and their UserName. For each Tweet in the XML, we are creating a new TwitterItem in the IEnumerable<XElement> returned by the Linq query. 

We then assign the generated TwitterItem sequence to the ListBox’s ItemsSource property:

We’ll then do one more step to complete the application. In the Main.xaml file, we’ll add an ItemTemplate to the ListBox. For the demo, I used a simple template that uses databinding to show the user’s profile image, their tweet and their username.

Now, pressing F5 again, we are able to reuse the emulator and re-run the application. Once the application has launched, we can type in a Twitter username and press the  Button to see the results. Try my Twitter user name (scottgu) and you’ll get back a result of TwitterItems in the Listbox:

Try using the mouse (or if you have a touchscreen device your finger) to scroll the items in the Listbox – you should find that they move very fast within the emulator.  This is because the emulator is hardware accelerated – and so gives you the same fast performance that you get on the actual phone hardware.

Silverlight and the VS 2010 Tools for Windows Phone (and the corresponding Expression Blend Tools for Windows Phone) make building Windows Phone applications both really easy and fun. 

At MIX this week a number of great partners (including Netflix, FourSquare, Seesmic, Shazaam, Major League Soccer, Graphic.ly, Associated Press, Jackson Fish and more) showed off some killer application prototypes they’ve built over the last few weeks.  You can watch my full day 1 keynote to see them in action. I think they start to show some of the promise and potential of using Silverlight with Windows Phone 7.  I’ll be doing more blog posts in the weeks and months ahead that cover that more.

Hope this helps,

Scott

• 5,666,293: Downloading operating system software through a broadcast channel
• 5,635,979: Dynamically programmable digital entertainment terminal using downloaded software to control broadband data operations
• 5,608,447: Full service network
• 6,367,078: Electronic program-guide system with sideways-surfing capability
• 7,561,214: Two-dimensional navigation of multiplexed channels in a digital video distribution system
• 6,055,077: Multimedia distribution system using fiber optic lines
• 5,864,415: Fiber optic network with wavelength-division-multiplexed transmission to customer premises
• 6,381,748: Apparatus and methods for network access using a set-top box and television

The forthcoming Ubuntu release, Lucid Lynx, has a lot of good things going for it but one little change is causing a great deal of angst among users. That change is the switching of the window buttons that enable one to close, maximise or minimise a window from the right to the left.

The dominant desktop operating system, Windows, has these three buttons on the top right hand corner of a window - from the outer they are in this order - close, maximise and minimise. Mac OSX has the three buttons on the top left-hand corner of the window and the order from the outside is close, minimise, maximise.

Lucid Lynx, now in its third alpha release, has the buttons on the left top of the window and the order, from the outer, is maximise, minimise and close.

Those who have objected to the change - and there are plenty of users in this category - have been provided a remedy: run this command - gconftool-2 --set /apps/metacity/general/button_layout --type string "menu:minimize,maximize,close"

Given that Ubuntu users are generally more inclined to use graphical interfaces for everything, this is not a solution that is bound to endear users to the distribution.

After 109 messages were posted about this change by users and developers, Canonical founder Mark Shuttleworth posted the following: "Moving everything to the left opens up the space on the right nicely, and I would like to experiment in 10.10 with some innovative options there. It's much easier to do that if we make this change now." Some of Shuttleworth's later posts were not quite as diplomatic, especially one which ended this way: "This is not a democracy. Good feedback, good data, are welcome. But we are not voting on design decisions."

Some users have waxed voluble, giving their own reasons why they think the change is not for the better; others have pointed to polls that indicate they are right. A few have supported the decision and some don't appear to care.

According to the schedule laid out by Canonical, the first beta release of Lucid Lynx was due for release yesterday but at the time of writing downloads were not yet available. There will be a second beta on April 8, a release candidate on April 22 and the final release will be on April 29.

Windows Mobile 6.x can multitask, and it can run applications written in native code. Windows Phone 7 Series can do neither of these things. The reasons are not philosophical, however: Microsoft has no problem with either concept per se. They're practical.

The hardware is powerful enough. The underlying operating system, Windows CE 6, can multitask just fine. The built-in applications also have multitasking capabilities—mobile IE will, for example, continue to download pages in the background, and the Zune application will play music in the background. Where multitasking is absent is with third-party software. Though this has been expected for weeks, it's only with the release of the development environment that positive official confirmation has arrived: any time the Start hardware button is pressed (which returns the phone to the Start screen), the current third-party application is terminated.

Read the comments on this post

Windows Mobile 6.x can multitask, and it can run applications written in native code. Windows Phone 7 Series can do neither of these things. The reasons are not philosophical, however: Microsoft has no problem with either concept per se. They're practical.

The hardware is powerful enough. The underlying operating system, Windows CE 6, can multitask just fine. The built-in applications also have multitasking capabilities—mobile IE will, for example, continue to download pages in the background, and the Zune application will play music in the background. Where multitasking is absent is with third-party software. Though this has been expected for weeks, it's only with the release of the development environment that positive official confirmation has arrived: any time the Start hardware button is pressed (which returns the phone to the Start screen), the current third-party application is terminated.

Read the comments on this post