I got the impression that there are certain words (among them "buggy", "bloated", "unintelligent" and "dumb") that cause a post (like this one) appear as rant to the eyes of many. Is there a central list or some kind of general rule or is it left to personal discrimination?
I think the way I see it is simple. Get to the point about what is not working. Don't beat around the bush about explaining how much you hate something. There are no specific words that would describe a rant. People (most of them anyways) know it when someone is whining about something.
If you have a problem with some product, describe the problem exactly as it happened. Don't start describing how much you hate the product because of that particular problem you had.
Even if that problem caused you so much stress. Sorry, we are not interested to know about it.
We are here to solve programming problems. So, provide the exact problem. No more and no less.
We are not interested to know whether you loathe or worship a product.
If you loathe about a product, please keep it to yourself or vent about it on some other site.
Product x failed to do what I want to do, what should I do?
That's how I look at it.
If I may post your question, this is how I would do it:
I am trying to understand how PhpStorm works but have been facing some difficulties. I am using the final version downloaded from JetBrains and my project is a fork of FengOffice. My environment includes common
LAMP stack on
Ubuntu 11.04 (
When I press Ctrl + N in PhpStorm, I am able to view all classes. However when I try to instantiate a class, all the classes are not displayed.
When I try to invoke auto-complete on an object variable $anew SomeClass(), I am able to view language constructs
if, endif, while; superblobals
$_GET, $_PUT. Pressing Enter key actually inserts the code
Is that the normal behavior of PhpStorm where it doesn't display all the classes or am I doing something wrong?
I believe that I didn't alter the meaning of your question.
I try to be humble and I don't bash something because I can't figure out how it works. It is a lack of knowledge on my part that I don't understand the product thoroughly. I can't buy a Semi-trailer truck and drive to office and say it gives horrible mpg driving it every day to office. You got to understand what the use of Semi-trailer truck is, it is not for every day office commute. (Maybe it's a poor analogy.) The point is that you need to understand the limitations and look at it the positive way. Sure, there are bad products, I don't deny that fact--but it may be that you just picked the wrong product for your particular job.
Anyways, that's the way I am.
I believe this is an open problem. There is an interesting article available here. It in essence boils down to detecting sarcasm within English text and human users tend to be the best at it. Context is everything.
That said, the Stack Exchange network is specifically designed and policed to be a question and answer knowledgebase. If a question appears to convey a -- positive or negative -- opinion then it is often flagged. Often, many of these questions can be rewritten to focus on a specific sub-issue which will be on topic and solicit cogent answers.
Unfortunately, the majority of people don't like to see anything that is
"negative" even when it's accurate. They like to refer to
features, and want to tell you to just buck up and accept it. It's one of the reasons there are so many bugs in software out there, denial is not just a river in Egypt. So when you identify a problem AND call it that, they freak out on the negative vibes.
Some of us just like to fix problems, and you can't fix a problem until you recognize that there is one.