Saturday, February 7, 2009

Microsoft sees end of Windows era

Microsoft has kicked off a research project to create software that will take over when it retires Windows.
Called Midori, the cut-down operating system is radically different to Microsoft's older programs.
It is centred on the internet and does away with the dependencies that tie Windows to a single PC.
It is seen as Microsoft's answer to rivals' use of "virtualisation" as a way to solve many of the problems of modern-day computing.
Tie breaking
Although Midori has been heard about before now, more details have now been published by Software Development Times after viewing internal Microsoft documents describing the technology.
Midori is believed to be under development because Windows is unlikely to be able to cope with the pace of change in future technology and the way people use it.
Windows worked well in an age when most people used one machine to do all their work. The operating system acted as the holder for the common elements Windows programs needed to call on.
"If you think about how an operating system is loaded," said Dave Austin, European director of products at Citrix, "it's loaded onto a hard disk physically located on that machine.
"The operating system is tied very tightly to that hardware," he said.
That, he said, created all kinds of dependencies that arose out of the collection of hardware in a particular machine.
This means, he said, that Windows can struggle with more modern ways of working in which people are very mobile and very promiscuous in the devices they use to get at their data - be that pictures, spreadsheets or e-mail.
Equally, he said, when people worked or played now, they did it using a combination of data and processes held locally or in any of a number of other places online.
When asked about Midori by BBC News, Microsoft issued a statement that said: "Midori is one of many incubation projects underway at Microsoft. It's simply a matter of being too early in the incubation to talk about it."
Virtual machines
Midori is widely seen as an ambitious attempt by Microsoft to catch up on the work on virtualisation being undertaken in the wider computer industry.
Darren Brown, data centre lead at consulting firm Avanade, said virtualisation had first established itself in data centres among companies with huge numbers of servers to manage.
Putting applications, such as an e-mail engine or a database, on one machine brought up all kinds of problems when those machines had to undergo maintenance, needed updating or required a security patch to be applied.
By putting virtual servers on one physical box, companies had been able to shrink the numbers of machines they managed and get more out of them, he said.
"The real savings are around physical management of the devices and associated licensing," he said. "Physically, there is less tin to manage."
Equally, said Mr Brown, if one physical server failed the virtualised application could easily be moved to a separate machine.
"The same benefits apply to the PC," he said. "Within the Microsoft environment, we have struggled for years with applications that are written so poorly that they will not work with others.
"Virtualising this gives you a couple of new ways to tackle those traditional problems," he said.
Many companies were still using very old applications that existing operating systems would not run, he said. By putting a virtual machine on a PC, those older programs can be kept going.
A virtual machine, like its name implies, is a software copy of a computer complete with operating system and associated programs.
Closing Windows
"On the desktop we are seeing people place great value in being able to abstract the desktop from actual physical hardware," said Dan Chu, vice president of emerging products and markets at virtualisation specialist VMWare.
Some virtual machines, he said, acted like Windows PCs to all intents and purposes. But many virtual machines were now emerging that were tuned for a particular industry, sector or job.
"People take their application, the operating system they want to run it against, package it up along with policy and security they want and use that as a virtual client," he said.
In such virtual machines, the core of the operating system can be very small and easy to transfer to different devices. This, many believe, is the idea behind Midori - to create a lightweight portable operating system that can easily be mated to many different applications.
Microsoft's licensing terms for Windows currently prohibited it acting this way within a virtual appliance, said Mr Chu.
Michael Silver, research vice president at Gartner, said the development of Midori was a sensible step for Microsoft.
"The value of Microsoft Windows, of what that product is today, will diminish as more applications move to the web and Microsoft needs to edge out in front of that," he said.
"I would be surprised if there was definitive evidence that nothing like this was not kicking around," he said.
The big problem that Microsoft faced in doing away with Windows, he said, was how to re-make its business to cope.
"Eighty percent of Windows sales are made when a new PC is sold," he said. "That's a huge amount of money for them that they do not have to go out and get.
"If Windows ends up being less important over time as applications become more OS agnostic where will Microsoft make its money?" he asked.
Select Flickr users begin to get Getty invites
The partnership between Flickr and Getty Images is finally moving forward. Early Wednesday the Yahoo-owned photo-sharing service announced that invitations from Getty have been going out in high numbers. Some members who have had one or more of their images chosen to be on Getty's sale site could have gotten notice as early as last week.
Originally announced in July, the special Flickr-branded Getty collection will be launching in early March. It's the first official move by Flickr where users can sell their images, although all the purchasing and organization will be done on Getty's end. In the interim Getty has set up a Flickr group where those selected can discuss licensing and rights issues if there are any.
Unlike microstock services such as iStockPhoto, Shutterstock, and Fotolia, the Getty/Flickr partnership will be royalty-free and rights-managed only. It's also going to continue to be invite-only, whereas the other sites allow user submissions.
Twitter puts new limits on API calls: Who's affected
Twitter on Tuesday announced a new limit on third-party access to its service via its application programming interface, or API. Later this week, according to Twitter developer Alex Payne, the Twitter platform will limit API calls from a single IP address at approved ("whitelisted") Twitter services to 20,000 per hour. This will affect services that use Twitter APIs in bulk for non-messaging functions, like managing followers. Normal calls to read and write status updates are not part of this change.
There is already an API limit in place for third-party applications that give users general access to their Twitter accounts and message. AIR apps like Twhirl and TweetDeck, and iPhone apps like TwitterFon, can't hit the Twitter service more than 70 times an hour. Twitter has been known to lower this limit when the service gets overloaded. But for most end users, the limit is not noticeable. Twitter client apps are generally configured by default to access the Twitter services far less frequently than Twitter allows.
But for developers who are working on apps that extend Twitter in new ways, the new limit could have a serious impact. Services like SocialToo, which does follower management for Twitter users, rely on the Twitter API to gather data on behalf of its users. (Another product that might be affected: Mr. Tweet.) The problem, according to SocialToo developer Jesse Stay, is that for some of its individual users, getting the basic information they need requires not one API call, as they would prefer, but rather hundreds, due to the way the Twitter platform functions.
The complaints, then, from developers, are two-fold. First, as Stay says, "Why develop for the Twitter platform any more if we know we can only grow to your limit?" Related to that are complaints about the Twitter API being inefficient. It shouldn't take a hundred calls to gather one chunk of data, developers say.
For Twitter's part, Payne says that Twitter needs to put a throttle on API access to keep the service available to all developers, and furthermore that its limit will affect fewer than 10 applications (see Is Twitter Strangling its Famous API? on ReadWriteWeb).
The Twitter back-end has had periods of not keeping up with the popularity of the service, and this new limit is clearly an attempt to get ahead of the problem, even if it annoys a few developers and hobbles some services.
What I find most surprising is that Twitter is not using this issue as an opportunity to make partners, instead of enemies, of its developers. There are several ways the company could do this, from asking developers to help them re-cast the APIs so they work for more types of applications, to passing along the cost of high-volume API use to the developers of the apps (which would also force the app developers to come up with business models of their own).
As long as Twitter keeps its service free for developers, it is essentially asking for trouble. Developers will continue to build apps that add value to users but stress the platform--in the absence of constraints, why should they do any different? Limiting access to the platform by installing a governor on the engine will initially throttle developers' creativity, although as necessity is the mother of invention, it may also lead to even more clever solutions for improving the Twitter experience.
The logical, eventual outcome of this change should be an improvement in the Twitter API that allows the follower-management products to work more efficiently. However, Twitter developers are already working on even higher-profile updates to improve the platform's services. As the recently-updated developers' Wiki says, eagerly anticipated features like OAuth support and the open "fire hose" feed of status updates are scheduled to go into test this month or next.
Need for speed spurs Opera JavaScript overhaul

