I am simply suggesting that the Opportunity cost is high for creation of the DOCS right now.
as you'll recall, Opportunity cost is the hidden cost of any decision. basically when you choose to do something, you are choosing NOT to do several other valuable things.
in this case I think that the decision to code BlitzMAX, fix bugs and release 1.0 on Win32 and Linux is a more valuable use of time than improving the docs.
as you'll recall, Opportunity cost is the hidden cost of any decision. basically when you choose to do something, you are choosing NOT to do several other valuable things.
in this case I think that the decision to code BlitzMAX, fix bugs and release 1.0 on Win32 and Linux is a more valuable use of time than improving the docs.
Perhaps, though I doubt all Mac users would share the sentiment. However, you'll recall that you initially included the 3d engine in the list of things that were more time-valuable than finishing the documentation. I'd argue that waiting until the 3d engine is finished before finishing the docs for a product people have already paid for could have quite a large "hidden" cost in people going elsewhere for a properly documented language and not even still being here when BRL want to sell the 3d engine.
I'm sure it's fun to dig around in the source, figuring things out by yourself, and there was a time when I would have been doing just that, but as Warren points out, there's a rather large "opportunity cost" of our own for those of us who are using Blitz as a full or part time "job" to effectively document the language ourselves.
So far, I'd say about 25% of what I've learned of BlitzMax has come from the docs and the other 75% has been from eager forum members and my own investigations. It really ought to be the other way around.