and here we are again… discussing the course of a former good idea and product getting more and more lost due to the fact of poor management and missing long-term-orientation. Lessons not learnt, not with Web, not with iOS and now not with Android.
Now the “Pro” Customers have to pay for another target, which in best case can be considered as alpha or experimental while the existing targets aggregating more and more bugs. Linux Desktop as platform is quite unuseable, Web aswell and the bugs and quircks in Windows and Mac moves Xojo more and more away from RAD than ever before.
Today I never could give any customer a quote for anything written with xojo.
My final statement on this… Xojo is dead. The Business Model of Xojo Inc is failing.
And damn I blame Geoff for this failure, because for many years I loved Xojo and it brought my Business forward.
The F*ck, bring a GPLed version of Xojo… release the sources so more manpower can fix or fork the mess you have created the last years.
I still can’t believe, you pay money for an additional abstraction layer (Xojo) full of bugs and quirks to end up with declares. But of course there is always an addon for something, another abstraction layer, increasing your technical debt and makes you more depended on third parties with even more money to spend. And they dare to call everything “Professional” or even “Enterprise”.
I consider Xojo Inc’s business model as scam. Of course there will be some weirdos buying this, but after a learning-curve with real-world (paid) projects, they will find out, what we already know and experienced the last years.
In any case, it shows that the green company is very self-confident. Just as I (and likely many others) came to the conclusion during the development of Web2 Plugins that I could also use TypeScript for everything “web”, the same could happen with Android. Especially since Kotlin is quite nice and from there it’s not far away to Kotlin Multiplatform … a dance on the volcano …
yeah I’ve filed many many many of those with various causes
pretty sure this is a fault in the transpiring of Xojo source to Kotlin source that the kotlin compiler then pukes on
And with NO information from that compiler to even know what to fix it leaves you with 2 options