> so it's your chosen package, but without > even taking a look at mythtv you trump it > as more mature?
IIRC MythTV got DVB support a little over a year ago, about the time I got my first DVB card. Support for full featured cards (cards with decoder) may have come even later.
vdr on the other hand has had DVB support for about 4 years.
So a year ago MythTV was very bleeding edge (at least regarding DVB support), whereas vdr just worked, and had been working for several years.
> (vdr doesn't have plugins for 'all those > buzzwords' as you put mpeg4 encoding to be)
The vdrrip plugin which I use uses mencoder. So it's a breeze to mpeg4 encode recordings.
> looking at the features, mythtv looks like it > does more, a LOT more.
> including stuff like picture in picture, multi > card support - and get this, transparent multi > machine support: "Distributed architecture > allowing multiple recording machines and > multiple playback machines on the same > network, completely transparent to the > user.", rss, mpeg4, mpeg2 > decoders/encoders and a whole lot of other > stuff.
Uhm, there are vdr plugins for all those buzzwords (except for "rss" maybe, but I don't know what that means in this context). (Multicard support is of course supported by default).
It's been a while since I've looked at mythtv, but vdr is much much more mature.
Thanks to vdradmin I seldom watch TV realtime anymore, and I almost never program vdr to record individual programs, I just feed vdradmin patterns or regexps!
Regarding item 2, I had a colleague at a University I worked at, which had a "proof" (I didn't look into it and it wasn't published but rather a good discussion and it was a bright guy) that a garbage collector was faster, in theory, in certain situations.
In a copying garbage collector, the work required is proportional to the live memory. With manual memory management, the work is proportional to the amount of garbage. So given enough memory, garbage collection will always be faster, "even if the cost of freeing a cell is only a single machine instruction" (Appel). Garbage Collection Can Be Faster Than Stack Allocation by said Appel is a good start if you want to know more.
The key phrase here is "given enough memory". And in my experience, I've never succeeded in giving real Java programs enough memory:->.
> Actually he's of Swedish descent but his family lives in Finland.
Close but no cigarr. He is a swedish speaking Finn. Finland is a bilingual country.
Re:Does anyone else get the feeling
on
Opencroquet
·
· Score: 1
> Like smalltalk. Early 70s, IIRC. The problem of > managing increasing software complexity, which > object orientation (partly) solved, became > significant only much later.
I know this is the common perception (i.e., that object orientation solves software complexity), but have you ever seen some scientific data backing this up? I have seen one or two very small scale investigations of this that can be taken seriously, but that's all.
The problem is of course that it's very expensive to compare programming paradigms. You need several large developments teams (at least one doing OO, one using something else) developing the same application, and you need to investigate more than one application. And you need to make sure the programmers are at the same level of skill, etc.
Anyway, if anyone has some referneces to scientific studies actually showing OO reduces software complexity, I would be interested seeing them.
(Note: I'm not claiming OO doesn't reduce complexity, I would just like to see more than handwaving proof of this).
I'm also a fan, and I have to agree. Somewhere along the line it started reminding me of the kind of tv-series which where great in the beginning but just continues season after season until you can't remember why you watch it anymore (e.g., X-Files).
I haven't actually finnished Winter's heart yet. I bought it a few days before the official release date, but as you say, it's slow. And I'm having a lot of troubles remembering what has happend (or even caring:\).
But the beginning of the series is absolutely superb.
Making money on free software might be possible in theory, but in real life it's not that easy. I seem to get contacted by one or two companies every month nowadays with job offerings as a programmer (programming ordinary commercial closed source software). I don't know of any company I could apply for a job where I could be doing free source development.
For every job where you get paid to write free software there are several order of magnitudes many more "commercial" closed source job offerings. And I don't see this changing in the near future either (sadly). Sure, open-source jobs might pop up here and there, but the majority of jobs available will be closed source jobs for a very long time to come.
I'm now working more than half time and studying full time, and I don't really buy into that "code free software in your free time" argument (1) I don't have any free time 2) if I had any I'd go out for beer). Besides, full time development on an application can't be compared to putting down a couple of hours per weekend.
And another point; the majority of ordinary companies don't care one bit about if you've done free source development. All that counts is experience from a commercial environment. (This is at least my experience from going to job interviews).
And the comparsion between open source coders and artists is flawed. If I'm a real good actor I can get a job at a a theater. If I'm a real good open source coder I go to work on closed software. If I'm a really bad closed source programmer I go to work on closed software (might take a little longer before I get a raise though;).
MAC address spoofing is easily done in software for all cards. A little greping in the kernel sources will find you the place where the kernel inserts the MAC address into the ethernet-frame.
Slashdot Mirror
> so it's your chosen package, but without
> even taking a look at mythtv you trump it
> as more mature?
IIRC MythTV got DVB support a little over a year ago,
about the time I got my first DVB card. Support for
full featured cards (cards with decoder) may have
come even later.
vdr on the other hand has had DVB support for
about 4 years.
So a year ago MythTV was very bleeding edge (at
least regarding DVB support), whereas vdr just
worked, and had been working for several years.
> (vdr doesn't have plugins for 'all those
> buzzwords' as you put mpeg4 encoding to be)
The vdrrip plugin which I use uses mencoder.
So it's a breeze to mpeg4 encode recordings.
> looking at the features, mythtv looks like it
> does more, a LOT more.
> including stuff like picture in picture, multi
> card support - and get this, transparent multi
> machine support: "Distributed architecture
> allowing multiple recording machines and
> multiple playback machines on the same
> network, completely transparent to the
> user.", rss, mpeg4, mpeg2
> decoders/encoders and a whole lot of other
> stuff.
Uhm, there are vdr plugins for all those buzzwords
(except for "rss" maybe, but I don't know what
that means in this context). (Multicard support
is of course supported by default).
It's been a while since I've looked at mythtv, but
vdr is much much more mature.
And the best thing about vdr; vdradmin with its autotimers:
http://linvdr.org/projects/vdradmin/
Thanks to vdradmin I seldom watch TV realtime
anymore, and I almost never program vdr to record
individual programs, I just feed vdradmin patterns
or regexps!
Regarding item 2, I had a colleague at a University I worked at, which had a "proof" (I didn't look into it and it wasn't published but rather a good discussion and it was a bright guy) that a garbage collector was faster, in theory, in certain situations.
:->.
In a copying garbage collector, the work required is proportional to the live memory. With manual memory management, the work is proportional to the amount of garbage. So given enough memory, garbage collection will always be faster, "even if the cost of freeing a cell is only a single machine instruction" (Appel). Garbage Collection Can Be Faster Than Stack Allocation by said Appel is a good start if you want to know more.
The key phrase here is "given enough memory". And in my experience, I've never succeeded in giving real Java programs enough memory
The Canon Powershot A80 can be an excellent alternative for a beginner. It's not a SLR however. Read this useful review.
> Actually he's of Swedish descent but his family lives in Finland.
Close but no cigarr. He is a swedish speaking Finn. Finland is a bilingual country.
> Like smalltalk. Early 70s, IIRC. The problem of
> managing increasing software complexity, which
> object orientation (partly) solved, became
> significant only much later.
I know this is the common perception (i.e., that object orientation solves software complexity), but have you ever seen some scientific data backing this up? I have seen one or two very small scale investigations of this that can be taken seriously, but that's all.
The problem is of course that it's very expensive to compare programming paradigms. You need several large developments teams (at least one doing OO, one using something else) developing the same application, and you need to investigate more than one application. And you need to make sure the programmers are at the same level of skill, etc.
Anyway, if anyone has some referneces to scientific studies actually showing OO reduces software complexity, I would be interested seeing them.
(Note: I'm not claiming OO doesn't reduce complexity, I would just like to see more than handwaving proof of this).
I'm also a fan, and I have to agree. Somewhere along the line it started reminding me of the kind of tv-series which where great in the beginning but just continues season after season until you can't remember why you watch it anymore (e.g., X-Files).
:\).
I haven't actually finnished Winter's heart yet. I bought it a few days before the official release date, but as you say, it's slow. And I'm having a lot of troubles remembering what has happend (or even caring
But the beginning of the series is absolutely superb.
Here is an embedded port of the Python interpreter: http://www.abo.fi/~iporres/python/
Here is a free online book about crypto: http://cacr.math.uwaterloo.ca/hac/
Making money on free software might be possible in theory, but in real life it's not that easy. I seem to get contacted by one or two companies every month nowadays with job offerings as a programmer (programming ordinary commercial closed source software). I don't know of any company I could apply for a job where I could be doing free source development.
;).
For every job where you get paid to write free software there are several order of magnitudes many more "commercial" closed source job offerings. And I don't see this changing in the near future either (sadly). Sure, open-source jobs might pop up here and there, but the majority of jobs available will be closed source jobs for a very long time to come.
I'm now working more than half time and studying full time, and I don't really buy into that "code free software in your free time" argument (1) I don't have any free time 2) if I had any I'd go out for beer). Besides, full time development on an application can't be compared to putting down a couple of hours per weekend.
And another point; the majority of ordinary companies don't care one bit about if you've done free source development. All that counts is experience from a commercial environment. (This is at least my experience from going to job interviews).
And the comparsion between open source coders and artists is flawed. If I'm a real good actor I can get a job at a a theater. If I'm a real good open source coder I go to work on closed software. If I'm a really bad closed source programmer I go to work on closed software (might take a little longer before I get a raise though
MAC address spoofing is easily done in software
for all cards. A little greping in the kernel
sources will find you the place where the kernel
inserts the MAC address into the ethernet-frame.