undefined | Better HN

0 pointsnprateem1y ago0 comments

I'm surprised it took 6 years to discover these issues. The N+1 problem and auth/field privacy are obvious on practically any project.

In other news, bitcoin will never replace cash, most companies don't need k8s and AGI isn't 2 years away.

0 comments

dventimi1y ago

The N+1 problem doesn't exist on any project that uses, say, Hasura.

jhatemyjob1y ago

Are you really surprised though? Like you alluded, people use Kubernetes and Bazel just because it has the big ol' G stamp on it. GraphQL is no different

(Well... slightly different. It's the FB stamp, not the G stamp)

nprateemOP1y ago

I'm surprised it took so long.

I worked with k8s and realised pretty quickly it was pointless for my org.

jhatemyjob1y ago

Yeah that's what I'm saying, it shouldn't be surprising, these delusions last entire careers. Look at all the people who base their career on Java

1 more reply

j / k navigate · click thread line to collapse

0 pointsnprateem1y ago0 comments

I'm surprised it took 6 years to discover these issues. The N+1 problem and auth/field privacy are obvious on practically any project.

In other news, bitcoin will never replace cash, most companies don't need k8s and AGI isn't 2 years away.

0 comments

dventimi1y ago

The N+1 problem doesn't exist on any project that uses, say, Hasura.

jhatemyjob1y ago

Are you really surprised though? Like you alluded, people use Kubernetes and Bazel just because it has the big ol' G stamp on it. GraphQL is no different

(Well... slightly different. It's the FB stamp, not the G stamp)

nprateemOP1y ago

I'm surprised it took so long.

I worked with k8s and realised pretty quickly it was pointless for my org.

jhatemyjob1y ago

Yeah that's what I'm saying, it shouldn't be surprising, these delusions last entire careers. Look at all the people who base their career on Java

1 more reply

j / k navigate · click thread line to collapse