Google Follows Through

Following up on a topic I've talked about before, Google has released Picasa for Linux. As speculated though, it's not a native port, but a Wine rollup. It's great to see Google follow up on the promise they made to support Linux apps, but it is a bit unfortunate they went the Wine route IMHO. There are a lot of downsides. First, it *looks* a bit out of place after you run it, ie it looks like a Windows app stuck in Linux and has absolutely no Window Manager integration. The package includes a bundled version of Wine, so is a hefty 25M. If other companies follow, will we now need to have 30 different wine installs (since this does not use a standard win install, even if you have one). I'm hoping this isn't a dangerous precedent where Linux support equals Wine. Now, unlike some, I'm not a Wine basher and think it is a useful piece of software, but if Linux support starts to equal “runs in Wine” we will forever be intrinsically tied to Windows and that's a very bad thing. I'm hoping it's only used as a sort of temporary migration platform while they gauge demand and get more comfortable with Linux as an end user platform, but that remains to be seen. All in all though, kudos to Google for staying true to what they said and also for potentially furthering the exposure Linux gets. One truly great thing here is that Google contributed over 200 patches back to Wine, so even if you never touch Picasa it's very possible you may benefit from this. More info is available here and here.
FWIW I did download and install this and it does run very nicely for a Wine app. Google makes 3 downloads available – RPM, DEB and a Loki-based installer. They even contributed some patches back to Loki. It should be interesting to see if they continue this three release paradigm as they support more of their applications on the Linux desktop. This is certainly a sticking point area for Linux and how Google handles it could set a precedent for many.
–jeremy
, , , ,

Mac OS X Kernel Source Now Closed

That (or something close to it) is the title of many articles that seems to be circulating. The odd part is, OS X was *never* Open Source code in the first place. Nor did Apple pitch it as such. Carbon, Quartz, Cocoa – you name it, no code. Does sound like a good headline though, doesn't it? What the articles are actually referring to is that Apple is no longer releasing the code for XNU, the OS X kernel, for the x86 platform. I don't follow Darwin too closely, but it seems to have been dead for some time now. The reality is that Apple just isn't an Open Source company. They claim to support OSS in their marketing, and do in fact release a fair amount of code, but it's just not their bread and butter…nor is it really their culture. They were, however, able to leverage OSS to make a nice platform.
Much of the speculation going around centers around why Apple chose to do this now. One of the most popular theories is that it's to prevent piracy. I'd hope they have a better reason then that, because it's clear that making something closed source in no way prevents piracy. Other theories abound though. Could it be because of an embarrassing disparity between the PPC and x86 trees? Or does it go deeper than that. Is Apple working on a non-MACH version of the kernel and trying to slowly work some items in without people knowing? Are they working on implementing the full Windows API to enable you to run Windows apps right in OS X? With the next release of OS X coming up fairly soon, I'd guess we'll know more soon. In the meantime, if this is a subject that interests you, I suggest reading these two extremely informative articles.
–jeremy
, , ,

Microsoft considers taking admin rights from employees

From the ZDnet article: As Microsoft moves its internal desktop systems to Windows Vista, the company is contemplating whether to change a long running tradition and take away admin rights from its employees in order to improve security.
This explain quite a bit I think. While some job functions absolutely need admin privileges, every employee at a company as large as Microsoft is a bit much. I think, though, it shows the mentality of the company when it comes to security. That mentality comes though in the end product, which has been historically ridden with security issues. This may also explain why so many applications that quite simply should not require admin privileges do – if Microsoft runs everyone as admin, that's the example that's being set. I've seen many companies give up and give people admin for the sole reason that it's the only way they can get things to work. Enter a decade of viruses, malware and fun. Good to see this mentality may finally be changing, although it's a bit late. Maybe in 5-10 years most Windows software will understand the proper security paradigm and the security issues will calm down. The Vista successor should be out by then ;)
–jeremy
, , , , ,

Red Hat Not Satisfied with Sun's New Java License

