jdmnd

Great news! Related[0]. The presentation video in the linked article from 2002 is a gem.

0: https://news.ycombinator.com/item?id=46266875

What you're suggesting seems like a spectacular leap. I do not think it is very likely that the unnamed employee at Cloudflare that was micro-optimising code in the DNS resolver is also the author of this RFC, Joe Abley (the current Director of Engineering at the company, and formerly Director of DNS Operations at ICANN).

This is interesting. It looks like there was even some discussion of making this behaviour part of the standard, since it's implemented by all of the major browsers.

https://github.com/whatwg/html/issues/2390

It works for any type that implements the `std::error::Error` trait; which is something you can easily implement for your own types. If you want your errors to be integers for some reason, you can wrap that type in a zero-sized "newtype" wrapper, and implement `Error` for that.

The Stack Overflow answer you linked seems to be claiming that it's simply easier to return strings, but I wouldn't say this is a restriction imposed by the language.

I found this[0] discussion on Jonathon Blow's youtube channel about game physics/framerate dependence. It certainly seems to more than simply a problem of software architecture as some commenters appear to suggesting here.

[0] https://www.youtube.com/watch?v=fdAOPHgW7qM

> I just realized I’m agreeing with a social justice warrior about something

Why are you accusing thinkxl of being a “social justice warrior” and why, exactly do you feel that that undermines your agreement? Is website usability a liberal ideology? Lacking any actual justification your edit feels very out of place on hn.

There was an announcement[0] a couple of years ago that certainly provoked a lot of debate on HN[1].

[0] https://github.com/Homebrew/brew/blob/master/docs/Analytics.... [1] https://news.ycombinator.com/item?id=11566720

  Timestamps are 64bit nanoseconds

As far as I can tell, this will overflow in just 11 years – 2028-06-15 09:33:27.3709551615 UTC

Why would this go into a new standard? Is there a practical use for such a high level of granularity?

edit: off by a factor of 10 in my calculation... It's actually

2554-07-21 23:34:33.709551615 UTC

Presumably GP meant phlogiston https://en.wikipedia.org/wiki/Phlogiston_theory

I have the same issue on the mid 2012 13" model. The camera seems to stop being recognised whenever the macbook goes into sleep mode... no solution found so far.