Quote - while i agree with what beryld said re pre ordering or not pre ordering i have no sympathy whatsoever for those building the p7 program and i don't want to take any courses in anything. it's their job,. they get paid to do it not me. they should do what it takes to put a working program on the market. if works all well and good if doesn't then they didn't do their jobs properley, end of story. if i buy software that just at least works but is bug ridden of course i'll complain. if the bugs are many i may even ask for my money back. any product should do what the manufacture says it will do

personally i'll wait and see if it has a better rigging and joint editing function. if it doesn't i'll stay with p6. i don't use it enough to warrant buying it unless these two specific items are covered.

billy

It is true that it is their job to do the best job possible - within means (temporal, financial, and resource limits).  But can you honestly name a single application (or OS for that matter) that doesn't have bugs, issues, or lack something being requested for a long time?  Note that all EULAs mention that little caveat - "the Program and the Documentation are provided to you as-is without any expressed or implied warranty of any kind..." (that's part of Poser's EULA)

This isn't like buying an article of clothing where not only the craftsmanship and materials should be worth the cost but it also must fit you alone.  This article of clothing has to fit everyone.  Making an article of clothing that does that would be an achievement indeed - especially if it were a three piece suit, hat, tie, and shoes.  Now multiply that by about a trillion and you have your reason why computer programming can never be about it being perfect.

There was an interesting discussion wherein programmers were trying to decide the simplest executable that could be considered 100% absolutely free of any possible error under any condition - the most likely candidate was the famous "Hello World" usually employed as a budding programmer's first and easiest program.  It usually comprises something like this (C):

#include <stdio.h>

void main()
{
    printf("Hello, Worldn");
}

How can that possibly bungle up!  Well, for starters, a programmer could make a typing mistake at any given point.  I'm a veteran of 20 years who can type (if you hadn't noticed) - and I've had to issue critical updates on a SINGLE mistyped character - these things happen.  If you read enough books, you are bound to find out that there are dozens of typos in every one of them.  To err is human, to stop expecting divinity is being a better human (!!)

To continue with this, it was disclosed that errors in the standard headers, variations in the OS, different compilers/linkers, and all sorts of assorted sorted issues could actually cause that most-simplistic application to crash or be non-functional.  Now, multiply that by tens of thousands or millions of lines of code.  Yes, it is the programmer's job to make it work - as best as can be done within limitations.  Code that consistently works on one set of systems may not work on others when whatever is causing the errors was not tested for.

Here, for all to purview, is a program that works 100% flawlessly:

That space above this line is it...

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone