Ugh. Rant time.

[c4757p]

Why is it that all these damn open source projects insist on making people navigate their stupid internal error management system to report a bug? I should not have to register for an account, sift through a million categories, spend twenty minutes screwing with the search engine trying to find similar bugs, and collect debug files from the program, just to tell them about an obvious, critical parser error (easily reproducible, at that) that should not exist in the first place. If I managed a software project and someone sent me a description of an error like that to my fucking personal inbox titled "FIX IT, BITCH" I'd be grateful to get the information. 

[Bored@Work]

They copied that idea from professional, commercial software. Where you typically have a hard time to find anyone who wants to hear about a bug. And if you find one they ask you to pay a premium before they stuff your bug report into some obscure system, never to be read again.

[c4757p]

An important difference is that many OSS projects like to pull the "stop whining, it's free" card. They they turn around and act like the software should be treated like a real, professional project. Can't have it both ways. If you're going to act like it is anything more than a cool toy, I shouldn't have to go crawling through the innards of your bug tracker because your program decided it doesn't want to open a file it saved thirty seconds ago.

[psycho0815]

Well, stop whining, it's free! 
Seriously though. As a professional software developer, i suppose i can see where they are coming from. Depending on how many bugs are reported every day/week, having them just emailed to you, simply doesn't work. You need some sort of issue-tracking. Off course, ideally all it's complexity would be hidden from the customer.

I think the main problem here is that most oss is written by selfmanaged developers. It simply doesn't occur to them, that some people just want to use their shit instead of constantly fiddle with it.

just my 2cnts

[firewalker]

The bigger problem is bug reports that doesn't help. Bug report from users that don't know what they are doing is in many cases a witch hunt for the developer. The user how is willing to go the process of signing up, searching for similar bugs etc,i s most likely to report a valid bug report that will lead to something fixed.

"The stupid thing doesn't work, please fix it" != a bug report.

Alexander.

[psycho0815]

"The stupid thing doesn't work, please fix it" != a bug report.

"Could you please tell me what exactly isn't working sir?" - "Everything"
"Ok, can you talk me through what you did?" - "Nothing"

Been there, done that.

Most Bugs, can be easily fixed by replacing the user.
So i guess you have a point. But that way some bugs can survive many updates only because it's not bad enough to go to the trouble of reporting it.
And for some users "not bad enough" is actually pretty bad.

Suppose you gotta find a balance somewhere

[HackedFridgeMagnet]

Are you going to name the project?

[Tepe]

Nobody cares about to save the time of the customer/user. Nobody think about the fact that a user is the hole day working with buggy devices.

How much was it you paid for support? 

[Tepe]

Here is it again,  the "stop whining, it's free" card. 

That's because it is basically the only reasonable response to give to somebody who demands something for nothing. 

No, I don't point out a specific project. I just remember the last years and all the time I lost with such things. It is not the fault of one project alone, its just the way the world is spinning around today. Maybe I'm a litle bit grumpy about. 

After three decades in the software field, I am more or less immune to such complaints 

Insisting on making the job more difficult for people who let you use their product without compensation is hardly going to benefit anybody.

[mgronber]

Nobody cares about to save the time of the customer/user. Nobody think about the fact that a user is the hole day working with buggy devices.

How much was it you paid for support? 

Here is it again,  the "stop whining, it's free" card. 

You have to admit that it is quite powerful card and usually its use is justified. Most of the OSS developers make software on their own time and for free. The time that is spent to gratuitous user support is taken from the software development.

You can always hire someone to accept bug reports in your favorite format and to fix the bugs that you want to get fixed. These are benefits of the open source software. So stop whining and pay if free is not good enough for you.

[c4757p]

Are you going to name the project?

KiCad. (Despite the ranting - I was a bit scared that I lost hours and hours of work to the bug, so I was not pleased.... - I really do like it a lot.) It randomly decided to no longer accept a + at the beginning of a net name, and started spitting out obtuse syntax errors on my old files. (The fix is extremely easy, too - if you put quotes around the name manually in the file, it works fine again. They just need to properly escape the names before writing them out. Frankly, having a good bit of programming experience in a past life, I want to know what hack of a programmer would ever write out to a plain text file without escaping the text! That sort of thing is what leads to buffer exploits, privilege escalation and the like.)

You have to admit that it is quite powerful card and usually its use is justified. Most of the OSS developers make software on their own time and for free. The time that is spent to gratuitous user support is taken from the software development.

If projects didn't expect to be treated like professional alternatives it would be a perfectly valid card to play.

Actually, I rather think they ought to offer the program both free and paid, where the paid version comes with additional support beyond what they have now. (At the very least someone to handle bug reports like that.) I'd actually be quite happy to pay for KiCad. I don't just use it because it's free, I actually do like it. They put in a lot of work and deserve some sort of compensation. And I'd love to be able to suggest fixes without having to tame the bug tracker first...

