Live data from Hacker News

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

twitter.com

141–150 of 191 posts

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

#141

Earlier quoted context omitted.

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. Ev…

microsoft's documentation for anything other than .NET stuff is absurdly bad. i was trying to do some work with their crm solution it took me a literal week to find out how to do simple oauth -- mostly because 99% of the documentation only had .NET examples using their own framework!

Microsoft's documentation for .NET is also absurdly bad.

No, I don't want to do a full reload for every overload of a method. Yes, I might want to see where these extension methods are popping up from, out of nowhere.

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

#142

So with tools like Sonarqube we get static code analysis on our code base which shows code duplication within itself. I wonder if there is some way to look for duplication from stack overflow? Not sure that is feasible, since no one is going to want to post all of their proprietary code to some API, but wonder if there is some system for local indexing SO that would also for local duplication detection.

StackExchange data dumps are (at least, were[1]) freely downloadable: https://meta.stackexchange.com/questions/2677/database-schem... [1] not sure what happens since they "illegally" retrospectively relicensed all the content a few months ago.

Yeah I thought they had something like that. Might be interesting to play with. I meant more of a question as to if anyone had actually done something like that with it. Basically a Turn It In kind of tool that universities use for plagiarism detection, but for code.

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

#143
post #73

Earlier quoted context omitted.

And anything MS?

Microsoft documentation was historically the gold standard for comprehensiveness and quality. If what the other commenter says (e.g. about their Azure docs) is true, I don't know if things have changed or what. Maybe a post-Nadella culture shift?

I guess people's expectations might have been lower? MSDN sucks along every axis I can imagine.

The content is bad: Quick, is System.DateTime[0] timezone-aware? The examples also use (the harmful and bug-prone) DateTime.Now 5 times, while DateTime.UtcNow is only mentioned once, as a minor aside.

The structure is bad: Is something part of "Core", "Framework", "Standard", or "Platform Extensions"? It's particularly ridiculous that trying to switch from Core to Platform Extensions while you're viewing a Core class (such as System.DateTime[0]), you'll get kicked over to.. Framework.

The layout is bad: Look at System.DateTime's list of constructors[1]. It takes up a whole screenful to say what Python's datetime.datetime constructor[2] paragraph says in three lines.

The design is bad: Compare the method listing of .NET's IDictionary[3] to Scala's Map[4], or Rust's HashMap[5]. Which one makes the type signatures the easiest to parse? Which one helps you get where you want to the fastest?

(Hint: For me, at least, not the one that insists on making everything a uniform shade of baby blue.)

[0]: https://docs.microsoft.com/en-us/dotnet/api/system.datetime?...

[1]: https://docs.microsoft.com/en-us/dotnet/api/system.datetime?...

[2]: https://docs.python.org/3/library/datetime.html?highlight=da...

[3]: https://docs.microsoft.com/en-us/dotnet/api/system.collectio...

[4]: https://www.scala-lang.org/api/current/scala/collection/immu...

[5]: https://doc.rust-lang.org/stable/std/collections/struct.Hash...

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

#144

Earlier quoted context omitted.

Unless you've never made any particular use of StackOverflow, stumble on an incorrect answer, realize you have no way to fix it, and then just leave because you don't feel like jumping through hoops just to make somebody else's day better.

If you've never made any particular use of StackOverflow, why would you expect them to care what you have to say about anything on the site? It would probably take you as much effort to get 50 rep as it's taken you to post multiple sour grapes comments about how dare they have a threshold which excludes you, don't they know who you are??

> If you've never made any particular use of StackOverflow

I would have made use of it... if I didn't have to post questions I have no interest in posting to farm enough reputation to actually do anything to fix the incorrect answers I occasionally stumble across in Google searches.

> It would probably take you as much effort to get 50 rep

Again, I have zero interest in posting questions just to farm reputation. Less than zero, actually, because of the mental overhead involved in doing so.

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

#145
post #82

Earlier quoted context omitted.

See https://meta.stackexchange.com/a/164449/192171 If an answer is factually wrong (as opposed to just poorly formatted or missing a few details), generally its better to leave a comment rather than try to edit it. I agree its not ideal, but suggested edits go into a site-wide review queue, so not everyone reviewing them will necessarily be familiar with C. This makes edit reviews a poor tool for evaluating factual c…

"You can comment" doesn't help when you need a certain rep threshold just to comment.

Don't you need more to propose an edit?

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

#146
post #126

Earlier quoted context omitted.

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

It's usually better to put that information in the revision comments when you commit rather than in the code itself. Otherwise the code accumulates layers and layers of comments over years.

I feel like it depends - I know I don't just start digging through the commit history of every line I edit.

If I'm trying to fix a bug, and only have to change one line for it to start working, and the tests still pass - but that line was there for a reason that wasn't commented (some edge case) - I'll likely miss it.

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

#147

Earlier quoted context omitted.

> read API docs for anything I’m unfamiliar with One of the differences i've noticed between myself and some of the junior devs i've worked with. I would usually use the official docs as my first resource, and they would use stack overflow instead.

This is a hard lesson I had to learn as a junior developer. I'm impatient and Stack overflow can often give me an easy solution. But just as often, it can't and I will spend 30 minutes unproductively trying things with little progress. As I become a better developer I become more inclined to spend 30 minutes with the documentation instead.

I face a lot of anxiety from this. I'll have a task like setting up Point in Time Recovery for postgres, and I've spent days mostly just reading documentation - How postgres manages wal logs, how the internals of several popular solutions work etc.

I know it'll be worth it in the long run, but it feels like I'm wasting time because "I'm not doing anything" - I'm not committing any changes while my coworkers are busy adding new features.

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

#148
post #126

Earlier quoted context omitted.

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

It's usually better to put that information in the revision comments when you commit rather than in the code itself. Otherwise the code accumulates layers and layers of comments over years.

Personally, I've developed a strong preference for putting this type of information as close to the affected code as possible. Immediately next to the affected code is the only place these types of comments have a prayer of being kept up to date. Keeping them in another document, a commit message, or anything similar just results in the content of the message instantly going out of date.

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

#149

Earlier quoted context omitted.

> read API docs for anything I’m unfamiliar with One of the differences i've noticed between myself and some of the junior devs i've worked with. I would usually use the official docs as my first resource, and they would use stack overflow instead.

This is a hard lesson I had to learn as a junior developer. I'm impatient and Stack overflow can often give me an easy solution. But just as often, it can't and I will spend 30 minutes unproductively trying things with little progress. As I become a better developer I become more inclined to spend 30 minutes with the documentation instead.

When you're reading documentation, you also will notice other things in addition to solving your particular problem. Those other things might be helpful few minutes later and you will actually save that time. Or may be tomorrow, if your memory is good. Or may be you'll read those documentation and will actually find a better solution.

Of course most of interesting problems are not described in documentation.

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

#150
post #116

Razer went from making great hardware and drivers to making terrible drivers that require you to sign in to a Razer account and constantly run Razer software. I was a Razer die-hard for years, but with their transition from a hardware company to a cloud-based user-data-mining company I avoid them. If you want good hardware with good drivers I highly recommend SteelSeries.

Steelseries drivers are phoning home more and more now...

However - you can configure the mouse, then uninstall the drivers and the settings persist.

So I continue to use steelseries.

Post reply on HN