There is no possibly way for you to know that. Or does everyone who decides not to use Xojo writes you an email telling you their reasons? Ah welI, it’s my bad. I shouldn’t have reacted. I was just almost literally blown of my chair on how someone could make such a public statement. Please continue on topic. I’m out…
I’m a data analyst at a much larger company than Xojo. These are 10k foot metrics and actually don’t have that much value. If I presented something like this I would be told it means nothing.
- What is a medium-sized company? What is this population and how is it gathered?
- How many bugs are marked as duplicates?
- What is the spread of severity? are 90% of these extremely low priority? High? No severity?
- What is an update? Comments? Code Commits? Releases?
- So many assumptions in the assessments and they are all 1 or 2 liners?
Finally, why post in a public forum? What does this do? Who is this for? Xojo has a business email…
We have a system that follows up with people who download and then never purchase. While every prospect doesn’t reply, we get enough to understand generally why prospects don’t become customers. This is important for anyone running a business to understand. And let’s please keep this conversation civil.
If you are serious about data and analysis, you will back up this pointlessly provocative statement with a well-founded survey and comprehensive analysis of the results.
I eagerly await the paper.
This is decidedly not what you have been doing in this thread, and this is a misleading reframing of the discussion as a whole.
I’m a user since first releases, maybe Version 3 under MacOs 7.x or 8. Don’t remember well. The sense of community was very strong. Big work was done. Now it’s like any other company. Does the Bug Tracking System bring any revenue to the bank account, directly or indirectly ? Are the cost of bug fixing justified? We can’t know it. Only Geoff knows it. I think this are sensitive data that we can’t have, so trust in yourself. I don’t know if it’s the case anymore, but in the past people could recommend to friends and schools which tool to use. Now, I could never suggest to anybody to start any new project with Xojo. Unfortunately.
We moved away from Xojo due to bugs.
I’ve started diving into the bugs to try and paint a clear picture for everyone. My first step was to categorize them by severity.
However, it looks like there’s no severity tag or a “Showstopper” tag in the bug database.
Wouldn’t it be helpful if we could track the severity of the bugs? What do you think?
following your analysis this is not the problem. Problem is the speed rate bugs are fixed. I’m pretty sure Geoff knows this.
It’s more relying back to a business strategy to hurry up by acquiring new customers. I’m not sure but it seems more to build a good opt-out scene for Geoff…
Xojo’s value raises only by number of customer base and not for it’s satisfaction
So, after realizing we can’t identify severe bugs due to the lack of tags, I moved on to my second step: focusing on bugs that are open and marked as needing review.
At the moment, there are 343 of them in that category. These are bugs that have been reported and flagged for review, but not reviewed : Bug Tracker Link.
However, after diving in, it’s clear that a lot of these entries are, frankly, junk. And the sheer amount of junk cluttering up what should be a critical system raises questions about how effective the current process is. It’s worth considering how this impacts the usability and reliability of the database. Thoughts?
For sure there’s something wrong in the bug tracker and how it’s used internally in Xojo’s company.
We customer can only express our feelings. Maybe Xojo could send out a survey list every 2 weeks of 50 most oldest bugs permitting customers to give a vote for the 15 most wanted bug fix. Beginning with the most oldest ones!
Any change has a cost, so the most questions can be answered only from who decides the strategies. We don’t know which is the target that Xojo wants to meet in the next 5 years and even in 10 years.
I hope that this/those person have at the least the right skills for decision making.
For sure Xojo biggest client’s base is now near to it’s retirement, same for Xojo’s owners… so now what? Which are the short and long terms target? I don’t know.
Dear Geoff, so why does Xojo have a bad reputation on Google?
4D Developer speaking.
I like Xojos bugtracking system very much because it is open and can be seen and searched by anyone (point in case: this discussion).
Of course you can report bugs to 4D but they keep everything under the rug. So if different developers report the same bug 4D is saying to each of them “oh, we never heard about that bug, you are the only one.” when, in fact, you now from collegues that they have encountered the same bug (and were beeing told the same crap).
Advantage: Xojo.
Bernd:
Like saying: I am fine because there are others who are worse than I am
If there are 5800-6500 licenses sold per year, how many of this people are really interacting with the bug tracker?
Well, there are a lot of comparisons in this thread with companies that are “better”, so why not allow comparisons with companies that are worse?
but it really seams to be out of control due to the quantity of bugs. And Android support is not even at the beginning of a serious approach… what then? This is about the stat’s how the bugs are treated in Xojo. You can only learn from who is better than you, not from who is worser
No, not really. I find a lot of really weird bugs. The only bugs that matter are show stoppers and even those are highly specific for each person. After checking my bugs there are only 1 or 2 of that category in my over 50 open bug reports.
Interesting because this is a basic property in VB6
Junk is just apart of data, i can’t tell you how many times I get “how do I open a bug report” as a bug report at work when I worked support. I’d close 10 of those a day.
Our system are only open to employees and not to people who could be teens learning computers and programming and the general public.
This fact alone will make a system bogged down but I would be more upset if it suddenly was closed to us or had gatekeeping for bug submissions.
Honestly you shouldn’t even be looking at anything not marked “reproducible” and then split it into crash vs not crash bugs.
However, after diving in, it’s clear that a lot of these entries are, frankly, junk. And the sheer amount of junk cluttering up what should be a critical system raises questions about how effective the current process is. It’s worth considering how this impacts the usability and reliability of the database. Thoughts?
That maybe you shouldn’t have undertaken an analysis of this unreliable data, to try and prove a point that is only vaguely qualitative?
Your scatter-shot attempt to push forward a narrative that Xojo Inc. (a software company that has been in business since before I learned programming - and I’m now retired) urgently needs to address its “inefficiencies” has only resulted in stirring up people’s emotions, passions, defensiveness and, yes, doubt.
You’ve garnered a wide spectrum of responses. If you plug in your AI to analyze these responses, what will you have learned? Nothing useful, I think.
Can one determine anything from the length or tone of this thread?
Really? Your initial criticism obviously not being enough, you have to insinuate that Geoff’s willingness to engage you and others in open discussion (an unenviable task) is somehow a negative?
Seriously, what is your end goal here? If you think you’re “contributing” - you are, just not in the way you think you are.
- Is Xojo perfect? No.
- Is Geoff perfect? No.
- Is the future success of any software development platform a certainty? No.
So, how is today any different than your 20-year younger self, when you were asking yourself if RB/Xojo was the right choice for you?