<Some question about design or product>
What are the pros and cons?
Sometimes, these questions get closed as 'too broad' or 'primarily opinion'. Why is that?
When I worked as a freelancer, I encountered lots of cases where customers were protecting their ideas and source code of their projects (such as web applications) as much as possible, no matter how unimportant, uninteresting and unoriginal were the projects and the concepts behind.
I've already...
To add to what @DavidMakogon said, you can try posting at programmers.stackexchange.com, opinion based questions are ok there. — Stefan Monov48 secs ago
@Rachel Well, almost. We're deflecting licensing questions to the new OpenSource SE, which can handle them much better than we can.
Indirect ("As a programmer") questions, such as education questions and worker interaction questions, are now fielded on The Workplace, though that has happened for some time now.
But you're right. The new scope declaration is mostly a clarification, not a change.
As long as we're using the paint can analogy, many software projects create their own paint can factories and fill the cans with various colors of paint using another factory in another town. It's true that the paint costs $100 for the factories to create, but the factories themselves cost $1,000,000 to make. There are observers to make sure the paint is the right color, and while the paint can factory knows about the paint factory, the reverse isn't true. — Robert Harvey4 mins ago
<Some question about design or product>
What are the pros and cons?
Sometimes, these questions get closed as 'too broad' or 'primarily opinion'. Why is that?
The Whiteboard
The Whiteboard