Desktop is still by far the most OK of them all
I wish they’d focus more on fixing bugs & less on renaming things
3 Likes
It is the most OK, but the problem is that is getting way outdated and without mayor new functionality that is standard this days, many many time wasted on reanmings and half backed new targets. 
2 Likes
Which is exactly how I feel, and even told the Xojo team directly. Renaming things has been so destructive to the enthusiast segment of their market.
Like yesterday I found a bug in API 1 object, try API 2, they fixed the bug there, then realize that the API 2 object is not a swap in job. I have 1000s of database records that are incompatible with this object, unless I waste CPU cycles in converting the data so it can be used with the API 2.0 object. That is after I’ve converted my entire project over to using this object, just to get one bug fixed.
Makes me really angry. To fix a bug, I have rewrite chunks of my project and add code that’s going to slow down my application. I WANT MORE SPEED, NOT LESS.
1 Like
and everytime YOU have to refactor your code to compensate or become compliant with some stupid API2 change, YOU run the risk of introducing new bugs of your own, or at the very least need to do an extensive unit/regression test to insure it still does what you intended… Total waste of time, with next to zero net benefit.
3 Likes
Could you say what that was? I’ve stayed on API 1. Is the bug in API 1 back to 2019r1.1 or was it introduced more recently?
-Karen
Many of them you can also produce cause of the leaky and unprofessional handled documentation. All older Docs are erased from Xojo Servers at the moment a new Version is out. That makes it sometimes a bit complex. Even if you say that the docs are available in the Xojo IDE. The Docs in IDE are never corrected within the same version. Means: Bugs in docs are corrected sometimes Online but not in the Offline Help. Changing to a new version makes use of the old version - more or less - impossible.
A short look on another language shows us how to handle that: Java. Oracle provides the docs of Java Versions back to Java 7 directly online as html docs, before there was not html as doc format so oracle provides them as download. Since Java 7 released in 2011 it is even back more time than Xojo is named Xojo. Dangerous.
I don’t want new language features. I can probably count on one hand the number of new features introduced since RealStudio that I actually use or need.
I also don’t have any show-stopping bugs preventing me from writing apps to do what I need them to do.
But I’ve stopped renewing my license until such time that they start fixing all the stupid sh*t in the IDE that Xojo ruined. Geoff told me two years ago “Don’t worry, we all see the IDE problems and they will be addressed in time”, but AFAIK there has been zero progress.
6 Likes
Let’s hope so. My experience is that I think it does what I want it to do, until I find that sometimes it doesn’t - because there are bugs in the underlying framework (eg 32bit overflows in the 64bit system). In my opinion the whole framework needs a serious health check by someone competent but instead they just muck around the edges …
Remember, they are, and have always been, ‘adequately staffed’.
To which I have always said, “bulls*t!” There are too few developers doing too many things. Instead of a team effort it’s mostly individual effort. Individuals make poor decisions all the time that a group will (hopefully) find and correct. I doubt they do proper code reviews and pull requests. I also doubt they do proper training for new developers before they’re allowed to commit to a release branch.
8 Likes
biting tongue
What’s a two word definition of “confirmation”?
uhmmmmm
I’ll take bitting tongue for $1000 Alex
I think that sums up Xojo Inc very well