CM> As a programmer, though, would you think it prudent to release new
CM> versions (betas) without including any info whatsoever with that beta,
CM> such as what has been changed, added, removed, etc.?
What has prudent got to do with any of it? Whenever we release new
versions of our software, we simply list the bugs that were fixed but
make little mention about other tweaks that went into the software so
the testers can regress the bugs and then just work on breaking the
software as a whole (video games, they are).
CM> For the longest time we never got any of that info; eventually, we
CM> started getting *some* info, but often not at all, or late, and
CM> often with the appended "other things that I forget right now," or
CM> something to that effect. I repeat, sloppy. And
CM> counter-productive, I would think, from a business standpoint.
Nothing relating to business, it's ONLY a feel-good thing for end
users.
CM> It has MUCH to offer a user, but more and more, it seems, LESS to
CM> offer a more casual user.
Agreed.
CM> It's very confusing for many who are trying the program (in my
CM> experience, anyway, having recommended it to many in the past).
CM> Much is undocumented, or documented poorly. It's a shame.
Agreed. It's obviously not designed by non-programmers. This is
something that they *should* fix, but will they? I wouldn't bet a
dime on it.
I don't recommend TB! to anyone outside of power users. It's just not
worth the effort for most people.
-tom!
--
Hopin' this said *something* useful, [EMAIL PROTECTED] out.
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
