modules that are constantly changing are more scary
Not that I don't agree, but let's not generalize. Some modules constantly change and that might be a good thing :-)
what if an interface changes
You can always write a wrapper.
or a bug is introduced
That's what tests are for. If the author doesn't use them, you can write them yourself (and even if the author refuses to include them, you can run them yourself just to make sure everything's OK). And you can also stay a couple of versions behind at all times.
At least with static code, you know exactly what you've got
Presumably... :-) | [reply] |
My point with "constantly changing" modules is that some authors are like kids with ADD...there really isn't a rhyme or a reason to what they're doing at any given time. So, you get v0.02 of a module, find that it does the job "well enough", only to find that when v0.03 comes around, the whole architecture has changed. If the interface is consistent and the behavior is somewhat consistent (modulo new features or bug fixes), then okay. Having to write a wrapper is, in my opinion, a signal that either you got the module at a time when the module was marked alpha, or the maintainer is one of those maintainers who just changes the interface on a whim. The latter are the ones that I take issue with.
thor
Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come
| [reply] |