yarg

It's beyond that.

There's information required to evaluate the current state that is currently unavailable - meaning that the current state of things will not be defined until the future.

Because the problem is perfectly avoidable with very little technical understanding, and this is Hacker News.

That only works in scenarios where competency is superfluous.

I'd like to see brain scans of burnt out people contrasted with those of people with PTSD.

With a more than fair share of both, I'm not sure that they're genuinely distinct phenomena.

I'd also be interested in how either/both tie in to depression.

I had a boss who actually acknowledged that he was deliberately holding up my development process - this was a man who refused to allow me a four day working week.

I had it go boom on Tumbleweed (when the drive filled up) less than a year ago.

I tried accessing and fixing the fubar partition from a parallel install, but to no avail.

> Defining 1/0=0 isn't really helpful imho

But it's quite a nice way to mask program bugs.

As someone who has pulled himself back from suicidality, I absolutely abhor the expression "died by suicide".

If I had gone through with it, I would have killed myself - and any euphemisms being thrown around would serve no-one at all (especially not those still living in that hole).

I would much rather have it framed as me having done something unforgivably stupid and completely preventable - but as a society we'd much rather reject that reality and instead refuse to acknowledge that more often than not the signs were all there; that not only was the death an irreversible act of idiocy, but it was also something that we could've and should've stopped yet did nothing to prevent.

It's a moot point.

Changes should be in place in time for regression testing, if you cannot manage that wait for the next cycle.

Those same rules apply to everyone, and you're being called out for not only repeatedly ignoring them, but also for refusing to listen to that criticism.

That's nowhere near useful enough to justify such a significant security flaw.

Relative coordinates sure, but why would you need the absolute position?

I'm with you on the second point - as unlikely as it is for the click to occur at the origin, it's still a legitimate value being abused as an indicator of something that might not actually be true - quite frankly the code was bad to begin with, and it was still bad after the fix.