Category Archives: microsoft

Office 2010 puts SharePoint in the centre

Microsoft has released a semi-public preview of Office 2010 – not a beta, so more than ever subject to change – as announced at its Worldwide Partner Conference in New Orleans. I’ve been trying it out, and wrote a quick review for The Register.

For the most part this is a refinement of Office 2007 rather than anything new and radical. That’s not a surprise; Microsoft’s boldest ideas (like the Ribbon) tend to survive for at least two versions before being sidelined, and I doubt the market would have responded well to anything disruptive this time around.

Still, there are two things which deserve highlighting. One is 64-bit; this is overdue and most welcome, even though many, probably most users will not notice the difference. For those that do, it really matters.

The other is the web applications. Although the obvious spin on this is that Microsoft is taking on the likes of Google, Zoho and Adobe Acrobat.com, it is important not to miss the other angle, which is that SharePoint is now firmly in the centre of Office. The web applications are built on SharePoint, and for the first time you can do your work equipped with nothing more than a browser.

Office Groove is now called SharePoint Workspace and lets you synchronize a SharePoint site to your local PC or laptop.

Presuming this works satisfactorily, it makes SharePoint both more usable and more compelling. I know plenty of small businesses who have looked at SharePoint in Small Business Server but never been able to make sense of it; these new approaches may well make the difference.

A side effect, which I am sure has not gone unnoticed by the folk at Redmond, is that shifting away from SharePoint to OpenOffice is harder then shifting from Office to OpenOffice. Lock-in is alive and well.

Another snag with SharePoint is that it gets very expensive once you start trying to use all its features. However, this is what I was told about licensing the web applications:

The Web apps will be licensed along with the Office client apps, so when a business purchases Office through their volume licensing agreement, they get the license to run Web apps on their own servers.  For customers of Microsoft Online Services (SharePoint and Exchange hosted by Microsoft) customers will be able to subscribe to the Web apps.

It doesn’t sound too bad; and the hosted option is important to note as well. Further, there will be some kind of free option:

400 million Windows Live consumers will have access to Office Web applications at no cost.

One day, Microsoft should start taking stuff out of Office, rather than putting it in. Who would not want a leaner Outlook? Maybe the new web applications built with Silverlight are the beginning of just such a new generation. 

I’ve posted some screenshots and further comments here.

Is Mono safe to use?

Microsoft has promised not to sue those who develop implementations of its C# language and Common Language Infrastructure – the heart of .NET.

You might assume that to be good news for Mono, the open source implementation of .NET sponsored by Novell; and I suppose it is, though not in any major way.

The key point here is that Microsoft’s .NET platform goes well beyond what is covered by the promise. ASP.NET, Windows Forms, ADO.NET, Windows Presentation Foundation, Silverlight: all this falls outside. The promise covers only what is standardised by ECMA.

Mono leader Miguel de Icaza is clear about the differences in his post, and says Mono will be split into safe and – presumably – unsafe parts:

In the next few months we will be working towards splitting the jumbo Mono source code that includes ECMA + A lot more into two separate source code distributions. One will be ECMA, the other will contain our implementation of ASP.NET, ADO.NET, Winforms and others.

A good thing? Well, it could help promote the core of Mono in the open source community, which is wary. Open source champion Richard Stallman recently stirred up debate on the subject by proclaiming C# dangerous, in what has become a somewhat perplexing post:

It is dangerous to depend on C#, so we need to discourage its use. … The problem is not unique to Mono; any free implementation of C# would raise the same issue. The danger is that Microsoft is probably planning to force all free C# implementations underground some day using software patents.

he says (and is unlikely to be comforted by Microsoft’s recent moves), though he adds:

This is not to say that implementing C# is a bad thing. Free C# implementations permit users to run their C# programs on free platforms, which is good. (The GNU Project has an implementation of C# also, called Portable.NET.) Ideally we want to provide free implementations for all languages that programmers have used.

Confusing. Still, it’s a valid and important question. Is Mono safe to use?

