
I firmly believe in checks and balances - e.g. Not everyone is a premier service subscriber entitled to a decent response time. But given the average time of responses here, waiting at least 24h for WRI to return with "acknowledged, you will hear from us soon" is simply not an option. I hope not to be the only one suffering from a low tolerance to waiting times.
#Mathematica soundnote pro
Maybe this is, why we have so many visitors from Illinois? :) Pro Bug Reports Here we can have anonymity and meet on neutral, third-party grounds - which is a prerequisite often for openness and honesty. Well, be honest, are there really better places than M.SE?! While to a degree Wolfram Community is decent, it does not match M.SE in quality, speed, and precision imho. While ultimately WRI, of course, will have the definite answer, all of the bug-related questions may well find sensible answers here in that nice and concise way, for which we love SE so much. The community might be interested in the scope of an issue (operating systems) and we may even in our desperation become interested in other tools and languages to provide a solution (not for long, alas).


Then we ask whether there are workarounds or third party packages or whether there are deeper insights and related issues. Q&A are a perfect match for bugs: Firstly, we ask about whether we were too dumb to read and understand the documentation (not necessarily a proof of low IQ.). And lengthy discussions automatically open such a room.

SE's main interest is to make money from its users and their knowledge - pardon me :), is to prevent discussions from spoiling concise and useful Q&A to build a knowledge base. And further more, seeing the issue pop up here will maybe serve as a reminder for me to report the long-forgotten issue myself.Ĭertainly discussions do not fit SE, but they are far from being banned. Then the dead-end threat will be minimized because not seeing a case number eventually will make me file a report to be sure. Clearly using bugs should be a "call of civil duty" to file a report at the same time or even earlier and to provide that information clearly visible for all. While this clearly is a danger, keeping people from repeatedly posting an issue is also a chance (we'll be getting there with the Pros).
#Mathematica soundnote professional
Also they often might get closed due to "technical issue for WRI or professional help". SE-incompatibility By leading to lengthy and controversial discussions they are not a good fit for the Q&A-rules of SE.

I see these three reasons given against bug reporting on M.SE:īy reporting bugs here, they never reach WRI and users will get lazy to report them, since they feel M.SE to be a viable substitute for the "real thing". There are reasons pro and con having bug reports here on M.SE and I would like to start with the obvious cons. Given the way the March 2018 post of Nasser (169209) has been received (high upvotes, discussion about bugs to be used, close votes because of an essential "WRI technical support issue", chat room accusations and allegations :) ) has triggered my reflection on the accepted answer above, given by would beg to differ with that answer and would like to provide some arguments.
