In case you don't have enough to do this week, here's another
interesting article that just came my way on another list. It's from
2000 but the message is timeless:
"There's a subtle reason that programmers always want to throw away
the code and start over. The reason is that they think the old code is
a mess. And here is the interesting observation: they are probably
That and "joel's best" are in the Joel on Software book. It's a very
readable and interesting book. I don't think he knows well everything he
talks about, but he has a keen understanding of what works and what doesn't
work in bringing a technical product to fruition.
I have a good question. While we're talking about updating with new
'builds' what exactly should be replaced besides the engine? What is
everyone out there doing? In the first public 2.6 last week, casual
observation revealed there were several internal stacks that had been
updated, not just the engine.
It's not really clear what stacks in a rev package get updated or
not. There seems to be a blur between Rev and User areas. I have a
lot of plugins and settings files and image libraries and upgrading
is a time consuming process. Perhaps I'll have to make a 'clean
installer' (like I used to use with Mac OS 9).
I'd like to keep everything updated, but the only good way to install
Rev seems to be start from scratch with a fresh install, and drop in
certain stacks one knows for sure that one needs from the older
It would be nice to know the build and version numbers before
downloading. Also I always have to rename the downloaded .pkg files-
they're all named the same. (I keep fresh versions of all builds I
use-revolution mailing list
[hidden email] http://lists.runrev.com/mailman/listinfo/use-revolution
On Jun 14, 2005, at 11:36 AM, Stephen Barncard wrote:
> I'd like to keep everything updated, but the only good way to
> install Rev seems to be start from scratch with a fresh install,
> and drop in certain stacks one knows for sure that one needs from
> the older folder.
This has been a complaint of mine from the beginning and every time
there's a new release, I gripe about it some more. I know RunRev does
understand the problem and plans to fix it at some point. My guess is
it'll be part of the next major rev of the product, which Kevin has
intimated will come in less than a year's time.
As it is, semi-manually updating everything is the only way I know of
to make sure everything is as it should be once an upgrade is complete.