Thread: VLC Player Officially coming
View Single Post
allnameswereout's Avatar
allnameswereout is offline allnameswereout
2009-11-01 , 17:50
Posts: 3,397 | Thanked: 1,212 times | Joined on Jul 2008 @ Netherlands
#53
Originally Posted by daperl View Post
You were asking developers to be modular because of limited resources
I stated several reasons with that being one of them, yes.

but you argue that it's not reasonable for manufacturers to do the same. I consider that a contradiction, and your reasons seem to be just rationalizations.
Yeah, and for reasons I stated your compare is invalid because you compare software with embedded hardware. It is only a contradiction if you refuse to take the different situation into account.

This comment has more to do with planned obsolescence and less to do with modularity. More to my point about contradiction. With your reasoning, wouldn't it be more in a software developer's interest to share fewer libraries with other software?
No, because features are going to be shared with other applications. Other applications need C library, or want to change volume, or want to have EQ, or want to decode MP3, or want to use X11, or want to show a PNG.

They could then force the user, because of limited resources, to have fewer choices, which appears to be your agenda anyway.
My agenda is to have one good, default touch UI multimedia player with legal codecs, using the backends which already exist on our desktop (which means that we for example use GStreamer and not Phonon). Alternative for such interface is installable, but uses same frameworks, hence only difference is UI. Example is interface for stylus, or Ncurses. There are no other multimedia players because there is no demand for them, because everything is already modularized yielding no differences. Hence only a few exist, each with different UI. Its the very essence of open standards and modularity.

I think I'm gonna fork gstreamer to daperlstreamer...
Won't bother me as I won't see it cluttering my system, just like 4000 Linux forks from GIT are not bothering me. But if they were there when I'd search for Linux kernel in my APT repository it'd bother me.

And I really don't want to go back to 90s having QuickTime, Windows Media Player, RealPlayer, and such installed so I can play some stupi format only supported by these players... so we provide our codecs via multimedia framework to whatever application supports our API. That there is a different multimedia framework for KDE than for GNOME is not a huge problem.
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
Last edited by allnameswereout; 2009-11-01 at 17:56.
 

The Following User Says Thank You to allnameswereout For This Useful Post: