Saturday, January 31, 2009

Regarding ease-of-use (number three on my list), a major problem with Linux is installing third-party applications. Programs which are in the repositories of your distro are very easy to install, in my opinion easier than on Windows. Downloading a separate package file (a .deb or .rpm for example) for your distro is also very easy (this however assumes some technical knowledge: the version number of the distro you're using).

But then there is the case where there is no package available for your distro. Maybe there is a package available for some other distro, which could be converted with alien. However, this is cumbersome, slow, and will sometimes even not install the application correctly.

The worst case is however when none of that is available, and just a third-party installer, or source files you have to compile yourself. Last year, I installed the commercial statistical package SPSS on my Ubuntu 7.10. It didn't work. First after a few months, when Hardy came out, it actually did work.

The compile-it-yourself way is however an option that none of non-technical users can ever do. Clearly, a lot could be improved when it comes to supporting third-party applications.
I hope that the LSB can standardize Linux sufficiently for compatibility across distros. But the program installation process itself needs to be improved a lot. The Burgdorf API (also known as LSB Packaging API) seems very promising. Small open-source projects which don't get enough attention to get native packages in all major distros could quite easily (supposed the right tools are developed) make their own install file.

When I wanted to install NES emulator, the ones found in the Ubuntu repositories didn't have all the features I wanted, so I ended upp downloading and compiling Nestopia. If the Burgdorf API had been in widespread use, they could have made an install file using that, which would have been much simpler for me.

The same would have held true for installing the commercial SPSS program. Had standardization been thorougly implemented, it would have worked on the first try to install it.

So, let's just hope that development of the Burgdorf API proceeds well, and that all distributions will adopt it! Then I think there would just be a matter of time before almost every program will be easy to install on Linux, removing one more of the obstacles for a really user-friendly Linux.
In response to comment on my previous post, let me define what mean with 'The year of the Linux desktop'. I would be something like: Linux is quite widespread on the home desktop market. Apple has around 6-7 %, something like that would suffice. My prediction is that this will take maybe four years (meaing sometimes in 2013). That would mean that Linux would be so easy and useable that (compared to for example Windows XP) a normal, non-technical user can use it with spending a similar amount of time on configuration and system management issues, it would need a similar level of knowledge (note that this can be entirely different *kind* of knowledge than other OS:es, but total computer illitterate user could learn them in a similar amount of time), and that most normal tasks could be done with a similar level of functionality, hassle and ease-of-use.

Currently, this is not the case for the majority of non-technical user.

Wednesday, January 21, 2009

What are the biggest problems with desktop Linux?

A lot of people has been talking about 'The Year of the Linux Desktop', and that this year it will come. But the years has passed, and the The Year of the Linux Desktop never seems to come. Why is that? What are the main problems with Linux that holds it back from becoming a success?

In my experience, the main problems are the following:
1. Hardware support
2. Multimedia support
3. Ease-of-use / Useability
4. Support for running Windows programs (WINE)

Other people may have a different list, or a different priority of the items in the list. This is just according to me. I will post about these items for some time, describe the problems, give an analysis of why the situation is as it is, and give some suggestions for solutions.

Monday, December 22, 2008

Introduction

As the title suggests, I'm going to write about Linux in this blog. Probably I'll write about some other things also, but I plan on starting some other blog for writing about those things (such as leadership, theology, personal matters and so on). But I'm not even certain I'll open such blogs. If I do, they will probably be in swedish anyways. I have not decided the regularity, or how long I'll be doing it, but let's see about that. This is mostly for myself wanting to write about things I've been going and thinking about, it is not otherwise from a certain perspective or something.

Now I'm 26 years old, and started using computers when I was maybe 10 or something. I've for a long time been somewhat of a computer geek, first sitting and hacking with DOS and windows 3.1, and a couple of years later I tried Linux. I've been using Linux regularly for at least the last twelve years, and as my main OS since 2001 (or was it earlier? I don't really remember, but at least in 2002 I had no other OS installed on the computer. I remember sitting a long quite a long time with DOS and Borland Turbo Pascal, but at some point I switched to C++ development, and suppose I kicked out DOS completely at that point.)

Firstly I used Slackware, which I think was a good OS. After a few years I switched to Debian, which I felt was a big improvement, easier to use, more packages, easier to upgrade, more autoconfiguration and so on. It was also easier to customize, in the way that you could add your own customizations while the system still had the control of over everything else. One example is the init scripts, which in Slackware is BSD-style, and in Debian SysV-style. With sysv-style, you can easily add your own init-scripts, while the OS still manages all the other scripts and updates them when packages are updated. After a few years on Debian I switched to Ubuntu in 2005, which I also felt was a quite big improvement. Not as big as the Slackware -> Debian, but anyways better. It was the old familiar Debian system at the bottom, while being easier to use and adding some other niceties. Ubuntu has it's bugs though (but Debian testing which I used, also had theirs), but overall it is a decent OS. And after the Hardy Heron has had some time to stabilize, it is (at least for me) a quite stable system.

Nowadays I'm not so geaky anymore, and am slipping away from the 'computer as a hobby' - usage pattern. Now I more want things to just work, and don't like so much spending time on configuration and kernel compiles and the likes. But I still has all the knowledge from all my computer experience, so I hope that writing from this perspective could provide some insights not found so much elsewhere. Of course my knowledge is very limited compared to the real pros out there, but compared to the average Linux user who just wants to use the computer, I think I am quite more computer-proficient. I have alse studied two years of computer science, which should give me some knowledge.

This is my first post, and I think this would be enough for this time. I'll come back with some more substantial posts later on, such as what the biggest weaknesses of Linux is, and some ideas on how those could be remedied.