Since other people can do Part II’s of remarkable things and thanks to Mary for explaining a bunch of things I am interested in, I can do a part deux about what I see being some of the points and profiles of Linux on the desktop. This expands on some ideas in my first blog post.
Linux on the Desktop - a Myth or Magic or its Real
Asa Dotzler awhile ago posted his extrapolations on what makes Linux ready or not so ready for desktop use. Its an interesting read and the comments frame what people consider the strengths and weaknesses of same. In his recent Part 4 he covers some interesting terrain as well. I believe that the whole corrolary becomes more complex when one introduces variability to the constants. Lets just say the question changes from “is Linux ready for the desktop” to “Is Linux ready for a POS Enterprise Desktop”. Then we get brand new methods of measurement and we need to apply other standards. We simply cannot use the same use cases for a personal productivity desktop versus a very focused and defined desktop that may only have one component. As Asa points out,
How does Linux improve here? The challenge is to find those areas where it’s valuable to change and make the transition as easy as possible (through good documentation, intuitive or easily learned UI, etc.) and to find those areas where change doesn’t offer enough benefit and make those areas as comfortable as possible. It is not necessary to be a clone, but it’s foolish to deviate from what Regular People expect when the value of that deviation isn’t extremely high.
My answer is that Linux must improve on a series of paths instead of just one. There are different success ratios for each type of use we define and to make Linux work in each one there are different sets of success and failure criteria. I don’t know how many there are of these but I suspect that we each can define a few when we think of how Linux could potentially be used in corporate or enterprise or home systems. It becomes a “habilis” question or a tool user type thing. We need to retain flexibility as we seek out where it could and will work versus where it needs to get better and not where it needs to emulate Windows. People don’t want/need another windows clone. The diea is make something sufficiently different and by that difference people are attracted. Asa uses the term “Regular People” above; but I maintain there are no regular people in this game. Everyone has sets of requirements or tools or productivity requirements that Linux may or may not fulfill. A project manager may find that the desktop does not provide sets of applications to open visio or MS Project diagrams easily. Is this the desktop or a focused application? And where the two interact and integrate. The question must be posed where the destkop ends and the applications begins.
If we only ask for the so-called “Regular People” then we get “Regular Answers”. But those, I maintain, are not the answers that really count since everyone uses their systems in non-regular ways and have their own unique habilis requirements. I like Asa’s analysis but I think when we simplify things we don’t reach the core issues.




