Re: Re: Arpi, if you are still reading the mcf-mplayer

Hi,

> > in c++... yeah :)
> 
> I was talking this afternoon about how fast Qt/KDE evolved to be the 
> major desktop system on Linux. And you know why ?
> * good coders
> * KDE relies on Qt to do most of the job
> * Qt is in C++ only and fully object oriented

lol :)
KDE... it's a real windows feeling
i've installed kde 3.0 on a celeron 300 with 256mb ram, and i got it always
crashing due to out-of-memory... the only app i ran was netscape.
after a week i dumped kde, and installed xfwm, now that is running fo rmore
than a month with zero crashes or slowdown problems, while has such fancy
menus etc like kde has. anyway i don't need them at all, i never enjoyed
those everything-translucent-iconized-antialiased-etc windowing managers, at
least i run X to run applications undre it, not for enjoying the graphics of
window titles...

> BTW, how many libraries does mplayer use ?
count it.

> Why do player developpers need to rewrite and AVI, MPEG, etc, demuxer 
> everytime they have to play a format ? Why not rely on THE (open) filter 
> of the architecture that the guy who created the format will do for you 
> ? Why recreate a whole data path (reinvent the wheel) when something 
> efficient exists ?
as nothing efficient does exists.
at least everyone implements it, and thinks that the other implementations
are unefficient or buggy.

> - It's not because you can control everything (you can also control 
> everything you need in DShow).

hmm, could you please fix the avi demuxer bug of dshow then? no? ah.
then we should keep workarounding it.


A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu