On2 vs libvp62 (was: Re: [Ffmpeg-devel] When is planned to add ogg Theora output in ffmpeg?)
Sat Apr 15 22:26:37 CEST 2006
On Sat, Apr 15, 2006 at 11:09:37PM +0300, Oded Shimon wrote:
> On Sat, Apr 15, 2006 at 04:02:20PM -0400, Rich Felker wrote:
> > On Sat, Apr 15, 2006 at 10:25:39AM +0100, Dieter wrote:
> > > In message <20060415134828.GC1890 at biurrun.de>, Diego Biurrun writes:
> > > > And anyway, what is fairly complex to you? As seen above libvp62 is
> > > > around 3000 lines of code. Writing (and debugging) that much code can
> > > > take some time depending on your skill and experience, but we're not
> > > > talking about man-years here.
> > >
> > > The usual figure is 10 lines of code per day, so 3000 lines would be
> > > 300 person-days.
> > This is utter nonsense. My libc implementation is 26038 lines of code,
> > and I have not spent 2603.8 days on it. The project was started in
> > December and I've hardly worked every day/round the clock on it.
> > For something like VP62, leaving out the step of discovering how it
> > works and just assuming you already have specs, I would think 3000
> > lines of code would take at most a week or two for a competent coder.
my guess would be 2-4 weeks with specs and 2-3 times as much without
> To give an example of something slightly more relavent, my vorbis decoder
> from scratch is about 1500 lines, not counting breaks, I think it took me
> 2 weeks, MAYBE a month. Definitaly not half a year...
average developer employed by average company: 10 line / day
average free software developer who volunteerly works on something (s)he
cares about: 100 lines / day
In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is
More information about the ffmpeg-devel