[NUG] *Re: API 2.0

[Norman Palardy]

> On Mar 14, 2019, at 7:58 AM, Jon Ogden via Nug <nug at xojousers.com> wrote:
> 
> My point exactly.  I had filed a bug report and it’s probably still open or closed as unreproducible.  The big gripe of most users is that instead of fixing things, Xojo just keeps going ahead and adding more stuff or changing stuff.  Take Serial Ports there’s a status bug with them as reported here: <feedback://showreport?report_id=14952>  In face the mailer doesn’t format Feedback links right it is case 14952.  This has been verified since 2015.  Verified.  Means that Xojo reproduced the bug.

No
It means "this behaves as described"
Verified isn't "Verified this is a bug"
Those statuses aren't clear in that regard and this is a constant source of pain and conflict internally and externally
It would be nice to have that status say "Verified this behaves as stated" or something much more complete and then extra statuses for "verified as a bug" or something

>  But it’s 4 years later and it’s not done.  And actually the first report of this was in 2010!!!

I honestly dont know why they ever did what they did with the baud rates turning them into numeric constants that arent just the baud rates themselves
That would have made more sense

> So why not FIX stuff first then move on instead of compounding error on top of error.

Fixes dont sell new versions.
In most fields getting people's attention is driven by big new features - and a long list of bug fixes doesn't get a lot of attention.
Its hard to get any of the news sites to mention a release that is a long list of bug fixes.

Basically bug fixes releases don't affect the revenue model and so they aren't common