I have been asking myself this for many years; and have asked Microsoft about it on a number of occasions with no clear answer. However, to me the breakthrough came when Moonlight was announced, an implementation of Silverlight for Linux for which Microsoft has partnered with Mono. The dual significance is first, that Microsoft is working with Mono; and second, that it shows how Microsoft has realised that overall Mono is more a benefit than a threat to its platform.

Action against Mono now seems less likely than ever. That opinion is not based on legal knowledge, but on the business & PR case.

Nevertheless, there could be limits. Stallman’s recent statement was provoked by discussions over whether Mono should be part of the default Debian install. It is not; but it is rising higher on the list of packages that are likely to be installed sooner rather than later by users, because Mono applications are growing in number.

On the server, Mono’s implementation of ASP.NET is now rather good. I’m using it on ITWriting.com for a Silverlight demo. I’ve been impressed by its compatibility with Visual Studio, though I’ve also found it increasing resource usage more than I would like. I’m using what is now an old version though, so I expect this to improve.

The cost savings in using Linux+Mono rather than Windows+ASP.NET are significant, which implies that the potential cost to Microsoft is significant too. It’s only a potential cost, because frankly the official platform is still less risky for a commercial deployment, from a technical rather than legal perspective. Mono is currently more likely to attract free or hobbyist users; but that could change. If Microsoft saw server license sales bleeding away because of Mono, my guess is that there would be rumbles.

What then of de Icaza’s move to separate Mono into safe and unsafe parts? I see the sense of it, but wonder if it could be counter-productive. While Mono is, errm, monolithic, Microsoft cannot take action against the unsafe parts without also blocking the safe parts. After the split, it will be easier for Microsoft to agitate about the pieces of Mono which might (or might not; I’m no lawyer) infringe its rights.

It still strikes me as unlikely that Microsoft would risk full-on legal action against its partner and against what is now a significant part of its platform story. However, I doubt we will get any further comfort from the company, beyond what it has already given.

*updated to acknowledge that Silverlight and WPF are covered by the open spec promise – see links in the comments.

Symbian appeals to Traveling Geeks: develop for our platform

I attended a Traveling Geeks event in London last night, a party sponsored mainly by Symbian and NESTA. I returned with a large pile of business cards from folk involved in a diverse range of initiatives. Kate Arkless Gray told me about Save our Sounds, a BBC World Service project to archive and map interesting and endangered sounds from around the world; while Sarah Blow sought to convince me that I don’t just need Twitter, I need Tweetmeme to track what is happening on the world’s most public short message service.

Digitrad wants me to sign up for yes.tel, which means registering a .tel domain with its service and using it as a public home page, email address and voicemail box. It’s not clear to me what advantage it has over all the other third-parties who want to own my digital identity, except that Digitrad is smaller and therefore less threatening than Google or Facebook. I’m happy with conventional registrars.

From my perspective, Symbian managed to dominate the event with engaging images around the walls and numerous representatives to talk up its mobile platform. The Symbian story is an interesting one. Originally developed by Psion, it was spun off in 1998 into an independent company co-owned by the giants of mobile at the time: Ericsson, Nokia, Motorola and Psion itself. Nokia proceeded to acquire more and more of Symbian, achieving greater control but also – it seemed to me – reducing the chance it once had of becoming an industry standard. Other vendors became wary of depending on an operating system controlled by a competitor. Linux had greater appeal – as seen in both the Palm Pre and Google Android – while Apple did its own thing with OS X on the iPhone, and Microsoft ploughed on with Windows Mobile.

Last year Nokia responded to the pressure by announcing plans to acquire Symbian in its entirety and then to give it to a new Symbian Foundation, an open source, collaborative project along the same lines as Eclipse. Developers can sign up to get the tools for programming Symbian applications in C++, Java, Python, Ruby, Adobe Flash, C# or HTML/JavaScript. I was told that Symbian intends to be even more open than Android. It restores Symbian’s cross-industry potential though there is now more competition.