This seems like an odd move by Red Hat. Now, I know they don't necessarily get along with Sun, but calling them out on the Distro License after Sun has announced its intention to Open Source Java and giving incompatibility with OLPC as the main reason?? Come on guys, you're better than that. I can only hope the article is a poor summation by the journalist, which is certainly possible these days. While OLPC is an amiable goal (one I should discuss on this blog, and will at some point), it's not a reason for any company to base this kind of decision on. Looking at the OLPC specs, the Sun implementation wouldn't even run in a usable manner anyway. Additionally, Red Hat contributes to classpath and could include that implementation. The one valid reason given in the article is that Red Hat would like to make some specific improvement to Java, centering around real-time capabilities, and I'd guess we'll see a 64-bit Java plugin available soon after it's officially Open Sourced. It will be interesting to see what Red Hat's reaction to the Open Sourcing of Java is if/when it's not GPL compatible. It constantly seems like the biggest proponents of Open Source Java are direct Sun competitors, which along with what Microsoft tried to pull is probably why Sun has been so skiddish on the issue. It should also be noted that, from what I can tell Debian does not approve of the license. If we reach a point that Debian approves of a license that Red Hat doesn't, we're probably in trouble :)
–jeremy
, , , ,

Novell Partner Linux Driver Process

Novell recently did a press release entitled “Novell Delivers Device Driver Breakthrough to Accelerate Linux Adoption. With device drivers being a sometimes maligned aspect of Linux, I was interested in exactly what Novell was going to do. After reading the press release, I really had no idea. After poking around the Novell site a little, I have a slightly better idea, *I think*, but there's still not a lot of technical detail available (or I am missing it). It appears that if you join the program and develop your driver in accordance to the Suse Kernel Module Packagers Manual, then your driver will be available via YaST and you'll also be notified in advance if an ABI change will break your driver. If the driver is certified, you can also get some level of support for it from Novell. At a certain level of certification, you can even ensure that your driver is available at the same time a kernel security update is released. Once nice thing here, is that Novell appears to be making an attempt to encourage development to take place in the mainline kernel, while allowing this as a way to obtain a driver either 1) before the driver is accepted upstream or 2) without having to upgrade your kernel. Both of those are nice, but hardly a “Breakthrough”, so I think I must be missing some other aspect. I'll have to keep reading. Once thing I don't really see mentioned is binary drivers. Will they be allowed as part of the process? If so, will a binary driver be allowed to certify somehow (say a Novell NDA)? I'm also waiting to see if Greg K-H comments on this, so I can see the nonmarketing side of things.
–jeremy
, , , , ,

Sun promises to open source Java

In a session at the JavaOne conference, it looks like the new Sun CEO has promised to Open Source Java.
“It's not a question of whether we'll open source Java, the question is how, ” Schwartz told delegates in his opening keynote at the tradeshow.
Interestingly, it hasn't created as much buzz as I'd have thought. The one thing I keep seeing that's incorrect is that the source to Java isn't currently available. It is and has been for a long time now, it just isn't available under an Open Source license. It will be interesting to see how this progresses. No timeline has been given and Sun certainly still seems a little apprehensive. There are a lot of other questions here also. What will the current Open Source implementations do? How much of this was was caused by C# uptake. How will Microsoft and IBM react? I'd guess the answer to most of those questions will depend on how the Open Sourcing objective plays out. No license has been officially announced, but one has to think that the CDDL is a likely candidate. No matter which license it is, it almost certainly won't be GPL-compatible. Also, Sun seem very concerned with forking. With the right to fork being one of the main Open Source ideals, they'll have to be careful how they go about trying to prevent forks. It will probably be a trademark enforcement, but if they try to work something into the actual license, it could get messy. On the Linux side, you have to wonder if this is going to get more distros to ship with Java preinstalled. I'd guess it once again will likely depend how Sun proceeds. So now I see why the issue may not be sparking the buzz I had expected. While it's great that Sun is continuing their commitment to Open Source, with so many aspects of this still up in the air, many people may just be taking a wait and see approach.
–jeremy
, , , , ,

Can the ordinary computer user ditch Windows for Linux?

That's the questions Mark Golden recently asked in the Wall Street Journal. His conclusion?
For me, though, using the Linux systems didn't make sense. I often send documents and spreadsheets between my home PC and the one at work, which uses Microsoft Office. And the files are sometimes complex. Meanwhile, for both personal and professional computer use, I want access to all multimedia functions.
While solutions may exist to almost every problem I encountered, I was willing to invest only a limited amount of time as a system administrator. Claims by some Linux publishers that anybody can easily switch to Linux from Windows seem totally oversold.

