[FFmpeg-devel] ffmpeg.org clean up

compn tempn
Tue Feb 17 02:11:15 CET 2009


On Tue, 17 Feb 2009 01:48:07 +0100, Diego Biurrun wrote:
>On Tue, Feb 17, 2009 at 12:55:17AM +0100, Michael Niedermayer wrote:
>> On Tue, Feb 17, 2009 at 12:32:35AM +0100, Michael Niedermayer wrote:
>> > On Mon, Feb 16, 2009 at 11:19:37PM +0100, Diego Biurrun wrote:
>> > > On Mon, Feb 16, 2009 at 10:37:04PM +0100, Michael Niedermayer wrote:
>> > > > On Mon, Feb 16, 2009 at 08:02:36PM +0100, Diego Biurrun wrote:
>> > > > > On Mon, Feb 16, 2009 at 10:37:57AM -0800, Mike Melanson wrote:
>> > > > > > Diego Biurrun wrote:
>> > > > > > > On Mon, Feb 16, 2009 at 10:16:38AM -0800, Mike Melanson wrote:
>> > > > > > >> Let me know of a plausible, cross-browser method to display 
>> > > > > > >> informational graphs (like performance vs. revision) in FATE using your 
>> > > > > > >> set of constraints. I'm still trying to solve that problem after a year.
>> > > > > > > 
>> > > > > > > Forget the cross-browser constraint.  Just make sure it follows the
>> > > > > > > relevant standards.  Browsers will eventually catch up, except maybe
>> > > > > > > IE, the use of which should be discouraged anyway.
>> > > > > > 
>> > > > > > So, adhere to standards that no one uses,
>> > > > > 
>> > > > > I beg your pardon?  The rendering engines of Firefox,  Safari and Opera
>> > > > > adhere closely to standards and even IE is catching up by leaps and
>> > > > > bounds.  This statement comes straight out of the 1990s...
>> > > > > 
>> > > > > > and that the biggest browser on the market does not care about?
>> > > > > 
>> > > > > In our "market" IE has a share of 23%, while Firefox has almost 50%.
>> > > > > 
>> > > > > http://natsuki.mplayerhq.hu/awstats/mplayerhq.hu/200812/awstats.mplayerhq.hu.browserdetail.html
>> > > > > 
>> > > > > Don't waste your time accomodating people that can fix their problems by
>> > > > > quickly downloading Firefox or upgrading their IE and make the world a
>> > > > > better place in the process.
>> > > > 
>> > > > > Back when I redesigned the MPlayer homepage I tried to make it work on
>> > > > > IE, but the pain was just too big and the code uglification too
>> > > > > enormous.
>> > > > 
>> > > > so even though the page doesnt work in IE correctly there still are 23%
>> > > > using IE?
>> > > 
>> > > Apparently.  Note that roughly half of them are using IE 7+, which
>> > > copes much better because it adheres more closely to web standards.
>> > > 
>> > 
>> > > And now let's define what "work" means here.  If you point your browser
>> > > to http://www.mplayerhq.hu/ you will notice the menu on the left.  Pass
>> > > your mouse pointer over it, you will see mouseover effects.  Entries get
>> > > highlighted, underlined or surrounded by a frame.
>> > 
>> > just tried
>> > menu is above the text and no effects with my mouse pointer over it, not
>> > that i expected any but the misplaced menu is serious incompetence on your
>> > side. And that is not a IE issue its a issue of the page being written so
>> > it will not display correctly on pre CSS browsers.
>> 
>> and note, the "incompetence" is not meant as an insult, its rather a
>> statement of the fact that if one has a webpage made primarely of text and a
>> menu and that doesnt display correctly for a quarter of ones users and even
>> for some members of the project. And one fully knowing that rather brags
>> about the philosophial advantages of it being broken for them, then i simply
>> cant pick a weaker word.
>
>MSVC accounts for much more than 25% of the installed compiler base.
>Does it compile FFmpeg?  No.  You are fully aware of this fact, yet you
>do not amend it?  Is it incompetence on your side?  Where is the
>difference?

i want this website/compiler bikeshed to be orange.

-compn




More information about the ffmpeg-devel mailing list