With Web applications imposing new demands on Web browsers, a previously behind-the-scenes programming technology called JavaScript is getting new visibility, and Opera is the latest case in point.
The Norwegian browser maker announced on Wednesday a new JavaScript engine project called Carakan.
Carakan runs JavaScript code about 2.5 times as fast as the Futhark engine in the alpha version of Opera 10, programmer Lars Erik Bolstad said in an Opera blog post.
Opera's main business is browsers for mobile phones, and its current JavaScript engine is optimized for minimum memory demands, but now performance is the priority, Bolstad said.
"The Web is a changing environment however, and tomorrow's advanced web applications will require faster ECMAScript execution, so we have now taken on the challenge to once again develop the fastest ECMAScript engine on the market," he said. ECMAScript is a standard group's official name for JavaScript.
JavaScript isn't the only way to build Web applications, but it's increasingly widely used. It's the foundation for Google Docs and Gmail, for example, and enables Yahoo Mail users to drag-and-drop messages into folders.
Speed is particularly important because JavaScript is used for interactive aspects of Web pages, where fast response or annoying lags are noticeable by people controlling the application. But it's also widely used for many more mundane aspects of Web pages, so faster JavaScript helps improve Web browsing performance broadly.
Opera isn't alone here with a fancy name for its JavaScript engine. Mozilla's Firefox has TraceMonkey, Google's Chrome has V8, and WebKit, the rendering engine used by Apple's Safari, has Squirrelfish Extreme. (Chrome uses Webkit for some other tasks in displaying Web pages, but not its JavaScript engine.)
For details on Opera's improvements--register-based bytecode, native code generation, and automatic object classification--check the blog post about Carakan.

Chrome takes new tack for faster JavaScript
Chrome programmers have switched out a third-party software package in favor of their own as part of Google's attempt to speed its open-source browser up more.
The change came with a key component for processing JavaScript text called regular expressions. "As we've improved other parts of the language, regexps started to stand out as being slower than the rest. We felt it should be possible to improve performance by integrating with our existing infrastructure rather than using an external library," according to a Chromium blog post by programmers Erik Corry, Christian Plesner Hansen, and Lasse Reichstein Holst Nielsen.
Thus was born Google's own project, Irregexp, the headline feature in the new developer preview version of Chrome, 2.0.160.0 (release notes). Check the blog post if you're curious about the technical details of Google's choices about native code generation, backtracking avoidance, and intermediate automaton representation.
Previously, Chrome used a supporting software package, or library, called JPCRE, a variation by the Webkit browser project of the PCRE package. That eased compatibility issues by making Chrome behave more like Apple's Safari, which is based on Webkit, but Google thinks it's got the compatibility issue in hand.
"During development we have tested Irregexp against one million of the most popular Web pages to ensure that the new implementation stays compatible with our previous implementation and the Web," the programmers said.
Separately, the programmers said they created a new third version of their JavaScript benchmark. This version specifically exercises regular expressions taken from 50 of the Web's most popular pages.
JavaScript is increasingly widely used to build sophisticated Web applications, including Google Docs and Gmail, for example.
Speed is particularly important because JavaScript is used for interactive aspects of Web pages, where fast response or annoying lags are noticeable by people controlling the application. But it's also widely used for many more mundane aspects of Web pages, so JavaScript speedup helps improve Web browsing performance broadly.
Chrome's JavaScript engine is called V8. Mozilla's Firefox has TraceMonkey, and WebKithas Squirrelfix Extreme. Opera hopes to outdo all those with its own new JavaScript engine, called Carakan.
More changes are coming to V8, though, and Google will detail some at its May developer conference, Google I/O. One session there will focus on the software, including "initiatives that will propel V8 to the next performance level," according to the session notes.
Separately, Google also released the new version 1.0.154.46 of Chrome for both its stable and beta version users on Wednesday. That version fixed a security problem and an issue with Chrome's incognito mode.
Facebook steps into OpenID Foundation
Facebook has joined the board of the OpenID Foundation and will host an OpenID Design Summit later this month, according to a post on the social network's developer blog.
This is a bit of a surprise because Facebook has developed its own universal log-in standard, Facebook Connect, which theoretically competes with the nonprofit OpenID standard. It should be noted that Facebook has not yet announced any official plans to make the two compatible, and that just joining the board and hosting an event might not quell the criticism from open-source advocates who say Facebook is still too proprietary in its nature.
Engineer Luke Shepard will be Facebook's representative on the OpenID Foundation board, a corresponding post on the OpenID blog explained, adding that Shepard has been "a huge internal advocate for OpenID" at Facebook. The board also consists of members from Google, IBM, Microsoft, PayPal, VeriSign, and Yahoo as well as seven elected "community" members. Many of the corporate board members joined about a year ago; OpenID creator Brad Fitzpatrick is now employed by Google and has helped to build its OpenSocial developer platform standard.
"Given the popularity and positive user experience of Facebook Connect, we look forward to Facebook working within the community to improve OpenID's usability and reach," the post by David Recordon and Chris Messina read.
Facebook's blog post, written by engineering VP Mike Schroepfer, expressed similar goals. "It is our hope that we can take the success of Facebook Connect and work together with the community to build easy-to-use, safe, open and secure distributed identity frameworks for use across the Web," Schroepfer wrote.
Facebook makes new push for more apps

Facebook is looking to unleash a new wave of applications to get its users creating and sharing more content.
The social-networking company has launched a number of APIs (application programming interfaces) that will let developers access content and methods for sharing in Facebook apps including Status, Notes, Links, and Video. According to a post on the Facebook developers blog Friday evening:
Specifically, your applications can now directly access all of a user's status, links, and notes via new methods and FQL calls. Your application will have access to any status, notes, or links from the active user or their friends that are currently visible to the active user. In addition, we're opening new APIs for you to post links, create notes, or upload videos for the current user, and we've made setting a user's status easier.
We're pretty excited to see what kinds of ideas you can come up with to help users create and share more content. For example, a travel application could make it really easy for users to create and share notes and upload photos and videos from a recent trip. Users could then display that content within a profile tab for that app. Or a news website could use Facebook Connect to allow users to easily post links from the site and feature all of the most recent links that a user's friends have shared from that website.
In announcing move toward greater openness, Facebook says it has seen "increasing engagement" among its users, more than 15 million of whom are updating their status daily and who are sharing more than 24 million links per month. The social network has 150 million active members.
Earlier this week, Facebook gave another nod toward openness, rather unexpectedly joining the board of the OpenID Foundation, whose designs on a universal log-in standard are something of a rival to the similar Facebook Connect.
Reaction to Friday's API news was by and large favorable among Facebook watcher, some of whom were quick to point to potential competition with microblogging service Twitter.
Said Nick O'Neill of the All Facebook blog:
Will this "more open" Facebook platform result in a new wave of applications? Probably, but I think there are still a lot of things that need to opened on the platform. My guess is that we'll see a large number of status feed applications build and while other apps will be built, any Twitter-like applications will receive the most amount of buzz.
At TechCrunch UK, Mike Butcher went on a greater length on the Twitter angle--specifically, "why I think Facebook allowing you to make your status updates public won't affect Twitter as much as some might think." Point 2 out of four:
Twitter is "mainstreaming" the Follow model faster than Facebook. Facebook's users are not used to this at all. They may well find Twitter easier to understand than changing the way they use Facebook already. What you do on Facebook is often quite different. Twitter is much more about communication/conversation.