lyxsus

8 ms·

31.
by lyxsus 6y ago
Amazing. Original comment I've reacted to: > Yeah, right. Because that SQL query will just magically write itself. Oh, just did, sorry > Especially if that ad-hoc GraphQL query requests extra fields Just did, whoops parent commen
32.
by lyxsus 6y ago
Ok, so you've failed to provide an example, I'll make you a big favour just this time. > If you need to get user, then 5 of his posts, then 50 of comments for each post That was the original database structure, right? So we ass
33.
by lyxsus 6y ago
No, because then I won't get anything from this conversation. Please, tell me, what else can I say to make you use a practical illustration of your position constructed on top of original example? I believe it's the only form of p
34.
by lyxsus 6y ago
I don't feel like I want to agree with that part, sorry. But I can admit I'm wrong if I had a counter-example relevant to that toy example. I'm very confused on where you're going to with that. > Because that SQL quer
35.
by lyxsus 6y ago
I was talking about the example originally provided, that had no data tapping with external services. That was a detail added by the guy I was replying to. idk why he decided it’s relevant there. If you want my yes or no answer, on is there
36.
by lyxsus 6y ago
So you gave me an example of a nested query that is not infinitely recursive and even admitted it. The one that as I said before you have an ability to easily identify before execution, just as any possible variations both in width and dept
37.
by lyxsus 6y ago
Ping me when you’ll be able to show infinitely recursive query in graphql. Until that, I agree, there’s no point to continue, and have a good luck with that :)))
38.
by lyxsus 6y ago
If you’re a backend developer, it’s just more work to do, unless you really make use of gql abstractions, they’re kind of more expressive than raw rest. For clients - instant exploitability, type safety, much more flexibility.
39.
by lyxsus 6y ago
You just don’t get that you can apply limitations to graphql query not unlike you when you don’t allow to fetch a billion records from rest endpoint? This what that about? Because that’s a question of how, solvable.
40.
by lyxsus 6y ago
He’s trying to make it like I believe in magic. Like I’m saying long live the backend job. Hell no, but it lets you to work with arguably better abstractions. And that posthraphile didn’t appear from thin air, it’s not a part of graphql, so
41.
by lyxsus 6y ago
But that’s absolutely not what the original example was showing. It was showing that even an dumb tool can do cool tricks on simple tasks. And that’s because you have an abundance of information about query and schema, so you can possibly d
42.
by lyxsus 6y ago
If you’ll keep cherry-picking this conversation will stop be entertaining. So yes, people who know what they’re talking about are discussing different set of problems that resolving data in general. I’m more and more convinced that you are
43.
by lyxsus 6y ago
What prevents me from Ddosing your fancy rest api? Nothing if you do nothing about it first. Why do you assign omnipotent requirements on one technology, but not another?
44.
by lyxsus 6y ago
Show me an example of how you make an infinite recursive query in graphql, I’ll wait. And I can spell it to you again, you know structure and complexity of your query before you execute it. Feel free to ignore it and disguise ignorance behi
45.
by lyxsus 6y ago
Omg, that’s clearly a trolling :) Or you’re really just talking to yourself.
46.
by lyxsus 6y ago
# part 2 It feels that there are the following type of people zealously hating gql: 1. Those who for some reason don’t understand it. That’s obvious from the scope of problems they highlight. The problem of resolving the data is not really
47.
by lyxsus 6y ago
It is not unbounded, unless you let it. Once again, at query time you have the full query. It’s not infinitely recursive. And if you split fetching the data by multiple endpoints and pretend your job is done, basically delegating the probl
48.
by lyxsus 6y ago
They can’t get any complexity, unless you let them. > lyxsus on HN: GraphQL gives you more control than REST. I like that :)
49.
by lyxsus 6y ago
lol, no. but nice cherry-picking, btw. too bad the original (and unedited) post is still available. # part 1 Let me break it down for you: > (This example is pretty silly, but I have very similar and not silly examples that I just can&#x
50.
by lyxsus 6y ago
If your front end is coded correctly, you know every query, their exact shape and complexity, so you can optimize for it and you exactly what you optimize for. If you let’s say have a public api, you’ll have more control than in rest, no le
51.
by lyxsus 6y ago
Omg, how hard is it to understand that any problem you attribute to graphql, will exist in rest. Every single one and more. Also, you can fine-tune any ad-hoc query, even in that magical tool, yeah. You know, your assumption of having a dee
52.
by lyxsus 6y ago
Lol The original post, if you’ll read it again, carefully, pointed out that you can compose a complex query in a single graphql query. And if you need this data, you have to get that data one way or another. What’s so hard about that? Now i
53.
by lyxsus 6y ago
In thread you’ve pointed before there’s a link to postgraphie. Even without tweaks it already gives a decent code. With some little efforts you can optimize anything you want, score query complexity and etc. If you don’t want unpredicted pe
54.
by lyxsus 6y ago
I think that these misconceptions a result of lack of experience/knowledge in graphic/databases and FP in general. I don’t see people writing assembly code trying to beat compiler optimizer very often, same thing here. We just nee
55.
by lyxsus 6y ago
Yes, it can and often will. That’s the point.
56.
by lyxsus 6y ago
I always thought it's an obvious and solid solution. And if we assume it's possible to do a snapshot and have a perfect mind clone in I can't see how there can be any doubt it'll work.
57.
by lyxsus 7y ago
Location: Saint-Petersburg, Russia Remote: Yes Willing to relocate: Yes Technologies: Javascript/TypeScript, React (Relay/Redux/Apollo), Postgresql/Mysql/NoSQLs, K8S, Python Résumé/CV: https://drive.
58.
by lyxsus 7y ago
But could we keep it if we wanted to? Is it possible to make any use out of it?
59.
by lyxsus 7y ago
Oh, you're right. But that's a rare case where it's an important thing to mention. Anyway, that's a health-related problem and my point was to bring it to a specialist. I think it's a terrible idea to ask that kind
60.
by lyxsus 7y ago
Did you already check your testosterone level and consulted therapist?

More ›