dventimi

19 ms·

241.
by dventimi 2y ago
I don't have to kid myself that it's logical because I know it's logical. That's cold comfort, however, because we're not going to create a more just future by winning a debate, especially against individuals. &quot
242.
by dventimi 2y ago
> Glad half the people in the US is doing all they can to increase C02. Make that all of the people, even you.
243.
by dventimi 2y ago
> Logic studies arguments, which consist of a set of premises together with a conclusion. Premise: "I want warm weather and cheap housing." Premise: "People should move to the places that offer what they want.&quot
244.
by dventimi 2y ago
Seems pretty logical to pursue your own interests, which are inherently human and personal. We don't know the interests of the individuals who choose to live in Phoenix, so we're not in a position to say they're right or wron
245.
by dventimi 2y ago
> Guess that is "logic" as in "human logic I assume the people living in Phoenix are humans, yes. Seems likely they're using the one and only logic available to humans.
246.
by dventimi 2y ago
Seems pretty logical to me
247.
by dventimi 2y ago
Because there's demand for housing
248.
by dventimi 2y ago
It has a heat problem, obviously.
249.
by dventimi 2y ago
"Maybe using a general-purpose programming language instead of just SQL is overcomplicating it," said I every day of my life for the past 25 years. Oh well. You can't fight City Hall.
250.
by dventimi 2y ago
I grant that the N+1 problem is real, but I reject that it's always a serious problem. That's what I mean when I say this it's overblown. I'm not persuaded there's an avoidance of translating GraphQL. Rather, I thin
251.
by dventimi 2y ago
> It's trivially easy to say that if every SQL statement took 1ms to execute Good thing I don't say that! What I do say is that the number of SQL calls will tend to scale with the volume of data retrieved. Limit the volume of d
252.
by dventimi 2y ago
I do not share that author's belief about application code.
253.
by dventimi 2y ago
It is QL.
254.
by dventimi 2y ago
Not necessarily. Tools like Hasura, PostGraphile, and Prisma let you skip out without even having to pay with implementation complexity.
255.
by dventimi 2y ago
The N+1 problem doesn't exist on any project that uses, say, Hasura.
256.
by dventimi 2y ago
I think some of the complaints come from using code to offer GraphQL backends rather than just using PostGraphile
257.
by dventimi 2y ago
Hasura, PostGraphile, and Prisma do make it quite a bit easier for the backend.
258.
by dventimi 2y ago
It would be the same thing except with Benje's approach, you're basically using GraphQL as a developer tool to create those end points instead of writing code to do it. And you don't have to write something to convert them to
259.
by dventimi 2y ago
Same, with a shout out to PostGraphile as well. As an aside, I'm sorry but I roll my eyes every time I encounter data loaders and the N+1 problem it's meant to address but which really is a consequence of insistence on following t
260.
by dventimi 2y ago
I generally agree and am likewise "over" GraphQL. Having said that, I disagree on some of the finer points. First, some of these issues--authorization, security, N+1--can be mitigated by using something like Prisma, PostGraphile,
261.
by dventimi 2y ago
I do not accept your guarantee.
262.
by dventimi 2y ago
I don't believe I said the N+1 problem doesn't exist. I said that I believe it's "overblown". I'll grant that's vague, and I can be more precise, but one thing I mean by "overblown" is that it&#x
263.
by dventimi 2y ago
If I'm reading you correctly you're saying there's an industrial grade application with a UI that routinely shows up to 80000 attributes to a user, or at least needs that information for client-side processing. Setting aside
264.
by dventimi 2y ago
That's also 101 entities. That's a half a thousand values if A and B have ~5 attributes. That's too much data. No human can make use of it and no application should offer it. Good ones won't. They'll impose limits a
265.
by dventimi 2y ago
Again, the number of network calls will scale with the total data payload of the overall request, but the requested total data payload should never be large. It's effectively capped. Therefore, the number of network calls is effectivel
266.
by dventimi 2y ago
Agreed. The N+1 problem is not as big as people make it out to be.
267.
by dventimi 2y ago
PostgREST for instance avoids the alleged problem by generating a single SQL statement. So does Hasura, PostGraphile, and probably Prisma for that matter.
268.
by dventimi 2y ago
I think the N+1 problem is overblown. The number of database calls will scale with the volume of data retrieved, but the volume is data retrieved should always be small.
269.
by dventimi 2y ago
Question for the Big Data folks: where do sampling and statistics fit into this, if at all? Unless you're summing to the penny, why would you ever need to aggregate a large volume of data (the population) rather than a small volume of
270.
by dventimi 2y ago
HN guidelines urge us not to cross-examine and I wouldn't want to do that anyway, so let me just say this. If you want to share the details of how you were bitten by these sorts of things, I'll welcome it as your "lived exper

More ›