Rewriting WinAmp from scratch (part 2)
Some time ago there was an topic on this forum about WinAmp's rewriting from scratch being a good or a bad thing. Today I was bored coding and decided to check out new skins. This is what I found:
i d/l the XP skin. It kick ass.
rewriting a proven solution from scratch is never a good idea, as any good programmer should know.
Whether the decision to rewrite from scratch was a good one or not can only be judged by the people who were involved on the process, I guess. Maybe refactoring would have worked better or as well. Who knows? I agree with Jan on the quality of the outcome, though. The new WinAmp rulez!
I still use the old version of Winamp. I didn't like the new interface and the fact that I couldn't find the buttons I needed on some skins because they were apparently not worthy.
Re-writing some areas of code can be the best course of action if, for example, a major shift in functionality or look is desired. Forcing code into contortions it was never designed for is painful and bug-prone. It's wholescale 'baby-with-bath-water' rewrites that are a problem.
I can't stand products that waste development time on skin-enablement. There is nothing more useless and time-wasting than skins.
winamp actually sold for $100M. there is an untold part of the story involving the fact that one of the winamper's relatives is an old-school silicon valley merger negotiator. ;-)
I agree with pb, skins are a turn off.
Fog Creek Home