Edit: Holy crap I use parentheses a lot...

[c4757p]

Okay, despite reporting the bug being a pain in the ass, I have to commend them - I reported it last night and a fix was committed this morning. 

[HackedFridgeMagnet]

I reported it last night and a fix was committed this morning.

That's pretty good. The wonders of a small team without management interference.

I use Kicad too, but haven't reported a bug, or haven't gotten around to compiling it either.
Was it a nightly build or a supposedly stable release?

On the other hand I have just be using Altium Reader, (no one I know will pay for my full licence), it's not without it's bugs and UI weirdness either.

[rsjsouza]

My US$0.02...

I work for a company that develops an IDE, and I can tell from my own experience: either with Open Source or proprietary software, a thorough report with a reproducible way to make the bug manifest itself goes a long way to quickly solve any issue. In the case of my company, this is valid for all customers regardless of their size. 

Since the complexity of these software tools increased (with several internal components), the bug reporting system follows suit (developer "A" only sees bugs filed against component "A", and so on) - in several cases it turns out that very few people actually have complete visibility of ALL the bugs submitted.

Since everybody is usually pressed by time and resources (including the software manufacturer), the customers and the developers naturally end up filtering nuisances and only reporting critical stuff. Of course, there are always the "low hanging fruits" that have an easy way to reproduce and a quick fix.

On the other end, the number of reports that say "don't work, it is a bug" are massive, and the software manufacturer can't really do anything without details. That is why some of the bugs linger for several versions.

Other bugs are simply too hard to pinpoint the exact reason, or are heavily dependent on the customer's OS, third-party software (antiviruses are famous for interfering with no-mainstream software) and sometimes even the PC's hardware (mostly USB if using emulators).

[c4757p]

On the other hand I have just be using Altium Reader, (no one I know will pay for my full licence), it's not without it's bugs and UI weirdness either.

Seems like all of the schematic/PCB packages are steaming turds. Some just don't smell as bad as the others...

and then another whining thread will appear. "why they get it for free? (the fixed version) while i pay for the support and bugs fix? - bummer (to the other people who dont care about support)"

Because you care about support and they don't, and the programmers choose to make it available to them. It's that simple. To them I say "shut up!"

My US$0.02...

I know, many error reports are useless and requiring them to be properly detailed helps filter those out. Some bugs are really hard to track down. I just wish there were a way to tell people about easy bugs like "file-save should put quotes around names". I guess it might not really be possible to filter out the crap, though 

[rsjsouza]

I just wish there were a way to tell people about easy bugs like "file-save should put quotes around names

I feel your pain... In my case there is no easy way: customers don't file bugs. We file all of them, but only after the customers provide full details and we reproduce them in our own systems. This helps to filter out all the crazy stuff and quickly fix the low hanging fruits ("put the damn quotes on filenames" type of bug), but at the expense of man hours - something harder to materialize in the open source community (not everywhere, though, as you can attest by the quick fix to your report).
 

[c4757p]

