Did you actually read the link? The study basically attributes all of the negative effects to the change and not specifically standard time or daylight saving time, so I think what that means is DST is no more or less good for people than standard time. The switching is the part that is harmful.

In what way? Healthiness of a time standardization seems like it would be hard to validate. I personally prefer DST I’ve never considered either healthier or unhealthier. I remember hearing statistics about an abnormal number of car accidents and stuff happening the Monday after DST/ST changes. I’ve also heard some rhetoric about risk of car accidents with kids walking to bus or school being mitigated by standard time.

I’m assuming you mean something less acute than those which are focused on immediate outcomes like death lol? The only thing health related I can think of is daylight exposure and vitamin d levels, but it seems inconsistent whether people are more likely to take advantage of extra morning sunlight or evening sunlight. Seems like it would be a wash?

Anyway, I’m legitimately interested to know what you mean by “healthy”

Many GraphQL and gRPC APIs do exactly that and return HTTP 200 even if the request didn’t auth.

Just because you are heavily biased toward using HTTP status for application layer errors doesn’t make it right. It is so wildly common that people can’t imagine it working another way, and I get that.

But it’s not “wrong” to do application layer auth status codes and apply no transport layer auth status codes It’s just a different paradigm than most devs are used to.

What do you mean? You can literally run GraphQL without HTTP. This isn’t just a GraphQL-ism, gRPC also does it https://grpc.io/docs/guides/status-codes/

I understand that most people use GraphQL over HTTP and that from a developer perspective you’d rather have HTTP status codes like every other REST API. To which I’d say, why don’t you just use REST instead?

There are a bunch of legitimate reasons why a clean separation of transport layer and application layer makes sense - you just aren’t using them so it feels like an arbitrary frustration to you.

Have you ever run an application like a golang REST API behind an envoy or nginx proxy or load balancer and gotten an HTTP status 500 back and wrongly assumed it was coming from your application/golang code, only to later find it was a problem at the proxy or load balancer? If so, you’ve experienced the misdirection of combining transport and application layer being forced to share a status field. This isn’t a trivial example - time is wasted every day by developers misdiagnosing errors originating from transport as application errors, and vice versa.

You might not like it, but separating them IS smart design.

That’s true, but for a good reason. GraphQL is transport agnostic, so using HTTP status to represent errors doesn’t make sense. HTTP is just a carrier for GraphQL, and the status code represents whether or not the HTTP part was successful.