About the same # from what I recall
5 or so
Iād have to ask Aaron or one of the the others who was there at the time to be more sure
Donāt forget that genius works on his development skills every day, and by now, he can likely handle the workload of five to six senior engineers with ease.
Furthermore, everything has become much simpler and more logical with API2. The factor of natural intelligence, which consistently outperforms AI, should also be considered. However, I lack the intelligence to evaluate this conclusively.
1 Like
Which speaks volumesā¦
-Karen
5 Likes
Are you sure you dont do standup as a sideline ?
To be honest, Iām surprised that I havenāt yet been banned or suspended.
Maybe theyāve come to realize that banning & suspending the last few folks who still are very experienced AND willing to help out wouldnāt be in their best interests ???
I know I know ā¦ am I crazy ? 
2 Likes
For fucks sake. You know what. It aināt my problem. I donāt need to get involved, nothing good can come if I get involved. What a joke that people pay $800 a year for.
Just you get angry, frustrated, pissed off (name another emotion)
I get it
I really do
Iām at the point I report bugs
if they respond I basically dont because I already did my bit and if they want to take action on the bug great, if not oh well
I already did my bit
My attitude is basically that Iāve resigned myself to this IS how things are and how they will be
And when client(s) say ālets look at something elseā Iāll be all over it
3 Likes
The last one I tried to file was āunreproducibleā, yet when it does happen (twice now), it crashes the IDE by simply toggling a checkpoint in the code editor and boomā¦ its all gone.
Xojo wouldnāt even investigate unless I could give them reproducible directions. They have the friking crash report, at least go look at that routine to and see if thereās anything that sticks out.
But then again, I do that for my customers. I will take as much time as a customer is willing to give me, to track down unreproducible crashes. I got one this week thatās caused problems for a couple of customers. Better reporting and more code checkpoints helped me narrow it down.
I am always grateful when a customer will help me with their time.
Turns out it was a NOE, in a function, but the stack trace didnāt list that specific function, it started from 1 step above. Displaying the stack trace in a MsgBox on the customerās Mac was causing my app to crash and Venture wasnāt displaying anything to the customer, app just disappeared from screen.
So now I need to see if thereās anything I can do to solve the stack trace inside a MsgBox crashing on that customerās Mac.
Stack traces are not always sure to give you the actual routine name
Even in Apples crash reports
Most times they are reasonable but there are ways they can be 100% wrong too.
Would be nice if that wasnt the case
And Xojo strips symbols from their framework so if the issue is there you get just that its IN the framework + a giant offset like
8 XojoFramework 0x0000000102d577f4 0x102c77000 + 919540
there was just a bug report about something like this
https://tracker.xojo.com/xojoinc/xojo/-/issues/71386
maybe its related ?
1 Like
Thanks, the failure doesnāt occur in a modal. app.unhandledException displays a message to the customer, with a stack trace and basic system information (some customers wonāt send you the report, but they will send you screenshots of the error dialog). However in this case (and I donāt know about others) the MsgBox is never displayed, logging shows that everything builds up fine, but on displaying the MsgBox is when it crashes. I will look into the crash reports today and see if I can get a better understanding of why.
I might try to replace it with declares to NSAlert and skip the Xojo MessageDialog, but there was some reason as to why I didnāt do this in the past.
In fact, you know what. Now I know why it happens, Iām going to remove my fixes and reproduce it on my dev machine. The cause is an OSObject that I never assumed would be nilā¦ Is nil for these customers. I know that this is my fault and I accept responsibility.
Edit: Addendum:
I just looked at the recent crash reports and itās a NSException, which means that Xojo is doing something wrong in their framework which causes the MsgBox to crash. It only happens when it tries to display the stack trace either for this function or for these customers, I will experiment further, maybe I will have to give up on their MsgBox/MessageDialog framework also.
I was quite surprised when I filed my first bug. I mean I know how to write a bug up ā expected vs observed behavior, system and environment, steps to repro, all that jazz. I took probably 30 minutes of my life Iāll never get back writing it up, and the first question out of the testerās mouth revealed they didnāt read what I wrote. I specifically said it was Postgres-specific and they complained they couldnāt reproduce it with SqlLite and to please give me a sample solution demoing the problem. Which tells me they took a quick swipe after a cursory read and gave up.
This isnāt even necessarily a dig on the tester, he is probably doing the work of 10 people from what Iāve come to understand since.
But by the time I got to bug #2 that was my attitude as well. After #2 I think I did one feature request which I kind of regret because that made it into their work queue while the actual bugs languished. And my feature request, while perfectly legit, was not a high priority thing. It was basically guard rails for noobs (and people like me who arenāt quite used to their creeping senescence yet) so I suppose this confirms they are currently pursuing that demographic.
1 Like
Don#t get mad above it. Not worth of it. When I am looking back for what kind of Software I was looking and now programming an App with JavaFX I have no questions about anything anymore. JavaFX is so bright and nice against. And yes, it is much better than all Xojo provides. For Desktop, Web, Mobile. And it costs not more than Xojo costs. Thatās the funny part on it. Xojo wants to get much money for nothing (what remembers me to dire straits)ā¦and not working Solutions. The entire Point is: no change in their Bug policy, no change in their behavior. And yes, I believe also you will be banned one day. Like everybody complaining about. You are welcome in other places. And at least here if it will be happen.
1 Like
I had a strange moment days ago with 2021r2.1:
my small (less than 20 lines of code) code was loosing lines, then the Method parameter disappeared.
I was lucky enough to realize what happened AND remember what I wrote there.
I completed the code, add the parameter back, save the project, then shut down the computer.
When I powered ON the m1 laptop, the weird does not re-appeared.
I already wrote that, but sometimes I am aslink myself if I am cursedā¦
(of course, not, but this looks like !).
MacOS 13.3.1 (a) (or MacOS 13.3.1, hard to tell).
Nota: I discovered that I used the same name for a Property and a Variable. I noticed a strange behavior: sometimes it works fine, sometimes not:
The Row where a date was added was correct, but only sometimes at unpredicted time. Sometimes, the date appeared in Row #0ā¦ Sometimes it appeared where I clicked.
That, until I realized my error. Once I removed the local Variable (Var Foo As Integer), the day say the sun shining 
.
Remembering that Variables should never have the same name I have also to declare: yes, Properties in Xojo are also what? Yes. Variables. And the Compiler sometimes does not complain when the user tries to target his own knees with a shotgun. Variables and Properties should never have the same name especially not in the same class. Not in Xojo, not in C++, C#, Java and what ever. Addressing that can only fail. And that is not strange. Strange is to use in a class the same name for a variable and a property. Sounds so weird that I canāt see why somebody should do stuff like that?
Of course, I do not know how this was possible.
That said,ā¦
Errare humanum est
Perseverare diabolicum !
Excepted if you are a genius, you are entitled to make errors, ant it may takes time until you realize it was an error.
Well, that Wikipediaās Quote says āTIOBEā, NOT Tiobe index, and says Software, NOT programming languages.
TIOBE the company actually DOES rate the quality of software and they offer that as their product.
This is correct. However, the TIOBE Index is not a software quality rating. Insinuating that a listing in the TIOBE Index is a quality rating by TIOBE is grossly misleading.
2 Likes
plus - on the level they are listed, who really cares? 
Oh that was not addressed to you or better I was not allowed to address it to You. The idea And the compiler should not allow that. It is strongly recommendet not to have two variables with the same name in the same namespace. Therefore I have also to apologize that means not you but the compiler and ide people