Survey: Windows loses ground with developers

From a recent InfoWorld article:

Microsoft’s Windows platform is losing traction as a target for application developers in North America but still is the dominant platform, according to Evans Data survey results being released on Tuesday.
Free IT resource

A survey this spring of more than 400 developers and IT managers in North America found that the number of developers targeting Windows for their applications declined 12 percent from a year ago. Just 64.8 percent targeted the platform as opposed to 74 percent in 2006.

“We attribute [the decline] largely to the increase in developers beginning to target Linux and different Linux [distributions]. Both Novell and Red Hat are the two dominant ones right now,” said John Andrews, the CEO of Evans Data.

The arrival of Windows Vista likely only kept the numbers from being even worse. “I think Vista probably offset some of the decline,” Andrews said.

The share for Windows is expected to drop another 2 percent, to about 63 percent, in the next year, Andrews said.

The targeting of Linux by developers increased by 34 percent to 11.8 percent. It had been 8.8 a year ago, according to the survey. Linux targeting is expected to reach 16 percent over the next year.

Evans views the situation as a battle of Windows versus open source with open source maturing, Andrews said. Windows remains tops, though. “They’re still dominant, there’s no doubt about it,” said Andrews. Use of Windows on the development desktop remains steady.

The survey, featuring developers at enterprises and solution providers like system integrators, covered both client and server application development.

Evans Data said the shift away from Windows began about two years ago and is accelerating. Linux is benefiting as are nontraditional client devices. Evans Data also surveyed developer plans for such platforms as Unix and Mac OS but did not release those numbers.

Now, I dislike “surveys” for a variety of reasons, which I’ve detailed in the past. They’re easy to manipulate, so can often come out saying whatever it us you want them to. That being said, I think in the right context and given the right qualifiers, surveys can be extremely informative. Sure, the linked survey isn’t without issue, so shouldn’t be taken without a grain of salt (only North America for instance, doesn’t seem to take into account people using languages that don’t target a specific platform). But, it comes to a general conclusion that seems congruent with what most people are hearing. As an industry wide trend, developer support for Windows is declining. I think that’s a leading indicator and one I’d be worried of if I were Microsoft. It’s not just Linux that they’re losing to, though. It’s Linux and OS X and the web (a huge one) and platform independent technologies and mobile devices and, well you get the idea. They are fighting a rising tide. I think < 50% of developers targeting Windows will be the watershed moment. Given the current trends, that may only be a few years off.

A quick note on a related topic. I often hear people say that many Open Source applications have surprisingly large download numbers for Windows. From asking around and thinking about this, that’s not surprising at all. I’d say it should be expected, in fact. You see, the adoption of Open Source apps in many companies is a grass roots type adoption. Because of this, coupled with the fact that Windows is still by far the dominant corporate desktop, you’ll get huge numbers of developers downloading various Open Source apps for Windows so they can test them out on their workstations. Once they are comfortable with the product and have a proof of concept, they very often (but of course not always) deploy them on non-Windows infrastructures. Raw numbers alone don’t always tell the whole story. It’s about context.

–jeremy

GPLv3 Coverage

For all the coverage the process has gotten to date, the final GPLv3 was released to relatively little fanfare on Friday, June 29th. The reality, as with any legal document, is that it’s going to take a while for company and project lawyers to read through and digest their perceived implications. As anyone who’s worked in a large corporation knows, legal departments take their time on this. That means the reality is that we won’t see adoption by major projects for a little while. That’s not a bad thing, it was to be expected.

One thing that struck me about the GPLv3 process is just how much mainstream press it got. We’re talking about a software license after all. This has to be a first. Also, whether or not you like the end result of the GPLv3 I think you have to give the FSF credit. The GPLv1 was pretty much just Stallman and even the GPLv2 process was fairly closed. The GPLv3 draft process, however, was much more open and it’s clear that feedback was considered very seriously. You can even see demonstrable evidence of RMS making compromises in some places. That’s significant and credit should be given where credit is due.

I’m not a lawyer and haven’t had a change to even read the final GPLv3 from beginning to end, so I’m not going to comment on specifics at this time. I hope to set aside time for that in the near future. In the mean time, here are some of the links I’ll be using to base my research on. Please feel free to add quality links you’ve found in the comments. Thanks.

–jeremy

Massachusetts May Adopt OOXML – What Say You?

