Alistair MacDonald wrote:
Jules Richardson wrote:
Cini, Richard wrote:
> I'm thinking of ditching Windows totally on my desktop at
> home
> as I build my next upgraded x86-bsed PC. So, I wanted to take a poll
> of the
> group for a recommendation on which Linux distro to use. I downloaded
> Fedora
> Core, Slackware, FreeBSD, Unbuntu and Linspire.
I've gone MCC, SLS, Slackware, SuSE, Debian over the years.
Actually, I forgot to mention that I've quite often had people recommend I try
Debian over Slackware before. You still get the problem of the Gnome / KDE
choice though, I suppose.
My personal experience with RedHat has been bad. But
that is just my
personal experience. I could never get it to do what I wanted. I had to
let it do what it wanted.
Yes, exactly the same here. It's not very often I hear from people who say
they liked it (or Fedora).
2) [...]
I'm currently struggling to find any half-decent OCR tool too.
I've given up on that.
I'm currently hacking front-end code in order to try and improve the
performance of the OCR engine itself. It's giving me a headache!
3) Systems
still suffer from rot, just like Windows does. After a
Debian has 'deborphan' which can identify those packages which are no
longer referenced by other installed packages. You can also force the
removal of packages if you are certain that you don't need them. I
suspect that most of the distributions do. The trick is working out the
appropriate incantation.
Yes, Slackware has various equivalents (run a 'man -k pkg' for a list).
Problem is, the concept of a 'package' is fairly high-level. Say you want to
be able to play x format of audio on your system. You might find there's a
multimedia library package that enables you to do this - except that what you
actually get is a bundle of umpteen billion library files which can play every
format ever devised, 99% of which you don't ever need, and which sit there on
the system doing nothing. If you go around deleting them manually, you screw
up the package system that's been layered onto the OS as an afterthought.
I just wish the concept of a package was more of a file-level thing, so that
you end of with a system just comprising the bits you really need and use -
coupled with some sort of common mechanism which can tell you when you're
trying to do something from a front-end script / GUI app for which you're
missing required modules / libraries / other apps of course. Possibly have the
ability for the system to automatically go fetch the needed bits from the 'net
too.
I seem to recall that Perl has something akin to this, and that in the Windows
world their media player can do it too - but having it built in system wide
with a common set of APIs to manage it would be nice.
cheers
J.