Have you heard back privately (or on another thread) about this issue from the SB team at all?
Not to be a negative-nanny, but SB being a subscription service, is really supposed to be ahead of the curve and keeping everything behind-the-scenes fully up-to-date, otherwise what's the point?
In my opinion, SB must absolutely, positively resolve these types of issues with the utmost haste and priority, or they should not be in the subscription business. Also, as a language, it's not feasible for commercial use, if it's this far out-of-date on something so crucial. Creating/publishing Android apps is one of the core purposes of using SpiderBasic - its a key part of why the language exists in the first place! This stuff
MUST be kept up-to-date, IMO, otherwise, unfortunately, SpiderBasic becomes nothing more than a neat toy for many of us.
I can't tell my clients, "Sorry, the program you paid me to write is great, but I can't release it on the promised platform because my language's publishing support is out of date, there is no work around, and there is no more information at this time, so just wait indefinitely..."
How well do you think that conversation is going to go?
I'm about to start a fairly large, long-term project and was going to buy PureBasic (I already subscribe to SB) and use SpiderBasic + SpiderBite + PureBasic + PureVision (PV for some quick admin form building) to develop this project, but now I'm seriously concerned that I won't be able to release the Android app on the Google Play store, which is
ABSOLUTELY REQUIRED in the spec - and we are on a fairly fixed timeline. This whole situation is sad, and greatly concerning.
Where is the development team in all of this? Why has this update been ignored for so long if it's been required since August 1st of this year? (It's nearly mid-September now.) Shouldn't this have been updated
BEFORE the cutoff date? What do we do? Are we all just stuck? Again, not trying to be a downer, but if this is how the future looks for SB, well I'm suddenly pretty afraid right now to walk this path. I may have to invest in different tools, because this
AMAZING language/compiler just doesn't seem to have the necessary support required to stay up-to-date so we developers can count on it commercially.
Any additional information? Can anyone give me some hope? I
WANT to feel good and continue with this platform, but silence will force me to move on, because I have
REAL WORK that needs to be done and no time to waste hoping for an answer that may never come.
I'm nervous about this situation - very nervous, and now I'm super-apprehensive about moving forward at all. Not good.
PLEASE, someone from the SB/PB team, give us an update!!! I
WANT to believe... ha ha, but seriously... Is SB a dead product? I shudder to think...
Please help. Please, someone tell me I'm just panicking and that everything is under control, an update is on the way, and future plans for SB include being fully updated on this stuff before any hard cutoffs? Pretty please?
C.K. wrote:
Has this been resolved with SB yet? If not, have you found a workaround to allow you to deploy?
Unfortunately not yet; And not working workaronds...