Well, today I finally cut the cord with any of my Xojo / REALbasic legacy roots. I have no software in production, or for sale that was Xojo / REALbasic born, and I’ve removed any references for same on my web site and resume (calling Xojo / REALbasic a “cross platform development tool”).
What a boondoggle that was. Live and learn.
I checked out Unity. It looks great. I don’t know that I have 2 years to invest in a learning curve for another development technology. So I’ve settled on Swift for my UI stuff, and good old C for the plumbing for my next app.
welcome to the lighter side… if you have any Swift question especially about various Swift versions of “Xojo controls” drop me a line.
Am currently working on a drop in control that will handle a Single Column “Listbox” and should work for iOS, macOS and even tvOS (with a few tweeks). It is fully self contained for “string” type data, but can easily be modified for more complex cell types (something I may do later)
Or while pros are starting whining. Real pros in the beginning and other ones after years. Reading old forum entries and old nailing list entries it was always a bug collection. And no, java was never like that
Yep, where is Marco Bambini and the other heavyweight (can’t remember his name) that were working on this product at one time. For pete’s sake you could email them back in the day.
Welcome to the club. I mean, I think we all would like Xojo to succeed but, at least for me, Xojo doesn’t want me to succeed. Bug, web2, API2, were not just straws that broke the camels back but whole bales of straw.
I’ve been (mostly) happy working in Go (error handling still leaves me mystified at times. I’m strictly on the backend and enjoy being a worker bee after 20+ years as a consultant. I have zero clients left and any software of value has already been sold off.
I had to do code review on some Xojo code the other day and it felt like a foreign language. So I guess the retraining has worked. Do I miss it? Sometimes because it just did some many things for you that most other languages/IDE’s do not do. I tell my Go coworkers that I’m a ‘spoiled Xojo developer. please help me fix that would take me 5 minutes in Xojo’
I know, right? But from what I saw @bkeeney you developed some cool stuff, and grew a consulting business, no? A few things that were software engineering problems that I’m glad that I did (in REALbasic) was develop a “double buffering” Windows screen repaint (Mac does this already) for my Gettysburg game. I developed an Outlook Message parser RB plugin (C effort), and an RB Spell Checker class. Away from the foibles of RB/Xojo these were engineering efforts, figuring stuff out kind of thing.
The thing that really frosts my cookies is the “money grab” mentality that this poo show company devolved into, it is shameful. I mean the customers are literally testing their software for them at the customer’s expense, and running rough shod over any semblance of legacy code support.
None of the cool things that I mentioned even compile now. I’m talking years of work. Out the window. The only thing that I have of value is the engineering experience solving the problems that I mentioned.
I wish that I could remember the other dev’s name! In the most flattering way possible I say that he looked a little like Napoleon Dynamite. He and Marco were solid. And a reason that I took RB seriously.
Many users pleaded with Xojo NOT to make some of the changes they have in recent years
This is especially true of API 2 since it would throw away years of code and also silently introduce breaking changes since it would suddenly start throwing exceptions instead of using error codes for many things
Sharing information about this individual. When I was working at the Whitehouse, he emailed me and asked me if I could get his daughter an intern job. Fair enough. But it was the way that he asked, you know? It left a very sour taste in my mouth.
