NI: please fix long standing bugs before creating more features

[MGiacomet]

Would be nice if NI would concentrate on fixing long standing bugs instead of creating new features dreamed by marketing...

There are threads in the forum about bugs that have been going on for 4-5 years! Ouch! They are there and it is not an excuse to say "we can't reproduce". Some bugs (intermittent or the type "we can't reproduce", have to be fixed by analysis, not by single stepping through the code. If one can't reproduce in the "clean lab" environment, analysis of the existing code is needed to find what could be causing the problem by the Customers.

We all experience them, don't we? So they are out there...

[Intaris]

MGiacomet:

Do you really think the Firefox programmers don't take user wishes seriously? Firefox isn't freeware, it's open source.  It's not the same thing.  Free software (Software Libre) is not freeware.  Freeware is generally closed-source.

I'm pretty sure a lot of the Firefox development team are more talented and dedicated programmes than I will ever be.  Doubting their committment to quality based on the end price you are asked to pay is extremely short-sighted.

[Yamaeda]

That's basically what they've done since LV2011.

[X.]

One of the problem with the LabVIEW model (shared with many other software products) is that bug fixes are not applying to older versions. So, to benefit from a bug fix, the bug being a major irritation for your GUI, you need to shell out for the new version. The model is additionally annual, or to some extant semiannual, contrary to models such as those used for modern browsers, which means that even if you are willing to pay to upgrade to the newest version, this is not going to happen soon. Adobe has opted for yet a different model, in which you subscribe annually and get fixes and new features as they come (somewhat similar to the browser model, but for a fee). Not sure wether this one works so well however (especially when it is cloud based and servers crash).

In other words, if you are NOT interested in the new features, but hear about a bug who is ruining your life being fixed in the new version, you are in practice paying for bug fixes. Also, some important bug fix (from a personal point of view) would sometimes be better than many minor features which turn out to be buggy themselves (I am thinking about subdiagram labels and label arrows in 2013, for instance).

Even though I upgrade regularly (cost being a minor issue due to my academic status), I'd say I'd be happy to pay for fixing bugs that annoy me. Heck, I would even pay for a bug reporting and tracking system!

NI developers, send me a private message if you want to work on my pet bugs. I am open to reasonable bribe requests. I'll then go to some quickstarter website and gather the requested money (in fact I am thinking of suggesting a dedicated subforum to the NI forum for that purpose).

[Intaris]

Why don't we have a Bugfix Exchange where we can vote on which CARs get handled next......

Kudos is coupled with a PayPal account.......

I'd better stop before NI marketing hears me.

[JÞB]

 I've never met any software team that can fund their ongoing bug fixing efforts without providing new features to keep users coming back-AQ

So, What percetage does you company charge for "Bug" Fixes... And,  what exactly is the timeframe?  Does X do bug fixes gratis for 30 or 40 years?

Yup, Busting on X again!  Of course, I have never paid for X products.... Where do I send the check?  (Whoops----STOP)

Oh,, you can select any sig line on any one of my posts X,   Deliver an address to who or what do you do that writes bug-free code! I would like to learn that system! (Trust me,  If there is a way, I WILL happilly learn it)

[ouadji]

just my opinion

for me, it is the only downside about Labview, Ni is too slow to fix bugs.

I've never met any software team that can fund their ongoing bug fixing efforts without providing new features to keep users coming back

I completely agree ... (200%)

but this does not prevent to fixing bugs at the same time.

Fixing bugs should be a priority. Some bugs are several years old ... it's incredible. (and annoy users)

[AristosQueue (NI)]

ouadji: Fixing bugs is a priority. Despite being a prioirty, there are many bugs that are many years old. And there will continue to be as long as "number of developers" is a finite quantity.

[jcarmody]

I had trouble with LabVIEW 2012 crashing almost every day.  That went away with LabVIEW 2013, but building installers immediately went from short to very long.  Perhaps LabVIEW 2104 won't crash and will build faster?  That'd be great.  My point is that the bugs I notice go away eventually.  I know you folks are using the more advanced features in LabVIEW, what issues are the thorniest?

[Darren]

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.