Should you develop for Symbian? The Symbian Foundation is a great move, but in the App Store era I suspect deployment issues are even more critical than the quality of the OS or its development tools. Developers will go where they can find customers. Apple is reaping the rewards of controlling the entire platform and marginalizing the mobile operators.

Still, as long as Apple is content for the iPhone to be punishingly expensive, it leaves space for others. The appeal of Symbian will depend not only on its success among device manufacturers, but also on how easy it is for users to find, purchase and install applications.

There is also the matter of reliable, fast and affordable internet access, the lack of which has so far spoilt every mobile device I have owned.

Clipboard.Clear … oops

Bob Warfield is upset because he lost some work. He copied some text in Live Writer, deleted it, then opened Word and tried to paste. No go .. clipboard empty.

Frustrating, but is he right to call his post Microsoft: Bad User Experience Is Cultural, on the grounds that Word is designed to clear the clipboard every time it opens?

Here’s a bit more information. First, Word does not do that here. Second, if it weren’t that I do equally silly things I’d suggest that it is always risky to entrust the clipboard with your work without a backup.

That said, I can understand why Word might appear to clear the clipboard on start-up. It could be a bug, or it could be an add-in of some kind. The thing is, it is really easy to clear the clipboard in code. Just call EmptyClipboard and you’re done. There are ways to do it in VBA too, via a DataObject, or in .NET via Clipboard.Clear.

As Warfield’s case shows, clearing the clipboard in code can be deeply user-hostile. Should Windows prevent it? Difficult, because if your application or add-in implements clipboard functionality, it is the correct thing to do when the user selects Cut, Copy or Paste.

Lessons? A warning, I guess, not to use the clipboard for any purpose other than a user-initiated clipboard action – though I guess it can be tempting if you are hacking some sort of inter-process data exchange.

Second, when Windows lets you down it is not necessarily Microsoft culture to blame. There is an argument though … applications that don’t conform to Windows guidelines are a big problem and without them things like User Account Control might not need to exist; and that is Microsoft’s fault in a way, because of the history of Windows, its changing guidelines, and the inability of even Microsoft to stick to them in the past. Maybe Microsoft is partly to blame for the wild culture of third-party Windows apps.

This is a blog entry rather than a comment because Warfield’s blog needs registration to comment, and I am allergic.

Mozilla takes aim at Flash and Silverlight with Firefox 3.5

I reviewed Firefox 3.5 for The Register. I found the new features unexciting from a user perspective, but not so for developers. The new TraceMonkey JavaScript engine, improvements to the Canvas element, JavaScript threading and various bits of HTML 5.0 make this a more powerful platform for web applications – provided that you workaround the problem of users with Internet Explorer. The arrival of video and audio elements is also worth highlighting:

Another new feature is SVG effects for HTML, including masking, filtering and clipping. The point I made in the review is that this is a shot at Adobe as well as Microsoft. Although it is a long way from a viable alternative to Flash for now, the direction is clear.

That does not mean it will succeed. On the other hand, if Apple, Google and Mozilla pull together in making browser standards rich enough not to need plug-ins for most of the scenarios where Flash is used today, this could disrupt Flash momentum.

What about IE? That’s the big question. Here’s a few questions:

1. Will Microsoft implement these standards or hold back, arguing that Silverlight makes them unnecessary?

2. Will IE retain its market dominance – still over 65% last time I looked, even though it is losing among developers and influencers?

3. Could IE add-ons along the lines of Screaming Monkey for JavaScript and the Mozilla Canvas plug-in that has been discussed pull IE along anyway?

This article by Ryan Paul from last year discusses the issue. He says, why shouldn’t Adobe embrace HTML 5.0 rather than fighting it:

Although Canvas arguably competes with Adobe’s Flash plugin in a certain set of use cases, it’s worth noting that Adobe doesn’t generate revenue from the Flash plugin itself. Adobe cashes in on Flash by selling its powerful authoring tools, which the company could easily extend to support standards-based web technologies.

It’s a fair point; but given the commercial advantages of owning the platform, as opposed to being just another tools vendor, I doubt Adobe would make this shift unless it saw no realistic alternative. Even fully open-sourcing the Flash runtime would be less risky.

