Linked by Eugenia Loli on Sat 17th Mar 2007 00:26 UTC
Ubuntu, Kubuntu, Xubuntu During my 8 years of Linux on and off usage I have tried more distros than I have chocolate bars. Each one of my previous encounters meant that I had to spend at least 2 days configuring before I have a desktop that I was somewhat comfortable with. With Ubuntu Feisty Fawn's latest test beta --for the first time ever-- this was not the case. I was up and running with all the niceties I wanted within 2 hours.
Permalink for comment 222312
To read all comments associated with this story, please click here.
Doc Pain
Member since:

"Until Ubuntu decides to support KDE properly, I won't use it, nor will I recommend it. "

I think it's possible to install KDE afterwards and switch to it then. Can someone confirm?

"In fact, these days I don't use GNU/Linux at all, since several things I use aren't supported:

1. Photoshop CS2 (WINE/Cedega/CrossOver Office do not support it, not even with nasty hacks)
2. Neat Image (full of bugs under WINE, haven't tried Cedega/CrossOver office)
3. Capture One Pro (WINE says v3.6, although it has bugs, not sure on v3.7)"

As it has mentioned before, just write a letter to the vendors of these software products. Tell them you paid some money to them, but their programs do not work in Linux properly.

To get serious again: Software support is not a lack of Linux or Wine. It's the fault of the software vendors. For Linux, specifications, APIs and frameworks are well documented, the libraries and the compilers are free (due to the GPL), so why do they refuse to use them in order to make a great product working on Linux?

BTW, I'm a photographic enthusiast myself and I never found any reason to use one of the products you mentioned. There are very capable alternatives available, just try them and see how you can work with them. Remember, even the Gimp's interface has improved and is ready for Joe Q. Sixpack.

"4. Canon EOS 1D DSLR - gphoto2 doesn't support this *major* pro camera whatsoever. Disappointing."

I agree, that's a real problem. But it's Canon's problem. There are standard specifications that Canon could have used, but they simply didn't, because they don't care. So, if your EOS had a standard USB mass storage system, a /dev/da?s1 file would be available to be mounted via the -t msdos command. No problem! There are other free standards that could have been used. But if Canon decides to be proprietary, I won't buy this product.

A simple workaround could be to eject the storage media from the camera and put it into a drive (internal or attached via USB). So access to the files would be possible.

I for myself own a Canon EOS-50 (without D) because digital SLR's quality is not worth the money at the moment. Letting a photo CD being made is possible as well, and is enough for my needs at the moment.

"Asking me to get off my a$$ and code drivers for this baby is what I consider elitist and a very unreasonable demand on the end user."

Inform developers that are able to. How does someone who you would call "elitist" to write a driver for your camera? He even would not use it, so why should he do such work?

It would be better to inform Canon itself that you want to use their great camera with Linux, but you can't because they don't support it. So you won't buy or recommend their products...

The easiest alternative: Hardware vendors and software vendors, use existing standards or publish new ones to the public!

"It's one thing that gives GNU/Linux zealots a very bad name in the real world."

Per definition, zealots have a bad name, if they defend Linux or MICROS~1 or whatever. I won't worry. Nobody cares about them.

Reply Parent Score: 2