I generally only release code that I am going to use myself in some way. I figure, the work is done anyway, why not share? I am not microsoft and am not being paid for the code. So, my target audience is NOT non-coders. My target audience is coders who also release their work.
This way, I get a benefit because my code gets tested harder and sometimes useful feature additions are suggested. And, my fellow coders get the benefit of having something that they can use in some fashion or another.
I will agree that most people should release their hacks to the beta forum first and let the kinks in installation instructions get worked out. I also think the current sorting system brings some of the worst hacks up to the top instead of letting them sink. Unsupported code often has the most cries for help, which means it stays at the top of the heap and gets more attention, more installs by people who don't READ before they try to install and then more replies, which keep it at the top.
If you want to avoid bad code, it's your job to read and see if users are having problems. If you can't code yourself, don't install very new modifications. Give them time to either have the kinks worked out or to prove that they are stable.
|
03-10-2005, 05:32 PM
Hybrid Mode