You can find Firefox here, and the developer features are described here.

Eclipse survey shows Windows decline

In May 2009 the open source Eclipse project surveyed its users. Visitors to the Eclipse site were asked to complete a survey, and 1365 did so. That’s out of around 1 million visitors, which shows how much we all hate surveys. Anyway, this report [pdf] was the result. A similar survey [pdf] was carried out in 2007, potentially making a valuable comparison, though the earlier survey has different questions making direct comparisons difficult in most cases, which is a shame. I especially missed the detail on which Eclipse projects are used most which is well covered in the 2007 report.

Here is what I found interesting. First, there’s a shift towards Linux and Apple Mac in the desktops developers use for Eclipse. In 2007 it was 73.8% Windows, 20% Linux and 3.5% Mac. In 2009 it is 64% Windows, 26.9% Linux and 6.9% Mac.

This is echoed in deployment platforms too (client and server). In 2007 it was 46.5% Windows, 36.6% Linux, 1% Mac; today it is 40.5% Windows, 42.7% Linux, 3% Mac.

Those surveyed were asked what other IDEs they used. I noticed that Microsoft Visual Studio and NetBeans feature fairly strongly; I also noticed that Embarcadero’s JBuilder is hardly a blip on the chart – intriguing, given how popular this used to be in the pre-Eclipse era.

The most popular code management tool is Subversion (57.5%) followed by CVS (20%). For build tools, Ant (33.4%) and Maven (18%).

Here’s an intriguing one: I often hear that Java is only successful on the server. That presumption is not supported by this survey. 23.4% said that desktop client apps are the primary type of software they are developing, compared to 30.2% server, and 24.7% web or RIA apps.

The preferred app server is Apache Tomcat (34.8%) followed by JBoss (12.7%) and Websphere (6.9%).

The most popular database manager is MySQL (27.7%) followed by Oracle (27.3%). That’s 55% for Sun+Oracle, of course, though bear in mind that many of the MySQL users are likely attracted by its free licence.

Before drawing too many conclusions, bear in mind that it is a small sample self-selected by people willing to take the survey; apparently it was also featured by a German technology site which resulted in a larger response from German visitors.

Although it suggests a declining use of Windows – which is especially plausible given the trend towards web applications – it does not prove it beyond the Eclipse community.

And next time – how about using the same questions, which would make it possible to identify trends?

I’ve also written about Eclipse here: The Eclipse Conundrum: can it grow without hurting its contributors?

Upgrade to Windows 7 in Europe: confusing as expected

PC manufacturers are now publicising their upgrade deals for Windows 7. Buy a machine with Vista today, get a free upgrade to Windows 7 later.

Except the software is not an upgrade as such – it’s a replacement. Here are the details from Asus, for example, which note:

The Windows® 7 Upgrade Option Program requires a clean installation of the Windows 7 upgrade media.  All personal data and settings, including documents, pictures, files, programs, music and video, should be backed-up prior to performing the clean installation of Windows 7.  After installation of Windows 7, the end user should then re-install all personal data and restore settings. Visit http://windows.microsoft.com/upgrade-windows-E for important information.

I think (and hope) that the referenced Microsoft site is only a placeholder, since its instructions are far from detailed:

… before installing E editions of Windows 7, make sure to back up your files and settings to an external hard disk, USB Flash Drive, or other media. After the installation, move your files and settings back to your PC and reinstall the programs you want to keep using.

Important: E editions of Windows 7 do not include Internet Explorer. We recommend that you get an Internet browser from Microsoft or another software manufacturer and have it available on a CD/DVD or other media so you can install it after you install Windows 7.

It is not a trivial exercise. There is a Windows Easy Transfer wizard for XP and Vista, and I presume this will be used:

Although this does a reasonable job, there are plenty of gotchas. The most obvious is that it generally cannot transfer applications, only data. It gives the user options concerning which folders to copy, but knowing which are needed may not be easy. It does not cope well if you partition the new computer in a different way. It presumes you have sufficient intermediate storage, which could be a problem if you have many gigabytes of media files to copy and no suitable external drive. You could get into difficulties with badly-behaved applications that store data in Program Files.