Andy continues his prodigious coverage of the Massachusetts OOXML/ODF debate. From a recent post:

The Massachusetts Information Technology Division (ITD), the state agency that effectively launched the voyage of ODF around the world in August of 2005, has released a new version of its Enterprise Technical Reference Model. And this new draft includes Microsoft’s OOXML formats as an acceptable “open format.” The new draft was posted today here, and the very brief comment period will end on July 20. The header to the announcement at the ITD Web site reads as follows:

A review draft of ETRM v. 4.0 is available for review and comment from July 2nd through July 20th, 2007. Comments should be submitted to standards@state.ma.us. This major release of the ETRM updates content published in version 3.6, introduces the new Management Domain, enhances the ETRM’s format for accessibility and usability as well as provides additions and updates to existing language and technical specifications. For a detailed outline of major revisions made in this version please consult the Major Revisions for ETRM v.4.0 document.

The announcement is not a surprise to me, as I’ve been following the progress of the ITD’s internal reviews over the past six months. I’ve not been commenting on this publicly in order to try to give Bethann Pepoli (once again the interim CTO, since the departure of Louis Gutierrez) and her team the space to do their internal evaluations with less pressure than Peter Quinn experienced the first time around. However, and as you can imagine, the ITD has been under as much pressure behind the scenes (and perhaps more) as the legislators of those states that have recently tried, and failed, to pass laws that would mandate open formats in government.

The OOXML-related changes to the text of the ETRM are deceptively insignificant. By my word search, there are only three references: the inclusion of the name of the standard in the introductory summary of changes, a brief description and migration section in the Domain: Information part of the draft (scroll down and look for the “Open Formats” section), and the listing of Ecma among the other standards bodies on a list of “Relevant Standards Organizations.” But the potential impact of these change if retained will be great.

How much pressure has the Massachusetts ITD been under to accept Ecma 376? I’ve been told by those in the know that the contacts reached all the way to Deval Patrick, our new governor. Here, as in the states where legislation was introduced, the point was forcefully and repeatedly made that Microsoft is the kind of company that can provide jobs and other economic support where and as it pleases. And, to be fair, the same points were been made in the past by representatives of IBM and Sun when they have spoke out in favor of ODF.

Now we are looking at a very short comment period, commenced with no advance warning, spanning a holiday, and contained within one of the busiest vacation months of the year (one can’t help wondering why).

That makes the comment period less than 14 business days in a month that, as Andy points out, is one that is very popular for vacationing. Assuming the addition of ECMA 376 moves forward, the question becomes how large of a blow is this to ODF? Opinions on that remain all over the map. Some seem to think it’s a minor setback while others say it could potentially relegate ODF to being a footnote in history. The fact remains that OOXML still only has a single implementation. It’s also unclear if the latest version of Office completely implements the spec or implements items not in the spec. This means that if ODF adoption doesn’t gain any traction, Microsoft will easily be able to move forward with proprietary extensions, let ECMA 376 languish or even drop support in the future altogether. In other words, we’ll be right back where we started. That’s a bad thing. Andy has further coverage on the topic, including reactions from around the industry.

–jeremy

Ubuntu on Two New Inspirons

In a move that would seem to back up initial indications that the Ubuntu Dell offerings were selling well, Dell has officially announced that it is adding two additional models to its Linux lineup:

From a Ubuntu perspective, we’re now offering Ubuntu 7.04 to customers in the United States on the Inspiron 1420N notebook and the Inspiron 530N desktop. Both are available for order now at http://www.dell.com/open. Since these are new systems, it usually takes us a bit of time to ramp production. Because of that, we expect to ship these new systems by the middle of next month.

Additionally, Dell has confirmed that it plans to extend the Ubuntu roll-out to countries outside the United States (currently the number one request on IdeaStorm). Dell also indicated that they are considering bringing Linux to their small business customers. Great to see that the Ubuntu offering is being well received. This move could very well be paving the way to both additional large scale OEM Linux plans and someday even a simple “Linux on any model” type roll-out by someone. Kudos Dell.

–jeremy

Red Hat CEO Says He Talked Patents with Microsoft II

