Reply to thread

Message: <blockquote data-quote="Sm!rk" data-source="post: 422609" data-attributes="member: 6467">My mention of standard breaking down weren't so much about what features you choose to implement, its deciding to use X, Y and Z generators in your generation process but then not sharing the end result in kind.Frankly, with VB there is no other option for you. While VB and Java can both use C/C++ libraries, that is not the case for VB going the other way. I doubt you can make any sort of sharable component with VB short of maybe activeX controls. But in regards to what a few have already said, there is no cross-platform-ability with VB at all. So the point is now confused in my mind, huh?At some level I see no difference with using libraries and TCP as the communication. Libraries will no doubt be quicker since the bindings are in place and don't have to be renogiated with each connection. And TCP or any network protocol offers obscure thoughts like a real random die server on a linux machine connected to a radioactive source, which I can poll to get random die rolls from my Palm or PPC. Of course random NPCs or whatever, might be an interesting thought for ad-lib LARPs where you manage and create everything on the fly and get streamed the data to a PDA or notebook.Or even "real" living worlds, where DMs from anywhere can download time segments that they then run with their campaign. Then later they upload specific changes, like thief guild member Snarky was killed. PC X and Z purchased the shoddy warehouse at 123 Port Road.Thats just some examples you could find many different uses. So it is powerful, but what kind of work load will it be to finalize a standard for the interoperability of any number of apps. And you'll defintly need some standard or else who else will be building these other useful products? In this sense GPL and the like are contracts between different programmer that say, you don't rip me off, I won't rip you off (In an untrusting world...).And while the lego analogy is appealing, there is no way this can be as simple as lego interoperability, where you have one inny nub, and one outty nub.Anyway to interject some egoism, I wouldn't mind coding to some adopted standard agreed upon by a community at large, but there is very little chance I would code to an SDK from one particular developer, unless they own the world like MS does.</blockquote>

Verification