Live data from Hacker News

Math.Pow(-1, 2) == -1 in Windows 11 Insider build

github.com

121–130 of 142 posts

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#121
post #29
post #6

Side note. One of the advantages of using proprietary packaged software is supposed to be a unified support and product. In this case the maintainer redirects the issue to some other team and passes the ball as if it were an open source project with 50 dependencies with thin responsibilities "no, if there's an issue with a button, you should report it to GUI-button, we do GUI-form and we just pass the button generati…

The buck is passed all of the time, it simply happens internally and out of sight of the customer. In this case, it looks like an open source component managed by a commercial company. They could do everything out of sight, but the open source world also encourages transparency.

Right, as a customer you always prefer that it happen out of sight, but I guess these are the very tradeoffs of choosing open source software, you can't get the best of both worlds.

That said, maybe a slight change like, "I'll open a ticket with the other team" instead of "you should open a ticket with the other team" makes all the difference. But like I said in another comment, if you open a ticket on github, you aren't paying for that support, you should aim to have a commercial relationship with Microsoft and then raise the issue through that commercial channel.

Otherwise you have no recourse to complain, you are getting everything as-is.

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#122
post #81
post #60

Earlier quoted context omitted.

> What do you disagree with, exactly? OP said it quite clearly and so did you: that it's the reporter's job. It's the maintainer's job to put in the bug report now.

> OP said it quite clearly and so did you: that it's the reporter's job. I don't agree that it was stated clearly. That's the whole point of my comment. Leaving it unclear is bad, tasks should always have an unambiguous owner.

From the OP:

> It’s not the job of a bug reporter to figure that out

What’s ambiguous about this statement?

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#123
post #49

Earlier quoted context omitted.

Unless the documentation says that Math.Pow just returns the result of calling some other code (it doesn't do that), the bug is both in the Math.Pow and underlying library. It should be reported and tracked in both.

But should it be the responsibility of the person reporting the bug in Math.Pow, or the devs maintaining Math.Pow sees it is part of the underlying library and makes the report?

The latter

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#124

Earlier quoted context omitted.

You're joking but we went from the Ada "contracts and pre/post conditions" to the ReactJS monstrosities instead on improving the whole thing and being more strict.

I think it has more to do with the people than the tools.

that's what the comment means we as people went from picking Ada to ReactJS

of course we also went from having no Rust and no TypeScript and only a few hundred thousand semi-academic people having some knowledge of programming to hundreds of millions of people doing some tutorial/bootcamp/cert/degree, or even built something, or actively learns, or right now works as a professional programmer.

(un)fortunately Ada was not able to grow to became the default tool for all these jobs that all those millions of people did or wanted to do when they did/do programming.

JS/ECMAScript is evolving, things are getting better!

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#125
post #30

Earlier quoted context omitted.

What do you disagree with, exactly? The bug is in an underlying library, so it should be reported to that library. That all seems correct to me, I don't see what there is to disagree with there. The problem with the comment is it does not make ownership of the next steps clear. The maintainer should've either taken the ball ("I will report this to...") or made it clear that the reporter should hold the ball ("We can'…

Bro is a Microsoft employee. He should say "thank you for the bug report", and open a bug in the underlying library if that is the correct place. Bug reporter might not care that much and not bother opening another bug report, and this looks like a pretty bad bug.

It was clarified on the thread that that person was NOT a Microsoft employee and just a volunteer. That completely changed my perspective on the situation.

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#127

How does the OS still function with a basic bug like this?

Due to how windows manage dependencies, you can have different versions of same library all the way back to windows xp days. It's not necessary other software on the computer will hit the bug on this version of library.

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#129
post #91
post #18

Earlier quoted context omitted.

I'm more used to hear this kind of 'it's not our fault' crap from state bureaucracies not companies that want me to pay them...

Microsoft is long past the point of realizing they don't need to make their product good to keep users. Everyone who uses Windows is stuck using it because of software lock-in, or it's what's on the laptop their job provides, or because they can't afford a Mac. Outside of niche communities, there aren't a lot of "Windows fans" out there these days. They'll gladly harvest your data whether you like them or not!

> because they can't afford a Mac

Ha, as if the situation with macOS is much better? The OS space is a (lopsided) duopoly, both Microsoft and Apple know it and have pulled down their sleeves long ago.

Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build

#130
post #105

Earlier quoted context omitted.

The definition is you write or amend a test before making the code change that makes it pass. That's it. It says nothing about the type of test you write. Personally i do it with literally every type of test that i write - acceptance, integration, unit. If you write a decent test, yes, TDD is always valuable. If you TDD with shitty tests, not so much, but that isnt really an issue with TDD.

Sounds like a “no true Scotsman” fallacy.

It's not. "Doing C before doing Y is beneficial but requires you to be competent at C." is not a no true Scotsman.
Post reply on HN