robzhu

6 ms·

1.
Innovation, Culture, and War(updateloop.dev)
2 points by robzhu 1y ago|0 comments
2.
by robzhu 2y ago
This is really cool! Definitely going to check it out
3.
Show HN: AI-generated tagline and image for long-form content(postly.dev)
1 points by robzhu 4y ago|0 comments
4.
by robzhu 6y ago
Can you provide an example?
5.
Show HN: Real-Time Session Invalidation(github.com)
2 points by robzhu 6y ago|0 comments
6.
The Case Against GraphQL(youtube.com)
2 points by robzhu 7y ago|0 comments
7.
Safe List Updates with DynamoDB(hackernoon.com)
2 points by robzhu 7y ago|0 comments
8.
by robzhu 7y ago
During China's Cultural Revolution, the Communist party also kept track of an adversity score.
9.
AWS Joins the GraphQL Foundation(aws.amazon.com)
7 points by robzhu 8y ago|0 comments
10.
by robzhu 8y ago
This is why I'm creating a command-line alternative to Photoshop.
11.
You Should Learn .net in 2019(hackernoon.com)
2 points by robzhu 8y ago|0 comments
12.
From MVC to Modern Web Frameworks(medium.com)
1 points by robzhu 8y ago|0 comments
13.
I'm Talking to Clothes: KonMari and Stoicism(medium.com)
1 points by robzhu 9y ago|0 comments
14.
by robzhu 9y ago
This seems like a pretty benign "cash grab" since it depends on helping the client succeed.
15.
by robzhu 9y ago
Congrats to the Graphcool team on the launch! You're part of what makes the GraphQL community awesome. I can't wait to see what you come up with next!
16.
Building Modern APIs with GraphQL(youtube.com)
3 points by robzhu 9y ago|0 comments
17.
by robzhu 9y ago
> I now see people on HN have very similar complaints about GraphQL - how its power and flexibility makes making a performant and secure GraphQL backend significantly harder than making an oldschool REST API backend. I'm curious to
18.
by robzhu 10y ago
I'm not sure I understand your use case. Can you give me an example of the problem you're dealing with?
19.
by robzhu 10y ago
They're similar with a few key differences. First, in OData, the URI is still a big part of the API, whereas the URI is unimportant in GraphQL, which allows GraphQL clients to simplify routing logic. Second, GraphQL lets you specify ar
20.
by robzhu 10y ago
You're right, there are no other protocols at nearly the scale of HTTP that use REST. I was just pointing out that REST was not strictly associated with HTTP in Roy Fielding's definition. If you look at my other link (Richardson M
21.
by robzhu 10y ago
Like other posters have said, the author appears to be pointing out shortcomings with HTTP, not REST. Roy Fielding made it fairly clear that REST is not strictly associated with HTTP. REST, as an architectural style, is defined by a set of
22.
Show HN: GraphQL and DDD: The Missing Link(medium.com)
3 points by robzhu 10y ago|0 comments
23.
by robzhu 10y ago
I highly recommend babun: http://babun.github.io/
24.
by robzhu 10y ago
You can send a GraphQL query as part of the query in your HTTP GET request: http://graphql.org/learn/serving-over-http/#get-request .
25.
by robzhu 10y ago
They're similar; both technologies allow clients to specify the data they need. I would say that GraphQL is more flexible and has a strong type system. For example, the filter semantics are defined within OData, while in GraphQL, you d
26.
by robzhu 10y ago
You might want to check out GraphQL: http://graphql.org/ . One of its killer features is the ability for clients to specify exactly the data it needs and obtain it in a single request/response.