Re:Turning Off GitHub Issues (2016)
by BugsJustFindMe on Tuesday May 23, 2017 @06:19PM
(#14405884)
> You're being sarcastic, right? This is OS. It's fundamental underpinning is that if you want to use it (or at least engage its maintainers), you have to care.
Ugh.
My partner, who doesn't know the first thing about code, understands the value of FOSS. Caring about FOSS doesn't fix bugs.
A month ago (more?) I encountered a bug in LibreOffice Writer, which I use because it's really good, where track changes on a docx file wasn't working properly in a particular situation involving the deletion of tracked comments across saves.
QUICK! Find the line of code that caused it! Find the mechanism for creating a test case! I'll wait here.
Back here in the real world I was able to report the bug and have it fixed by someone who knows what the code does.
You're confusing an application versus an API which is what this thread was about.
You can't really compare a huge end-user product to a developer library though. Developers are supposed to be able to write code.
Re:Turning Off GitHub Issues (2016)
by BugsJustFindMe on Tuesday May 23, 2017 @06:47PM
(#14406076)
The world isn't all NPM left-pad modules. Code is arbitrarily complex.
There are libraries that are as complex as a large end-user product.
Re:Turning Off GitHub Issues (2016)
by yjftsjthsd-h on Tuesday May 23, 2017 @11:38PM
(#14407446)
Don't stop there: plenty of libraries are more complex than the applications using them. More complex, more general, used by more people. I mean, just libc and curl probably dwarf most applications that consume them.
That being said, maybe there could be a "found problem, not sure is a bug" flag that defaults to on. Or a warning dialog that says "without example code or detailed repro, this issue probably won't be looked at."