A quick follow up on this post based on some questions/comments that I got via email. First, no – I absolutely don’t think Red Hat is currently in discussion with Microsoft to sign a Novell-style patent deal. Note the bolding. They may very well be in some kind of discussion, but that is not necessarily a bad thing. If Microsoft privately went to Red Hat with potential patent infringements, even silly unspecified ones, then Red Hat would be obligated to address the issue. That would require discussion. It’s very tough to be the CEO of a public company these days. “No comment” is very often the only answer you can give without the MSM twisting your words in all kinds of directions. Also note that Red Hat may be in talks about specific and valid patents or talks about something completely non-patent related. Who knows – speculation on this is mostly useless. I do remain confident though, that a Novell-esque deal will not come out of this. Don’t forget that RHT is fundamentally an Open Source company. It’s in their DNA and it’s reflected in their employees and culture. Novell had one or two key people leave after they signed the deal. Red Hat would have an exodus. The C-level execs at Red Hat know this. They get Open Source at a very fundamental level themselves, in fact. The following is the last official statement I could find from Red Hat on this topic. In the end, I have no reason to believe that sentiment has changed.

“Red Hat has only recently been able to see some of the terms of the original Microsoft/Novell deal, due to the belated and redacted SEC filings that were made. Based on what we have seen, the deal is not interesting to us. Red Hat continues to believe that open source and the innovation it represents should not be subject to an unsubstantiated tax that lacks transparency.”

–jeremy

Red Hat CEO Says He Talked Patents with Microsoft

It comes as absolutely no surprise that Microsoft approached Red Hat before any other Linux vendor (including Novell) about the patent agreement. It also comes as no surprise that a discussion took place and that no agreement was reached. Was is a bit of a surprise to me is:

The developer of Linux software, has yet to sign such a deal which could see Novell, its biggest rival, woo customers away from Red Hat and work on product development and sales with the world’s No.1 software maker.

In an interview with Reuters, Szulik declined to say whether his company is now in negotiations with Microsoft over signing such a patent agreement.

“I can’t answer the question,” he said.

When recently asked a similar question, Mark Shuttleworth gave an emphatic No:

For the record, let me state my position, and I think this is also roughly the position of Canonical and the Ubuntu Community Council though I haven’t caucused with the CC on this specifically.

We have declined to discuss any agreement with Microsoft under the threat of unspecified patent infringements.

Allegations of “infringement of unspecified patents” carry no weight whatsoever. We don’t think they have any legal merit, and they are no incentive for us to work with Microsoft on any of the wonderful things we could do together. A promise by Microsoft not to sue for infringement of unspecified patents has no value at all and is not worth paying for. It does not protect users from the real risk of a patent suit from a pure-IP-holder (Microsoft itself is regularly found to violate such patents and regularly settles such suits). People who pay protection money for that promise are likely living in a false sense of security.

Red Hat had also given a more deliberate “No” in the recent past, so the change of attitude to the “no comment” variety is a bit worrying. Here’s hoping that it’s just due to corporate disclosure rules (or something else innocuous) and not an actual change of opinion. Red Hat signing an “infringement of unspecified patents” type deal would be very bad IMHO.

–jeremy

Ari Jaaksi on Nokia and Open Source and the N770

Stephe points to a white paper on Ari’s blog that details the early learnings at Nokia around open source and product delivery. This learning predominately focuses on the Nokia N770 and maemo project. The N770 is an “Internet Tablet” and is the predecessor to the N800, which I’m the proud owner of. If you’re unfamiliar with the N800, you can get an LQ branded look here.

The 10 page white paper is full of useful information and insight and is a worthwhile read in its entirety. Here are a few highlights.

On cost savings:

The biggest cost savings came from the utilization of already available components. We utilized several free components and subsystems as such, with no modifications.

We also improved several components to better meet our requirements. Such improvement is cheaper than creating the needed functionality from scratch.

Some 2/3 of the code of the Nokia 770 is licensed under an open source license. These components made it possible for us to build the software cheaper than we could have done using closed and proprietary technologies.

On code quality:
If we compare the code from open source to the code developed by us, our conclusion is that open source is of better quality. We have more bugs and problems in the Nokia developed code. This is only natural because the majority of the Nokia code is build from scratch and is thus very young. Open source code, on the other hand, has mostly been used by others already. They have fixed the most severe errors already before we started to use the code.