Despite a few minor errors (Linux was really written as a Minix replacement, I'd hardly call Usenet in 1993 a “Web bulletin board”, Linus really is not in charge of maintaining central Linux standards) I think Mark gives Linux a fair assessment (although I think he would have faired slightly better with newer distribution versions). Linux isn't ready for the desktop. But, things really are changing. During the first round of Linux on the desktop talk about 4-5 years ago, Linux wasn't ready for technical reasons. To a large degree, that has changed. It's not ready now mostly due to legal encumbrances, software patents and other non-technical stumbling blocks. For many reasons though, I think these will be much harder to overcome than the technical obstacles were. You see – the Linux community is filled with some really smart people that excel at overcoming tough technical issues. We were bound to fix the technical issues. The Linux community however is not necessarily filled with people interested in marketing and it's especially not filled with people who are willing to concede freedom in the name of marketing. Look at the drubbing Linspire took when they released what from one angle can be seen as a legitimate attempt to fix the problems Mark had.
As you know, I've covered this topic a lot recently. I'm coming to see this situation as sort of the Ying and the Yang or the fire and the water. On one side we have the people who will fight for freedom, do what's right and solve the technical issues. On the other side we have the people that are interested in making things easy and catering to the masses. The intersection is that they both want to help Linux adoption (albeit for much different reasons). I'm slowly coming to an understanding that both groups need each other more than they may think at first. You see, the first group – they want open specs, open solutions and Open Source. But, with the current marketshare, it's not hard to understand why some companies aren't listening. Very few companies are interested in doing the “right thing”. They are interested in maximizing profits. So in come the people who are attempting to market Linux to the so called unwashed masses (ie. the ones who don't see there computer as a tool or something to tinker with, but merely as a way to check email). So, the question becomes can both sides meet at the intersecting point and agree to work to the same end via different means? Can we work towards to end goal of group 1 (which I think in the right one, personally) via group 2 gaining marketshare and mindshare in the main stream while avoiding the binary doomsday scenario? I'm still thinking about that one, but I'm interested in what others have to say.
So, does the fire need water?
–jeremy
, , , ,

Freespire and the Proprietary Software Debate

At the recent Desktop Linux Summit, Kevin Carmony announced the release of Freespire. From the site:
Freespire is a community-driven, Linux-based operating system that combines the best that free, open source software has to offer (community driven, freely distributed, open source code, etc.), but also provides users the choice of including proprietary codecs, drivers and applications as they see fit. With Freespire, the choice is yours as to what software is installed on your computer, with no limitations or restrictions placed on that choice.
I think everyone knew this was Open Source dynamite waiting to happen and Kevin admitted that Linspire had been planning this for years, but didn't think the Linux community was ready until now. Reaction to the announcement was what you'd expect and included this vitriol response from Groklaw. A response from Kevin is available on LXer. This of course is a topic that I've discussed here ad nauseum. Kevin does make one good point. 10 years has really made little difference when it comes to vendor support. Now, in that 10 years Linux has improved so much that it's hard to believe, but US hardware manufacturers haven't really come around. Either have many of the software vendors. Photoshop, current versions of flash, Dreamweaver, Quicken – none of them available for Linux and no announcement that it will become so. Does that mean we should give up the fight? Hell no, but a different approach might not hurt. It's hard for a group the represents 1% of the market to demand something, whether we're right or not. Does Open Source produce better software? Undeniably, yes. Should we all value our freedom? Absolutely! the thing is, the majority of the computer users don't care about “better” software nor freedom in the context of software. Yeah – it is sad, but it's reality. Education is part of the key here of course, but so is getting people to try Linux. Right now, too many people just don't care. Us insisting that religion be part of the package certainly isn't going to change that. Now sure, I'll keep trying to educate. I'd like to think I've enabled more people to drop non-free software than most. Someone focusing on the other parts may not hurt though. The problem is, it's a slippery slope. “A Doomsday scenario” by Arjan van de Ven could legitimately become a reality. So could Linux never gaining any discernable market share on the desktop. I'm starting to think that may not be so bad. The server poses many less problems on this front (no MP3, no 3D cards, no DVD, etc.) and those of us who want to run Linux on the desktop because of the libre reasons I suspect have been for a long long time. I doubt companies will see it that way (there's just too much money involved), and someone giving Microsoft real competition is just too compelling for the rest of us to ignore. Something has to give though, and at this point it looks like it's going to give soon. Something tells me it might be ugly.
–jeremy
, , , ,

Will Sun Open-Source Java?

An age old question, will Sun Open Source Java? With a new CEO in Jonathan Scwhartz and the JavaOne Conference around the corner, the topic is getting quite a bit of attention at the moment. Keep in mind though, to Sun, “Open Sourcing” Java would almost certainly mean CDDL and not GPL. With Scwhartz being on of the proponents of Open Sourcing Solaris, the chances for Java are probably greater than before, but there are still clearly some major debates going on within the company. Will the move benefit SUNW and the stockholders? With rumors of up to 30% layoffs, does the new CEO have more pressing issues on his plate? At a company the size of Sun, 10% of the workers are probably superfluous…but losing 30% would be devastating. He's not in an enviable position, that's for sure.
Back to Java for a moment, one of the major gripes has always been the redistribution verbiage. Open Source or not, that really has to change. One of the common cons I see for potentially Open Sourcing Java is that it will surely cause forks and confusion. There are already a bunch of forks around, and I don't see a lot of confusion there. So, will Sun reverse its long time thinking on the topic and go Open? If they do, will companies like IBM (who has a massive middleware investment in the language) jump in and participate with Sun?
In the bigger picture, will Jonathan be able to turn around a company that contributes a lot to both Open Source and the computing world in general (NFS, much of XML, Java and more) but hasn't turned an annual profit in 5 years? No easy task. As usual, there is some irony here. For some of the major misjudgments Scott made in the past (network computing as the major example) he seems to have been pushed out now by wall street for the products not scaling vertically at a time when most people are scaling horizontally (that is, most companies are not buying huge high end machines, but scaling out with many cheaper ones). The lower end Sun product offering is actually looking very good right now. Odd.
–jeremy
, , ,

The Microsoft Malaise

In his usual style Dvorak mixes rational thought with wild speculation to get readers attention. But let's look into the topic, as it's an interesting one. Microsoft is clearly finding it difficult to compete. As mentioned, that will not stop them from making piles of cash for the foreseeable future, but in this industry it's possible for the giants to fall remarkably fast. So what is Microsoft doing right now. It looks pretty clear that Vista is going to be a large disappointment. It will gain some traction on new PC's, but I don't see any kind of immediate must have upgrade potential in the enterprise. The product is so late and the feature list so cut, that if Microsoft didn't have the market share they do, this would have been absolutely disastrous. Second, at a time when OOo is finally coming into its own, Office decides to completely redo the UI from the ground up and release seven versions. This is a bold move to take with one of their two cash cows and with ODF an ISO standard now, this will be fascinating to watch play out. So, with the writing on the wall, Microsoft has started to diversify. The problem is, they are going in too many directions at once, and not doing any of them outstanding. The Xbox360 is nice, but they failed to gauge demand and way under produced, which in the console industry is a killer (just ask Nintendo). MSN has failed to gain any ground in the search space as has most of of the online attempts Microsoft has made. I think all these from Vista to MSN share a common thread though. Microsoft has lost touch with their users. They're concentrating on everything except what their users want. That's a dangerous thing to do.
This brings us to one of the points I partially disagree with in the article. John says Microsoft is preoccupied with Google, who is not even a competitor. That's shortsighted. Google is a competitor. They are slowly proving that the web can be the OS, at least for a large portion of users. Nothing could be more detrimental to the Microsoft bottom line. The partial part comes in because I do think their complete preoccupation has become a problem. It seems every app Google comes out with, Microsoft throws a me-too copy out sometime later. They're losing focus. The irony here is that one of the only innovations to come out of Microsoft in some time, XMLHttpRequest, is the base of AJAX which may plant the seed that finally displaces them. What an odd type of justice that would be.
–jeremy
, , , ,