I must confess that most of my rantiness (yeah, it's a word - suck on it, spell check) was a product of my "holy shit all my work is gone" fear - which was entirely my fault for doing real work on a nightly. I stand by my desire for better error reporting, though I realize it's not as simple as "just fucking fix the error reporting system now, goddammit"...

I also stand by my "what god-awful programmer would even think about writing raw string values out to a file without escaping them first??". And I'm a bit peeved that the solution they implemented was not to fix the saving of the values, but to accept raw values containing numbers - especially considering whatever input parser they're using already seems to understand quotation marks. God only knows what else it will let you type into a net name that it won't be able to read back. I suppose instead of just submitting an error report I should have submitted a patch - I am more than capable.

[HackedFridgeMagnet]

I also stand by my "what god-awful programmer would even think about writing raw string values out to a file without escaping them first??"

Having done plenty of "escaping" myself, I have to agree with you here. Any data written to text file needs to have escaping done on it otherwise it's just a random string and not organised data. As such all such data exported should go out through the same WriteDataToFile function that the developers had got right in version 1.
I know most people hate XML but at least developers remember it needs to be escaped.

Don't worry about the rant everyone has them and I myself find them quite therapeutic.

[rsjsouza]

the problem with open source (probably) is... people do it for fun during their freetime or just to fullfill their need.

All the open source projects started this way but, as you mentioned, the successful ones required a significant amount of time (years, not months or days) from the original developers until they reach a critical mass of knowledgeable people. By then the "community" is doing a significant amount of development and bug fixes (at the same time the "stop whining card" starts to develop), but it still requires some management that approves patches and new features; something simlar to what happens to Wikipedia. Without this management, the project becomes a headless chicken and therefore impractical.

once payment is involved from users, they need to make it more "professional", means to satisfy "all" users need (which is impossible even in enterprised paid proffesional'ed softwares), i dont think the OD will bother since they have another job that probably secures them better. in that case... you are on your own.

Hehehe... Not only it is impossible to satisfy ALL users' needs but also to fix ALL the bugs...

Despite all this, nowadays several large Open Source projects (Linux, GCC, etc.) have professionals working on them, or companies that sponsor certain porting efforts or sponsor the project during a given amount of time.

I must confess that most of my rantiness (yeah, it's a word - suck on it, spell check)

Love it! Rant on an inflection of the word rant... This makes sqr(Rant); or Rant²

And I'm a bit peeved that the solution they implemented was not to fix the saving of the values, but to accept raw values containing numbers - especially considering whatever input parser they're using already seems to understand quotation marks.

I agree with you... It looks like a half-baked solution for the problem.

[psycho0815]

And I'm a bit peeved that the solution they implemented was not to fix the saving of the values, but to accept raw values containing numbers

Agreed, that seems a bit quick'n'dirty. Problem is if you fix the saving of the values, it still won't load the files that have already been saved with the faulty quotation. You'd have to write some sort of converter, that loads the file, identifies the places with missing escaping and fixes them, without breaking the actual layout obviously. Or provide some kind of fallback-mode that accepts raw input if normal loading doesn't work. Not sure how much effort that would be, i never looked at the codebase. (Also C/C++ is not normally my language of choice).

So i can see why they choose to do it that way for now. Hopefully they'll do a proper fix in a later version.

[c4757p]

Problem is if you fix the saving of the values, it still won't load the files that have already been saved with the faulty quotation.

I think what I'd like to see is a better "unstable" line in addition to stable and nightly. I'm using nightly because it has some cool new features, which actually do work. The file save problem is due to them being in the middle of a file format switch. What I'd like is a code branch that gets all the new features pushed to it as soon as they work, but doesn't contain the half-finished ones like the new format. They only need to worry about backwards compatibility to the last stable release, which it doesn't have a problem with. I wouldn't expect backwards compatibility to be maintained across two nightlies.

[free_electron]

I just wish there were a way to tell people about easy bugs like "file-save should put quotes around names".

that is programmer stupidity.

it's a matter of writing robust i/o code. there are ton's of libraries that already do that crap for you. filter out illegal characters, deal with long file names , split parameter strings etc. USE THEM !

ANY kind of input , wheter coming form a text field, file or i/o interface needs to be 'sanitized'.
in case of filenames : if you detect a space in the string : remove any existing quote marks and re-wrap in quote marks. scan for illegal characters ( so people can't force os commands through the file filter. etc etc

[codeboy2k]

ANY kind of input , wheter coming form a text field, file or i/o interface needs to be 'sanitized'.
in case of filenames : if you detect a space in the string : remove any existing quote marks and re-wrap in quote marks. scan for illegal characters ( so people can't force os commands through the file filter. etc etc

agreed.  The problem with today's kids is that they are re-learning all the same old mistakes over and over again.
Anyone who grew up on Usenet has seen all the robustness of the software that defined the "Internet" back then.

We've seen all the exploits fixed, all the good programming practices adhered to, and we all learned what not to do when writing code.

Today, it's Ajax/JSON/HTML/SQL/PHP, etc and all these technologies are being re-exploited because the new kids are writing the same old bad code, and creating the same old problems we already fixed once.  They write code, but they aren't thinking.

Now, none of what I just said has anything to do with reading data from a file. But as FE said, it's the most basic of all things. Sanitize the input stream, especially if it is an original source that might have been modified by an end user, as Kicad's text files are.

Kicad itself doesn't even follow any of the most basic usability and workflow paradigms that came before it, as most every other capture and PCB program does. It's just a beast to work with.

(yeah I know, quit whining, it's free )

[HackedFridgeMagnet]

Kicad itself doesn't even follow any of the most basic usability and workflow paradigms that came before it, as most every other capture and PCB program does. It's just a beast to work with.

That is so not true, I found it easier to use than Eagle. Also I got a non engineer guy to layout his first ever board using it, 2 layer, just dip profile and maybe 40-50 components.
And he did it reasonably quickly with only a couple of queries, I had to help him with the DRC errors and track widths.

He followed the tutorials and he was a programmer by trade.

I have more trouble with Adobe Reader usability than I do with Kicad.

[Bored@Work]

They write code, but they aren't thinking.

That, and they aren't listening. The kids invent one rubbish programming language (python, php, JavaScript ...) after the other, "invent" one rubbish technology after the other (Ajax, Flash, ...), and redo every single mistake of the past. They don't even invent their own mistakes, they just do the old mistakes over and over again.

When you tell them they don't listen.

There is an example in some other thread. Someone is asking if version control is really needed. 30 years after it is an established proven technology. I have given up trying to educate such idiots. These days I am fortunately in a position that I can refuse to work with people who don't do version control. I have fired subcontractors on the spot who refused to do it, or refuse to do it properly (no, a bulk check-in, of course without merging, every second week is not proper ...). They don't listen, so there the job goes.