On engineering flexibility:
Open source is flexible when we needed to fix a problem or change functionality. We often requested bug fixes or modifications to the commercial closed components on our platform. If the vendors didn’t have the capacity or will to fix the problem on time, we had few options. We could not fix problems ourselves because the companies using closed source didn’t want us to access their source code. With open source components, though, we fixed bugs yourself, hired somebody else to fix them, or worked with the communities for the modifications. We thus had many options available, and in most cases we managed to fix the problems at hand. The free access to the code and to the developers improved the quality of open source originated components within the final product.

On confidentiality and the open source community:
We worked intensively with communities already before we announced the Nokia 770 Internet Tablet. Open source approach requires openness and information sharing during development. A high publicity launch, on the other hand, is the way to introduce consumer products to the public and you do not want to reveal the products before the launch date. There is thus a potential conflict between the open source openness and product launch secrecy.

The credentials, work, and history of open source hackers are open for everybody to see. The hackers typically want to work with interesting things also in the future. Therefore, they don’t want to become famous for jeopardizing somebody else’s project and misusing their trust. Thus, openness and open source can actually be much stronger bond than any NDA or monetary sanction one can put on an individual or a company.

Based on our experiences, we can combine open communication and product confidentiality. We had no information leakage prior to the commercial product announcements, although we had had tens of developers working on the software with us. For some of the developers, we had told very detailed information about the forthcoming product. Developing products in open source and yet maintain the confidentiality of the product plans and roadmaps was possible for us.

and a summary:
Our experiences demonstrate that open source technologies and development model suit very well for such devices. We created the product in shorter time and with lesser resources that we have managed to develop other products utilizing proprietary software. In essence, open source offers time and cost savings in a form of readily available components and subsystems, available developers, and effective development model.

It was clear at the Linux Foundation Collaboration Summit that Linux in the mobile space is going to be huge. Even though Nokia has a serious investment in Symbian, they are exploring what the future holds for mobile Linux. That future looks very bright.

–jeremy

Top 500 Supercomputer OS Share

Top500 has released its latest Supercomputer list and Linux now represents over 75% of the top 500. That means 389 (or 77.80%) of the fastest (reported) supercomputers in the world run some Linux variant. That’s up from 65.20% in November of 2006. Windows made what I believe is its first appearance on the list, but according to this article that machine has been “rebooted as a Linux cluster”.

–jeremy

Google Desktop is now available for Linux

At the Linux Foundation Collaboration Summit, it was alluded to by a few Googlers that more Google Linux apps were coming “real soon now”. Making good on that quickly, Google just released the Google Desktop for Linux. While it is a native app, it’s not Open Source. It would be interesting to see a side-by-side comparison of this and Beagle (which I admit to not using). It’s good to see that, unlike in many cases, the Linux version looks to be an exact feature match with the Windows and OS X versions. At this point I think SketchUp and Notifier are the only two Google apps left without some kind of Linux version available.

–jeremy

Windows Vista – 6 Month Vulnerability Report

Jeff Jones, a Security Strategy Director in Microsoft’s Trustworthy Computing group, recently posted a 6 Month Vulnerability Report that compares Windows Vista, Windows XP, RHEL WS 4, Ubuntu 6.06 LTS, Novell SLED 10 and Apple OS X 10.4. Jeff has pointed out his potential bias, so I won’t even get into that angle. This report indeed does a better job than some from a methodology standpoint. For instance, he didn’t simply compare a default RHEL install, which includes a full Office suite and a whole host of apps not found in a default Windows install, with a default Windows install. He attempted to rip out the packages from the Linux installs that he perceived as being extra functionality when compared to a Windows install. This gives a much better baseline.

I’d like to simply offer a couple items that I think make reports like these a bit misleading. First, there is no standard definition of what a “Critical” or “High” security level is. It’s usually up to the vendor. It’s therefore possible that some vendors would rate nearly identical vulnerabilities with different severities. Second (and more importantly), we’re of course only looking at reported vulnerabilities here. Due to the Open Source nature of Linux, it’s much more likely that vulnerabilities will be discovered, reported and addressed. I’d contend that there are many more unreported vulnerabilities (which can be and in fact are still exploited) in proprietary software. If done again, another component I’d like to see added is average time to fix from time of first report. I’d be remiss if I didn’t point out that there are points that can easily be made for the flip side of the coin. The obvious one is that with a much larger install base, many more people will be targeting XP and Vista than other operating systems. In the end, statistics can almost always be made to say whatever you’d like.

–jeremy