Reply to thread

Message: <blockquote data-quote="Scribble" data-source="post: 5533891" data-attributes="member: 23977">I can't really argue with any certainty one way or the other about this since I don't know all the inside info. From the outside though, I can see a HUGE amount of potential that I didn't see available (or as easily available) with the offline builder(s.)There's a reason more and more software is moving to the cloud after all. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />Might work, might not- we'd have to look at the costs involved with maintaining such a system. Off hand it still seems susceptible to the unintended revenue leak I mentioned before. Would it help one of their other goals which was to combat piracy (And by this I mean at least trying not to blatantly help piracy)Also- what about Mac support? What about future products? How easy/hard would it be to tie the old CB in with future plans? (I get the feeling they kind of eventually want the online stuff to function as almost an xbox online continuous convention sort of thing... Log on and jump into a game at any time.)I doubt it... <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":P" title="Stick out tongue    :P"  data-smilie="7"data-shortname=":P" /> Anytime a change is made there will be flack.I think the main amount of Flak seemed to come from loss of current functionality.   I don't think that had anything to do with going to a web based system- I think it had to do with a release date that didn't match what was actually needed to complete the system (which could have happened with anything they did.)Sounds like a reasonable assumption, but without seeing the original code, it's hard to tell. If the original CB was a bloated mess coded with little to no ability to easily be manipulated and re-purposed, then no, it might end up being the opposite actually. (You might end up spending more development time just figuring out what the heck the original code DOES for instance.)Maybe- maybe not.Anything seems good when you assume all the risks involved don't pan out.</blockquote>

Verification