Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker for Windows won't run if Razer Synapse driver management tool is running

twitter.com

Post reply on HN
Print view View original

61–70 of 191 posts

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#61

Post by Jare »

moomin wrote: post #56
jordansmithnz wrote: post #6

Ha, stackoverflow is a great tool, but... the more answers I see on an area I’m experienced in, the more I realize how wrong they can be. Sure, the answer usually gets the job done, but everything else about it might not be right. If I need to use stackoverflow, these days I make sure I do a few things: - read a number of answers, comments included. Just because an answer is accepted doesn’t mean it’s the best one -…

I'll suggest one more addition to this (and any code you take from the internet): put a comment in saying where you got the idea from (with a link). It can help the next guy out a lot. And you might be the next guy.

This is huge and has saved me a few times already when I became my own "next guy"

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#62

Post by mrweasel »

SteveSmith16384 wrote: post #54
bitwize wrote: post #46

Earlier quoted context omitted.

But what if the docs suck, as is the case with a lot of .io domain libraries?

And anything MS?

Microsoft have best most fascinating documentation in some cases. It can be fantastically detailed, while being completely useless at the same time.

Take their Azure Python API, which is clearly translated directly from C#: There's a number of functions, which according to the documentation takes a string as an input. The thing is that it won't actually take a string, it will take three or four predefined strings. Everything else will yield no result. The only thing Microsoft doesn't care to put in the documentation is which strings are actually valid and what result you can expect from them.

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#63

Post by baud147258 »

SifJar wrote: post #25
CJefferson wrote: post #24

Earlier quoted context omitted.

The problem is stackoverflow seems designed to avoid "better answers". Questions are often long abandoned, and the original questioner won't come back and choose a new correct answer. On a rarely looked at question, it would take years for a correct answer to raise up the ranks. I've seen various answers which used cryptography dangerously, and asked if there was any way they could be fixed, and I just got the answer…

It's worth noting that it is possible to edit other people's answers. So it is possible to correct answers with incorrect or dangerous information. With sufficient "rep" (2000, where an upvote on one of your questions or answers is worth 10), edits don't even require approval from others (before that, they must be peer reviewed before the edit takes effect)

Personally I find the "edit without peer review" too powerful, since you can do it for any question, regardless if you're supposed to be competent there or not; it would be better if it was limited for tags where you've got a bronze badge. Perhaps it's the lack of oversight which makes me a little wary. And 2000 rep isn't that hard to achieve, it just requires some persistence.

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#64

Post by Jare »

fctorial wrote: post #49
bitwize wrote: post #46

Earlier quoted context omitted.

But what if the docs suck, as is the case with a lot of .io domain libraries?

Is the io prefix somehow related to software tech?

It is often used for the following (that I have seen - may be others):

- open source libraries - online casual browser games - development/staging environment counterpart to a .com

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#65

Post by chrisoverzero »

kstenerud wrote: post #10

> homework assignment for all programmers reading this thread: Think about how you'd find this bug in your own programs. You copy/paste the code, it seems to work, and you don't realize it's broken because you don't run either of these programs which made the same mistake. Wait... WHAT?? Who the hell copy pastes code into their program without first examining and understanding what each step is actually doing, how an…

>Who the hell copy pastes code into their program without […]

The developers of Docker for Windows and the Razor Synapse driver management tool. Among others.

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#66

Post by mdszy »

_-___________-_ wrote: post #2

If you're going to copy-paste code from Stack Overflow and deploy it to millions of users' systems, I think you have some responsibility to understand what the code is doing. I can totally see how this happened, and I would definitely not say that I would never make this mistake, especially under time pressure etc. But a careful programmer would a) desire to understand what the code did, and thus spend enough time re…

How many times have you run `npm install` or used literally any programming package management system without personally reading every line of code that you're installing?

Re: Docker for Windows won't run if Razer Synapse driver management tool is running

#70

Post by inetknght »

moomin wrote: post #56
jordansmithnz wrote: post #6

Ha, stackoverflow is a great tool, but... the more answers I see on an area I’m experienced in, the more I realize how wrong they can be. Sure, the answer usually gets the job done, but everything else about it might not be right. If I need to use stackoverflow, these days I make sure I do a few things: - read a number of answers, comments included. Just because an answer is accepted doesn’t mean it’s the best one -…

I'll suggest one more addition to this (and any code you take from the internet): put a comment in saying where you got the idea from (with a link). It can help the next guy out a lot. And you might be the next guy.

Especially if it's not a copy-paste job. If there's any adjustments or even a rewrite, the comment should include the reason why the changes were made. The next guy coming along might not realize that changes were needed
Post reply on HN