Skip to main content
added 203 characters in body
Source Link
muru
  • 204k
  • 2
  • 41
  • 67

IMO these should be closed for multiple reasons:

  • consumer hardware changes too quickly and has too many minor variations for the answers to have any lasting value. Same problem with shopping recommendations.
  • the answers are far going to be far too opinion-based. One user's priorities need not be the same as another's.
  • the question is far too broad. If a system has problems with graphics and with networking and with touchpads and ... these are all problems that should be asked and answered separately, because each individual component is likely to be more commonly used than the device as a whole.
  • I feel such questions would also involve a lot more back-and-forth discussion and essentially become a request for on-going support. Keep that to chat, please.

Such questions can be answered well by users with experience of the hardware in question.

Not from my POV. What if the user with experience tried 16.04 and asker wants to use 14.04? What if it's the other way around? What if the asker is worried about WiFi and the answerer only ever uses ethernet? What if the asker is interested in gaming and the user only does CUDA? For a useful answer, the asker and answerer's usage has to align, more than with any other topic seen on our site.


Experience with a device is good material for a blog post or a review site. Not for Q&A.


I have a tried to post a broad-strokes Q&A about this: Will my device work with Ubuntu? It's community wiki, thus easier to contribute to for many users. Let's see what can be made of it.

IMO these should be closed for multiple reasons:

  • consumer hardware changes too quickly and has too many minor variations for the answers to have any lasting value. Same problem with shopping recommendations.
  • the answers are far going to be far too opinion-based. One user's priorities need not be the same as another's.
  • the question is far too broad. If a system has problems with graphics and with networking and with touchpads and ... these are all problems that should be asked and answered separately, because each individual component is likely to be more commonly used than the device as a whole.
  • I feel such questions would also involve a lot more back-and-forth discussion and essentially become a request for on-going support. Keep that to chat, please.

Such questions can be answered well by users with experience of the hardware in question.

Not from my POV. What if the user with experience tried 16.04 and asker wants to use 14.04? What if it's the other way around? What if the asker is worried about WiFi and the answerer only ever uses ethernet? What if the asker is interested in gaming and the user only does CUDA? For a useful answer, the asker and answerer's usage has to align, more than with any other topic seen on our site.


Experience with a device is good material for a blog post or a review site. Not for Q&A.

IMO these should be closed for multiple reasons:

  • consumer hardware changes too quickly and has too many minor variations for the answers to have any lasting value. Same problem with shopping recommendations.
  • the answers are far going to be far too opinion-based. One user's priorities need not be the same as another's.
  • the question is far too broad. If a system has problems with graphics and with networking and with touchpads and ... these are all problems that should be asked and answered separately, because each individual component is likely to be more commonly used than the device as a whole.
  • I feel such questions would also involve a lot more back-and-forth discussion and essentially become a request for on-going support. Keep that to chat, please.

Such questions can be answered well by users with experience of the hardware in question.

Not from my POV. What if the user with experience tried 16.04 and asker wants to use 14.04? What if it's the other way around? What if the asker is worried about WiFi and the answerer only ever uses ethernet? What if the asker is interested in gaming and the user only does CUDA? For a useful answer, the asker and answerer's usage has to align, more than with any other topic seen on our site.


Experience with a device is good material for a blog post or a review site. Not for Q&A.


I have a tried to post a broad-strokes Q&A about this: Will my device work with Ubuntu? It's community wiki, thus easier to contribute to for many users. Let's see what can be made of it.

Source Link
muru
  • 204k
  • 2
  • 41
  • 67

IMO these should be closed for multiple reasons:

  • consumer hardware changes too quickly and has too many minor variations for the answers to have any lasting value. Same problem with shopping recommendations.
  • the answers are far going to be far too opinion-based. One user's priorities need not be the same as another's.
  • the question is far too broad. If a system has problems with graphics and with networking and with touchpads and ... these are all problems that should be asked and answered separately, because each individual component is likely to be more commonly used than the device as a whole.
  • I feel such questions would also involve a lot more back-and-forth discussion and essentially become a request for on-going support. Keep that to chat, please.

Such questions can be answered well by users with experience of the hardware in question.

Not from my POV. What if the user with experience tried 16.04 and asker wants to use 14.04? What if it's the other way around? What if the asker is worried about WiFi and the answerer only ever uses ethernet? What if the asker is interested in gaming and the user only does CUDA? For a useful answer, the asker and answerer's usage has to align, more than with any other topic seen on our site.


Experience with a device is good material for a blog post or a review site. Not for Q&A.