There is also a chicken-and-egg problem with reinstalling applications. You are meant to reinstall applications, and then run Easy Transfer, as otherwise installing an application might overwrite the settings you have transferred. On the other hand, if the reinstalled application has a different version than the source application (which is not unlikely if it is downloaded) then transferring settings over the top could mess it up.

Personally I’m wary of the tool. If I have to do this sort of reinstallation, I take a minimalist approach and only transfer documents, plus a few select settings that I understand. Without Easy Transfer though, it is easy to lose things like emails and address books, or browser bookmarks, the lack of which can cause aggravation.

Then there’s the matter of the web browser. Asus doesn’t say whether it is supplying one on its “driver” DVD.

Overall, I’m expecting this to be good business for armies of home PC support people.

Discussion of the reasons for this is here and here.

EU responds to questions on Microsoft’s plans for Windows 7

Events in the EU’s case against browser bundling in Windows have taken an odd twist. The case was brought originally by Opera, which complained that it couldn’t sell its browser because IE came free with Windows. Other interested parties such as Google and Mozilla joined in. In January the EU issued a statement of objection:

The evidence gathered during the investigation leads the Commission to believe that the tying of Internet Explorer with Windows, which makes Internet Explorer available on 90% of the world’s PCs, distorts competition on the merits between competing web browsers insofar as it provides Internet Explorer with an artificial distribution advantage which other web browsers are unable to match. The Commission is concerned that through the tying, Microsoft shields Internet Explorer from head to head competition with other browsers which is detrimental to the pace of product innovation and to the quality of products which consumers ultimately obtain. In addition, the Commission is concerned that the ubiquity of Internet Explorer creates artificial incentives for content providers and software developers to design websites or software primarily for Internet Explorer which ultimately risks undermining competition and innovation in the provision of services to consumers.

Microsoft’s problem: whatever the merits of the EU’s case, it is desperate to have a single global launch for Windows 7, to put Vista behind it, to persuade XP users to upgrade, and to compete with Apple. The EU had in mind some sort of install menu where users could choose a browser; but Microsoft unilaterally decided to unbundle Internet Explorer from Windows 7 completely, in a special Windows E edition. Today Microsoft also confirmed that because of the EU’s case, it will not offer upgrade editions of Windows 7 in Europe.

The odd thing is, Microsoft has no guarantee that its actions will necessarily appease the EU, as confirmed when I asked about this. The EU’s immediate response was not comforting:

At the level of both computer manufacturers and retail sales, the Commission’s Statement of Objections (SO) suggested that consumers should be provided with a genuine choice of browsers. Given that over 95% of consumers acquire Windows pre-installed on a PC, it is particularly important to ensure consumer choice through the computer manufacturer channel.

As for retail sales, which amount to less than 5% of total sales, the Commission had suggested to Microsoft that consumers be provided with a choice of web browsers. Instead Microsoft has apparently decided to supply retail consumers with a version of Windows without a web browser at all. Rather than more choice, Microsoft seems to have chosen to provide less.

I spoke to Jonathan Todd, European Commission spokesman on competition:


What could happen if Windows 7E doesn’t satisfy EU requirements?

We haven’t reached any conclusions yet as to whether or not their intention would in any way be relevant to the concerns that we’ve expressed in our statement of objections. Until such time as we’ve reached our conclusions it’s difficult to comment. If we were to find that there had been a breach of the anti-trust rules we could fine them and we could require them to change their business practices.

What is the likely timescale of the EU determining whether or not the planned release of Windows 7 conforms to the requirements?

Clearly we’re doing that as quickly as possible.

How long?

That depends to a certain extent on Microsoft.

What does Microsoft need to do to expedite the process?

As we indicated in our statement, one of our concerns was that we would have to verify whether the technical separation of Internet Explorer from Windows was not negated by other actions by Microsoft, for example as regards the terms and conditions under which Internet Explorer would be made available to computer manufacturers.

