Xojos bug tracking system

I dont know how PHP’s process works to deal with bugs in it
Or how JetBrains prioritizes things in their IDE’s
(nor Java nor MS etc)

What I CAN say is that in JetBrains Rider, VS for Mac (yes despite being defunct it still gets updates periodically), VS Code, I have yet to run into a show stopper issue in their IDE’s or the framework code.

I HAVE run into bugs. Rarely. (VS was maybe the worst since it WAS only a beta product)
But even those were fixed rapidly

and NOTHING in the frameworks apps made in them rely on

THAT sort of reliability is whats missing from Xojo
Nothing like

Val from “-1” to UInt32 produces different result on mac Intel to mac ARM

Passing an array of structs to plugin code results in OutOfBounds on ARM builds.

Those simply demonstrate a lack testing to see the compiler generates the SAME output on each target

THAT doesnt increase anyones ability to think of Xojo as a reliable platform

1 Like

No idea and I don’t care since I haven’t run into a bug yet.

Shouldn’t need to poke and prod into the Xojo Bug Black Box just to learn how to get a bug fixed.

THIS :point_up_2:

1 Like

Not to run into Xojo bugs is an independent form of arts :slight_smile:

3 Likes

kind of kicks a hole in How do we decide what goes into Xojo? – Xojo Programming Blog

It impacts EVERY user that makes web projects (significant surface)
Has NO workaround that doesnt result in a jarring experience

Kicked down the road 8 times already

1 Like

I fix this for you: It impacts every professional user…
or in the words of the genius: “Ahh a Professional here… won’t fix, next!”

3 Likes

New release, new bugs.

1 Like

For years I told him to write their website/ license system / xojocloud control panel in Xojo. It seems so damn obvious. – Geoffs response? He told me a story about Steve Jobs.

4 Likes

deflect. defend. deny.

Why am I not surprised ?

2 Likes

He gifted Xojo hobby devs with DBKit :rofl: :joy: :sweat_smile:

DBKit is what? Garbage? Crap? Looking on similar tools in the java edge and also in the C# edge I am asking my self: is it worth of handling ll this f.ck.p with Xojo? In my eyes no.

Imagine if Geoff did something like WebAwesome and get feedback from devs…

2 Likes

That HAS to be the best example of German humour I’ve ever seen !

I owe that man a beer next time I’m there

1 Like

I always thought them doing consulting projects in Xojo would a) be a revenue stream and b) improve the product immensely since they’d find more edge cases and fix them quickly (because the consulting projects would require them). But WTF do I know, eh?

2 Likes

Apparently about as much as I do
I figured exactly the same and suggested it more than once
I wanted to do on-site training. More or less what Geoff used to do for 4D.

I figured he’d have some insight into how lucrative that could be.

Consulting would have had their own people using the product in a much broader way than they do. It would have been well Beyond Eddies example project. And building the IDE doesn’t stretch Xojo’s usage in many areas. Many arent used at all ( Reports for instance)

As well doing training would have pushed them to improve in areas where their own people found issues, bugs & shortcomings while doing training.

It went no where
No idea why not
It just didnt

Lead a horse to water & all that
:man_shrugging:

3 Likes

All those things that would make Xojo better are a cost that Geoff doesn’t seem to want to pay.

It’s cheaper to not do any of it. I think that’s where the we’re not NASA nonsense comes in.

2 Likes

theres a cost to doing stuff - sure
theres a cost to NOT doing it as well - lost sales & revenue

the NASA thing is a straw man
no one expects NASA level of code quality or PERFECT
just BETTER each release and improving in terms of fewer bugs released into the wild each release would be AWESOME !
from what I tracked it pretty much flat lined and wasnt showing signs of improvement

THATS the problem

Instead “because it would be hugely expensive” they do what seems to amount to nothing to improve their processes
That was probably the biggest issue when I was there - several devs did things on their own to improve processes. But it wasn’t systemic or required
And losing those devs they seem to have lost all that

2 Likes

…at least they tried it with the native bug reporting app.

And failed because of “not invented here” syndrome and the unwillingness and unability to cope with open standards.

true words…

Interesting that no one on the Xojo forums are talking about the newly introduced bugs in the bug thread.

Has there been a discussion about how the new bugs were introduced?