@FemaleIsNotAFeeling@william Maybe you should actually listen to what we are saying instead of making things up.
>How do they explain photos of the death camps with the emaciated starving captives? And the photos of dead bodies?
Germany had been the victim of the bombing of its infrastructure during the war, and lost the ability to produce and distribute as much food to its prison camps as it needed to. A picture of a starting person or a dead body does not prove anything about how or why it happened.
>There are videos on YouTube right now of some Nazis/ex Nazis that told some of the stories of what they did.
Plenty of ex-Nazis denied the holocaust, specifically those that fled and got safety elsewhere. Denying the holocaust is a CRIME that would have them executed, so many of these people just played along with it in order to have a chance at a normal life.
>Do they think Hitler was fake? How do they explain him away? There are so many videos of him and his famous speeches.
No. There is no evidence that Hitler ordered the holocaust, and there's an entire debate among Holocaust "Scholars"—functionalism v intentionalism—to try and explain how he's responsible. There's plenty of evidence that Hitler didn't like jews, but this was totally justified based on what jews had been doing to Germany, and are currently doing to the world today.
>What of the death camps like Auschwitz that still remain today and are open to the public to tour like a museum? What about all the hair and the teeth on display there that the Nazis took from the gassed bodies?
Just read the Chemistry of Auschwitz.
>Jews still live with their serial numbers tattooed on and faded by history. So much more stuff, it's not worth entertaining the lie.
Because it's not possible to fake a tattoo, obviously.
>Any holocaust denier is sick and hoping to repeat history one day.
No, the holocaust myth only exists as a narrative to make gentiles feel any kind of sympathy for jews at all, so that we do what they want. Whether it's going to war against Arabs, or flooding our country with foreigners, tolerating anti-social behavior in our cities, or letting men go into women's washrooms.
This is why you, FemaleIsNotAFeeling, are locked in here with us, because your unwillingness to tolerate men pretending to be women is just another form of anti-semitism. And national socialism is the only movement in all of history to put those freaks away.
@niggy@professionalbigot69 I was under the impression that backdoors would come from the Intel Management Engine or AMD's equivalent, rather than by backdooring the encryption algs or operating systems themselves.
You said that it's bullshit because we don't hear about it, and I said why you don't hear about it. But go ahead, stop being a coward and actually affirm White nationalism in your church and report back with what happened.
I'm pointing out that calling MODERN American Christianity the savior of White people is cave in head retarded because EVERY denomination, whether it identifies as liberal, evangelical, etc. does the same anti-White thing.
In both of our cases, we are posting our racism anonymously on the internet. The difference though, is that I don't pretend to go to a church that would excommunicate me immediately if they saw what I was posting.
Sometimes it's what people need to stop coping and get with the program (I needed that to get here), but I am concerned that there is a mentality that causes these people to harden their hearts and keep believing nonsense out of spite.
@feld@alex You should stop taking the commentariat on HN seriously.
Including children in a GQL query do not become the equivalent of arbitrary SQL LEFT JOINs because GQL is NOT A REPLACEMENT FOR SQL. If there is an include available in the GQL spec for your API, it's because you put it there. It doesn't allow random arbirary joins.
@feld@alex Not my team. They are 3rd party API services.
The tradeoff is between ingesting one query that has a lot of load on the backend and a bunch of queries that each have a smaller load but combined have a greater one. If a query takes too long, the smarter thing to do is to push it into a background job and give the caller a URL to fetch the result later. I don't know if common GQL tooling supports this, but this is the proper solution.
And no, it's not the same as handing out unrestricted access to your DB any more than REST is. It's an alternative way to make APIs, not a SQL replacement.
Edit: GQL also helps resolve the "problem" of corporate silos, even if it wasn't relevant to my specific case. It is a serious issue, and reducing the need for communication between different teams that are in different stages of the SDLC is a very good thing.
@feld@alex The advantage of REST API there is that everyone uses the SAME request, so they get cached. If you add query parameters to determine what fields get returned, those become separate requests so they can't be cached together.
/api/my_object and /api/my_object?fields=a,b are two different requests, so the only technical advantage of REST API is gone. All consumers of the API need to be calling /api/my_object for caching to work between those two consumers. The same is true for things like including children and filters.
But including children is by far the best advantage of GraphQL. With a REST API, you would need to custom code a /api/my_object?include=my_child parameter for it to work. It can be done, but it all has to be custom and I hardly ever see it done in practice. GraphQL makes it trivial to not only include children but filter and select fields for them, too.
For a REAL WORLD example, I regularly have to call REST and GQL APIs at work. With REST APIs, I regularly end up making THOUSANDS of individual requests to get all the information that I need, while I can pack everything from GQL APIs into a SINGLE request (plus pagination). The GQL takes a lot less time and is far simpler.
@feld@alex Not really. At least, if you contort a REST API to do what GraphQL can do, it loses the advantages of REST APIs. The singular advantage of a REST API is that they are highly cacheable. The advantage of GraphQL is that it's easier to make querying child objects in a single request, you can add query parameters to a REST API to include specific child objects, but you have to do this specifically for each child object, and it also becomes a new request that can't be cached with the other requests.
@alex@feld GraphQL is a replacement for REST APIs. It's not about app scalability, but organization scalability. It makes it easier for you to connect multiple frontends to a single backend without the need for SDK development teams.