There’s some tension between the usability issues that people will face when they try and acquire Windows 7, for example that acquiring an operating system without a browser could be inconvenient, and the …

[interrupts] Let me make it clear, the commission has never ever suggested to Microsoft that they should supply Windows 7 without a browser.

This has never been one of the suggestions that we’ve made to them.

It is not necessarily relevant to resolving the concerns that we have about Microsoft’s conduct.

The considerations are that consumers have to have genuine choice about which browser they use.

Why do the same conditions not apply to Apple and other operating system vendors?

For the extremely simple reason that Apple doesn’t enjoy a dominant position of the operating system market. It’s not a problem to have a dominant position, but when you are in a dominant position in the market, and they have over 90% of the operating system market, when you are in a dominant position that places constraints on what you can and cannot do.

I suppose the counter argument is that if you are in the operating system market you need to be allowed to offer similar features to others in that same space?

Listen. You can do what you like in terms of bundling if you are not in a dominant position. If you are in a dominant position your actions have a direct affect on competition throughout that market. That’s the difference.

How low would Microsoft’s share of the market need to dip before they would no longer be required to hobble their product for the sake of competition law?

I don’t agree with your analogy about hobbling their product. What we’re talking about is making sure that consumers are not hobbled by what is imposed on them by Microsoft.

There are advantages to having a browser integrated with the operating system. For example, it means that a single vendor is managing security, that updates are coming down in a streamlined fashion, and that within enterprises the functions of the browser can be managed with the same tools that are used to manage the rest of the operating system.

If you bundle in your browser and you make it difficult for other browsers to get a market share, then you’re denying consumers choice and you’re taking away the incentive for innovation. Internet Explorer wasn’t updated for, how many years?

For five years, which was disgraceful by any measure.

Because they didn’t have an incentive to do so.

They did have an incentive to do so, but they didn’t realise that they did, and in fact Microsoft is losing market share quite rapidly in browsers which throws into doubt whether legislation is actually necessary.

You’ve read our statement. We’ve never ever suggested that Windows should be supplied without a browser. The heart of our case is genuine consumer choice. Therefore, certainly as regards retail sales of Windows 7, they appear to be taking away choice from consumers rather than giving them more.

I don’t think many users are going to be operating Windows without a browser so they are going to make that choice at some point.

Yes, but as we all know, if you are buying an operating system that doesn’t have a browser included it’s that much more difficult to actually get a browser.

If you require a software manufacturer to bundle another company’s software product with their own, it raises questions about security, about support, about updates, which are difficult ones, I understand why Microsoft might not be willing to do so.

We both know also that Microsoft claimed for many years it was technically impossible to separate Internet Explorer from the operating system.

Microsoft does not intend to remove the parts of IE that could reasonably be described as part of the operating system. All it intends to remove is the web browser as the user sees it.

For many years Microsoft said it is impossible to sell the operating system without a browser, that it’s not possible to separate out Internet Explorer from the operating system.


Todd said more than I had expected. There are a few things I find it hard to make sense of. The EU’s complaint seems to be not only about lack of competition, but about its consequences, spelt out as lack of innovation in browsers, and Microsoft’s unfairly-gained market share for IE. This made perfect sense a couple of years ago, but not so much now. Browser innovation is rapid – look at Google Chrome, WebKit and Safari, Mozilla FireFox, Opera (which never went away) – and Microsoft is already losing market share in browsers, a point which Todd did not answer.

On the other hand, I do not want to downplay Microsoft’s discreditable action in first energetically developing IE to squash the competition, and then leaving it frozen to promote Windows rather than the Web as the platform of choice. A disgrace; but one which the market is solving without EU legislation.

As for current developments, could Microsoft be trying to stimulate antipathy towards the EU by deliberately inconveniencing them with Windows E? Or is this really the company’s best effort to satisfy the EU while still releasing Windows 7 on time? I guess the latter; but it is an odd state of affairs.

Technorati Tags: ,